UTM Tracking for CleverTap: How to Build and Validate Campaign Links

Why CleverTap requires per-channel UTM tracking

CleverTap is built for mobile-first engagement — its core channels are push notifications, in-app messages, email, and SMS, all orchestrated from a single platform. This cross-channel architecture creates a UTM tracking challenge: if you use the same tracked URL across push, email, and in-app steps in a CleverTap Journey, GA4 cannot distinguish which channel drove each session. The utm_medium parameter is the only reliable way to separate channel attribution in GA4 when one platform delivers across multiple channels.

Push notifications are the highest-risk channel. When a user taps a CleverTap push notification, the device opens the campaign URL with no HTTP referrer header. GA4 sees a session with no referrer and classifies it as Direct traffic — your push channel's contribution vanishes into the Direct bucket. SMS links have the same problem: no referrer, no attribution. Email traffic is slightly more forgiving because some email clients pass referrer headers, but explicit UTM parameters on email links give you guaranteed attribution that is more reliable than referrer inference.

The only approach that works consistently across all CleverTap channels is per-channel UTM tagging: build a separate tracked URL for each channel step within a Journey, keeping utm_campaign consistent across all steps and varying utm_medium by channel.

Building tracked CleverTap campaign URLs with mlz build

CleverTap's campaign builders have a destination URL field — in push campaigns this is the "Redirect URL" or deep link target, in email it is any hyperlink, in in-app messages it is the button action URL, and in SMS it is the message link. Build your tracked URL with mlz build before opening the CleverTap campaign builder, then paste the tracked_url into the appropriate URL field. For multi-channel Journeys, build a separate tracked URL per channel step — changing only the --medium flag while keeping the same --campaign slug.

# Push notification step in a CleverTap Journey
$ mlz build \
  --url "https://app.example.com/reengagement" \
  --source "clevertap" \
  --medium "push" \
  --campaign "win-back-jun-2026" \
  --validate

{
  "tracked_url": "https://app.example.com/reengagement?utm_source=clevertap&utm_medium=push&utm_campaign=win-back-jun-2026",
  "params": {
    "utm_source": "clevertap",
    "utm_medium": "push",
    "utm_campaign": "win-back-jun-2026"
  },
  "stored": true
}

# Email step in the same Journey (same campaign, different medium)
$ mlz build \
  --url "https://app.example.com/reengagement" \
  --source "clevertap" \
  --medium "email" \
  --campaign "win-back-jun-2026" \
  --validate

{
  "tracked_url": "https://app.example.com/reengagement?utm_source=clevertap&utm_medium=email&utm_campaign=win-back-jun-2026"
}

# SMS step: same campaign slug, utm_medium=sms
$ mlz build \
  --url "https://app.example.com/reengagement" \
  --source "clevertap" \
  --medium "sms" \
  --campaign "win-back-jun-2026" \
  --validate

{
  "tracked_url": "https://app.example.com/reengagement?utm_source=clevertap&utm_medium=sms&utm_campaign=win-back-jun-2026"
}

In GA4, filter by utm_campaign=win-back-jun-2026 to see all sessions from this CleverTap Journey, then pivot on the utm_medium dimension to compare push, email, and SMS contributions side by side. The consistent utm_campaign slug groups all Journey touchpoints together, while distinct utm_medium values separate them by channel — giving you a complete multi-channel attribution picture in a standard GA4 acquisition report without any custom dimensions or custom channel groupings.

UTM tracking for CleverTap Journeys (multi-step automation)

CleverTap Journeys are multi-step automated workflows triggered by user behavior events — app installs, purchases, inactivity, or custom events. A single Journey can include push notifications, emails, in-app messages, and SMS in a coordinated sequence. When building a Journey, every step that includes a link to an external URL needs its own tracked URL. Use a consistent utm_campaign slug for all steps in the Journey, match utm_medium to the channel for each step, and use utm_content to identify the specific step or variant.

# Step 1: Welcome push notification (day 0)
$ mlz build \
  --url "https://app.example.com/onboarding/step1" \
  --source "clevertap" \
  --medium "push" \
  --campaign "onboarding-journey" \
  --content "push-day-0" \
  --validate

{
  "tracked_url": "https://app.example.com/onboarding/step1?utm_source=clevertap&utm_medium=push&utm_campaign=onboarding-journey&utm_content=push-day-0"
}

