From 1bed935467d195cee52511b6fdac8ab7531d7ea8 Mon Sep 17 00:00:00 2001 From: harsh mahajan Date: Mon, 31 Aug 2026 22:39:52 +0530 Subject: [PATCH] feat(console): use utm params the sources pipeline actually records The console's source handler reads ref, utm_source, utm_medium and utm_campaign and posts them to /console/sources. A bare `source` param is not read anywhere, so it was dead weight. utm_medium distinguishes the surface, so a banner or navbar entry added later can be compared against the card. An explicit param is required because the handler discards same-origin referrers, and cloud.appwrite.io matches that check. --- src/routes/(console)/bottomAlerts.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/routes/(console)/bottomAlerts.ts b/src/routes/(console)/bottomAlerts.ts index 06cf2064d..f8a5a8b94 100644 --- a/src/routes/(console)/bottomAlerts.ts +++ b/src/routes/(console)/bottomAlerts.ts @@ -20,7 +20,8 @@ if (isCloud) { scope: 'everywhere', cta: { text: 'Try it now', - link: () => 'https://appwrite.io/?ref=old-console&source=promo_card', + link: () => + 'https://appwrite.io/?utm_source=old-console&utm_medium=promo_card&utm_campaign=new-console', external: true, hideOnClick: true, skipUpgradeRedirect: true