BlogAnalytics

UTM parameters for app campaigns in India: WhatsApp, SMS, QR and the Play Store

· 6 min read · By the Strait team

A practical UTM naming scheme for Indian app campaigns across WhatsApp, SMS, Instagram, push and QR codes, where the tags get lost on the way into an app, how Google Play's referrer carries them through an install, and what TRAI's URL whitelisting means for SMS links.

UTM parameters are the simplest analytics tool there is: five or so query parameters on a link that say where a visit came from. On the web they just work. For an app campaign they quietly fall apart, because the visit doesn't end on a web page. It ends in an app, often after a trip through the Play Store.

This post is about making UTM tags survive that trip, with a naming scheme that fits the channels Indian apps actually use.

Why this is mostly an Android problem in India

StatCounter put Android at 93.89% of mobile operating system use in India in September 2026, and iOS at 6.05% (StatCounter: mobile OS market share in India). Whatever you do on iPhone, the Android path decides whether your campaign numbers are right. The good news: Android is also where carrying tags through an install is well supported.

The parameters

Google Analytics documents the full list (Google Analytics Help: collect campaign data with custom URLs). The five you'll use on almost every link:

Parameter What it's for Example
utm_source Where the visit came from whatsapp
utm_medium The type of message broadcast
utm_campaign The offer or promotion diwali-sale
utm_content Which link inside the same message banner-a
utm_term The paid keyword, for search ads running-shoes

A naming scheme for Indian channels

The value of UTM tags comes from consistency. WhatsApp, whatsapp and wa are three different channels in a report. Pick lowercase, dashes, one name per channel, and write it down:

Channel utm_source utm_medium
WhatsApp broadcast or Business API whatsapp broadcast
WhatsApp share by a user whatsapp referral
SMS (DLT template) sms transactional or promotional
Instagram bio or story instagram social
Push notification push notification
Email newsletter newsletter email
QR code on print qr print
Influencer the creator's handle influencer

Use utm_campaign for the offer (diwali-sale, ipl-week-2) and utm_content to tell two links in the same message apart. Our UTM builder applies these conventions and lowercases everything for you.

Where the tags get lost

Where UTM tags go on an app campaignA tagged link is tapped. If the app is installed, the app must read the tags from the link. If not, the person goes through Google Play, and the tags survive only if they are carried in the install referrer or recorded on the server at tap time. Tagged link tapped App installedapp reads the link Not installedPlay Store, then install tags kept if the appor server records them tags lost unless carriedby the referrer or tap
On the web, the page reads the tags. In an app campaign, two different paths have to keep them.

App installed. A verified link opens the app directly, so no web page ever runs your analytics script. The app has to read the tags from the URL it was opened with, or a server has to record them when the link is resolved.

App not installed. The person goes to Google Play. Your website never sees them again, and the app's first open has no URL at all. Unless something carries the tags through the install, the install shows up as organic.

Carrying tags through Google Play

Google Play has an official carrier: the referrer parameter on a Play Store link. Whatever you put there is returned to your app on first open by the Play Install Referrer API, together with the time of the referring visit and the time the install began (Android Developers: Play Install Referrer). URL-encode the tags into that one parameter:

JavaScript
const tags = new URLSearchParams({
  utm_source: 'whatsapp',
  utm_medium: 'broadcast',
  utm_campaign: 'diwali-sale',
}).toString();

const play = `https://play.google.com/store/apps/details?id=com.yourco.app&referrer=${encodeURIComponent(tags)}`;
// …&referrer=utm_source%3Dwhatsapp%26utm_medium%3Dbroadcast%26utm_campaign%3Ddiwali-sale

Play Console also uses these: its listing conversion analysis can be filtered by "the value of the utm_source URL parameter in deep links to your store listing", and the same for utm_campaign (Play Console Help: understand and grow your app's user base).

The limit of a raw Play link is that it only serves people without the app. People who have it installed land on the listing too, instead of in the app. That is why app campaigns use a deep link that decides per phone.

How Strait keeps the tags

With Strait, you put the UTM tags on the link's destination once, and the link server does the rest:

  • Channel. Each tap's channel is the first of: the tapped URL's utm_source, the destination's utm_source, the in-app browser it was tapped in (whatsapp, instagram…), then the referrer. So an untagged WhatsApp tap can still be labelled WhatsApp (REST API reference).
  • Campaign. A link's campaign is the one you set, or else the destination's utm_campaign, and it follows the destination if you change it. On iPhone, the campaign is also passed to the App Store as the campaign token.
  • Through the install. On Android, a tap without the app goes to Google Play with the link id and the tap id in the referrer. On first open, the SDK reads it and the install is joined to that exact tap, so it inherits the tap's channel and campaign. Our Play link carries those ids, not your UTM tags, so for a breakdown by your campaign names use Strait's Analytics rather than Play Console's UTM filters.
  • Through to revenue. Purchases sent with trackEvent carry the tap they came from, within 7 days of the open, so revenue lands on the channel and campaign (Analytics: how we count).

In the app, the destination's query parameters arrive with the link, so your own analytics can read them too:

TypeScript
links.onLink((e) => {
  if (!e.matched) return;
  myAnalytics.setCampaign(e.params.utm_campaign); // your own analytics tool
  openPath(e.path, e.params);
});

We tested the Play path end to end on a real phone with a Google Play internal testing build: tap without the app, install from Play, first open on the link's screen, install recorded with the method install_referrer.

If your campaign goes out by SMS, the tags are not your only worry. TRAI directed telecom operators on 20 August 2024 to block SMS traffic containing URLs, APKs or OTT links that are not whitelisted, to be implemented by 1 October 2024 (PIB: TRAI press release).

Two practical consequences:

  1. Whitelist the domain your links use, not your website's, in your DLT template. Each Strait workspace has its own subdomain (<handle>.strait.link), so only your links pass.
  2. Keep SMS links short. A 160-character message has no room for a long URL full of tags. Put the tags on the destination and send a short slug like /diwali; the tags still reach your reports.

A campaign checklist

  • One naming scheme, written down, lowercase with dashes
  • Tags on the destination of each link, not typed into each message by hand
  • One link per placement (utm_content or a separate slug) so channels don't blur
  • Android App Links verified, so installed users open the app (App Links checker)
  • A test install from Google Play to see the campaign carried through
  • Link domain whitelisted in your DLT templates before an SMS send

For printed codes, the app QR code generator adds utm_source=qr and utm_medium=print for you. For WhatsApp specifics, see how to open your app from WhatsApp links.

Sources and how we checked