# Step 2: Onboarding email (day 1)
$ mlz build \
  --url "https://app.example.com/onboarding/step2" \
  --source "clevertap" \
  --medium "email" \
  --campaign "onboarding-journey" \
  --content "email-day-1" \
  --validate

{
  "tracked_url": "https://app.example.com/onboarding/step2?utm_source=clevertap&utm_medium=email&utm_campaign=onboarding-journey&utm_content=email-day-1"
}

# Step 3: In-app message (day 3, shown when user opens app)
$ mlz build \
  --url "https://app.example.com/feature-tour" \
  --source "clevertap" \
  --medium "in-app" \
  --campaign "onboarding-journey" \
  --content "in-app-day-3" \
  --validate

{
  "tracked_url": "https://app.example.com/feature-tour?utm_source=clevertap&utm_medium=in-app&utm_campaign=onboarding-journey&utm_content=in-app-day-3"
}

With this tagging structure, GA4's campaign report for utm_campaign=onboarding-journey shows total sessions, completed onboarding steps, and any conversion events associated with the entire Journey. The utm_medium dimension breaks down which channel drove each step completion, and utm_content shows which specific step in the Journey was the last touchpoint before the conversion event. This is the standard UTM structure for Journey-level attribution in GA4.

CleverTap UTM tracking gotchas

CleverTap does not auto-append UTM parameters to campaign URLs

CleverTap has no global setting that automatically appends standard UTM parameters to all campaign links. CleverTap's built-in analytics tracks delivery and engagement using CleverTap's own internal tracking — but these are not UTM parameters and GA4 cannot read them for session attribution. Every push notification Redirect URL, every email hyperlink, every in-app message CTA URL, and every SMS link requires a manually tagged URL. Build tracked URLs with mlz build before entering them in CleverTap to ensure standard UTM parameters are present on every campaign destination URL.

Using a single tracked URL across all channels in a Journey merges attribution

A common shortcut is building one URL with utm_source=clevertap&utm_medium=push and reusing it for every step in a Journey. This is incorrect for any non-push step — email clicks, SMS clicks, and in-app CTAs that reuse the same push-tagged URL will be attributed to the push channel in GA4. Build a separate tracked URL per channel step, changing only the utm_medium value. The additional build commands take under a minute and produce channel-level attribution that is accurate rather than misleading.

CleverTap SMS uses link shortening — add UTM parameters before shortening

CleverTap SMS campaigns can use built-in link shortening. If UTM parameters are added after the URL has already been shortened, the parameters append to the short URL and may or may not survive the redirect chain depending on the redirect implementation. The reliable approach is to build the fully tagged URL with mlz build first, then paste that tagged URL into the CleverTap SMS campaign builder before CleverTap applies any shortening. CleverTap shortens the complete tagged URL as a unit, and the redirect from the short link to the destination typically preserves query string parameters. Use mlz build --validate to confirm the destination resolves before the SMS campaign launches.

CleverTap in-app CTAs that navigate within the app do not need UTM tags

CleverTap in-app messages can have CTA buttons that navigate to an in-app screen (deep link routing) or open an external browser URL. UTM parameters are only relevant for external browser URLs — in-app routing does not load a web URL and GA4 never sees the navigation event in the standard SDK configuration. For in-app CTAs that open external browser URLs (promotional banners, feature announcements, campaign landing pages), build a tracked URL with utm_medium=in-app. For buttons using in-app routing or deep links that stay inside the app, no UTM tagging is needed.

CleverTap A/B testing variants need separate tracked URLs

CleverTap supports A/B testing for push notifications and emails, allowing you to test different message copy, images, or send times. If the A/B variants link to the same destination URL, standard UTM parameters cannot distinguish variant performance in GA4 (GA4 doesn't know which CleverTap variant drove the session). Use utm_content to differentiate variants: build --content "variant-a" and --content "variant-b" URLs for each test arm and use them in the respective CleverTap variant configurations. In GA4, pivot on utm_content within the campaign to compare variant conversion rates directly.

CleverTap UTM naming conventions

Recommended UTM parameter values for CleverTap, aligned with GA4 channel reporting and a lowercase-hyphenated taxonomy:

• utm_source: clevertap for all sends from the CleverTap platform across all channels. Always lowercase. A single source value for all CleverTap channels makes it easy to filter GA4 acquisition reports to see all CleverTap-attributed traffic regardless of channel, then pivot on utm_medium for channel breakdown.
• utm_medium: Match the delivery channel — push for mobile push notifications (iOS and Android) and web push; email for email campaigns; sms for SMS campaigns; in-app for in-app message CTAs that open external browser URLs. Add a GA4 custom channel grouping rule (Admin > Data Display > Channel Groups) to classify utm_medium=push under a Push channel, as GA4 does not include Push in its default channel grouping. Similarly add a rule for utm_medium=in-app if you want a dedicated In-App channel row in GA4 reports.
• utm_campaign: A consistent slug per campaign or Journey. For one-off campaigns: black-friday-nov-2026, new-feature-launch-jun, weekly-digest-jun-8. For automated Journeys: onboarding-journey, win-back-30d, cart-abandonment-flow, reengagement-jun-2026. Use the same campaign slug across all channel steps in a Journey so GA4 groups all Journey touchpoints into a single campaign row.
• utm_content: Journey step identifier or A/B variant label. For multi-step Journeys: push-day-0, email-day-1, in-app-day-3. For A/B tests: variant-a, variant-b. For specific in-app CTA buttons: primary-cta, banner-cta. Omit when a campaign has a single CTA, single step, and no variants.
• utm_term: Rarely used for CleverTap campaigns. Consider for audience segmentation where the same campaign is sent to different behavioral segments: utm_term=lapsed-30d, utm_term=high-value, utm_term=new-users.

See the UTM naming conventions guide for the full cross-platform reference and the UTM tracking for developers guide for programmatic generation and validation at scale.

FAQ

Does CleverTap auto-tag campaign URLs with UTM parameters?

No. CleverTap does not have a global auto-UTM setting that appends standard UTM parameters to all campaign links. CleverTap tracks campaign performance in its own analytics using CleverTap's internal event tracking — but these are not standard UTM parameters and GA4 cannot use them for session attribution. To correctly attribute CleverTap-driven sessions in GA4, you must manually add UTM parameters to every campaign URL before entering it in CleverTap's campaign builders. Build tagged URLs with mlz build --source "clevertap" --medium "push" (or the channel-appropriate medium) before opening the CleverTap campaign editor.

What utm_source should I use for CleverTap?

Use utm_source=clevertap for all campaigns sent through the CleverTap platform. Use a single source value for all CleverTap channels (push, email, SMS, in-app) rather than channel-specific source values like utm_source=clevertap-push — the channel distinction belongs in utm_medium, not utm_source. A unified source value makes it easy to filter GA4 to see all CleverTap traffic in one view, then pivot on utm_medium to compare channel performance.

How do I track CleverTap Journeys in GA4?

Use a consistent utm_campaign slug for all steps in the Journey, match utm_medium to the channel for each step, and use utm_content to identify each step (e.g., push-day-0, email-day-1). In GA4, filter by utm_campaign to see all sessions from the Journey, then pivot on utm_medium to compare channel contributions and on utm_content to compare individual step performance. This gives you multi-touch Journey attribution in standard GA4 reports without requiring custom dimensions or BigQuery.

CleverTap has its own analytics dashboard — do I still need UTM parameters for GA4?

Yes. CleverTap's analytics dashboard reports on CleverTap-specific events: notification delivered, notification clicked, email opened, email clicked, in-app viewed, SMS delivered. It does not push session or channel attribution data into GA4's acquisition reports. GA4's channel reporting is built from UTM parameters and referrer headers — it has no visibility into CleverTap's internal event data. If your product or marketing analytics live in GA4 (conversions, LTV, funnel reports), UTM parameters on every CleverTap campaign URL are required to correctly attribute sessions in those reports.

How do I validate CleverTap campaign URLs before launching?

Run mlz build --url "your-destination-url" --source "clevertap" --medium "push" --campaign "your-campaign-slug" --validate for each campaign URL before entering it in CleverTap. The --validate flag confirms HTTPS, resolution (200 response), redirect chain integrity, and query string preservation through any redirects. For landing pages that will be shared across multiple channels, run mlz inspect "your-tracked-url" to verify OG tags, Twitter Card metadata, and viewport configuration — a landing page missing OG tags will render poorly when users share it from email or social, even if the push campaign itself delivers correctly. See the campaign link preflight check guide for the full pre-launch validation workflow.

Related reading