SMS campaign tracking with UTM
SMS messages are tiny and links open in whatever browser the phone uses, so SMS needs short, UTM-tagged links to be measurable. This page shows how utm_medium=sms keeps text traffic distinct, and the privacy rule that a recipient's number or identity must never appear in the URL.
Short links plus UTM
SMS has tight character limits, so you typically send a short link that redirects to a UTM-tagged destination. Tag the destination, not the visible short link:
- Short link redirects to a tagged page
- destination carries utm_source=<your-sms-tool-or-list>
- utm_medium=sms (kept distinct from email)
- utm_campaign=<the specific send>
Keep recipient data out of the link
It is tempting to personalise SMS links per recipient, but a phone number is personal data, and any per-recipient identifier in the URL ends up in server logs and forwarded messages. Keep the UTM to generic, send-level labels and let your messaging platform hold the per-recipient engagement data privately.
Use utm_medium=sms rather than folding texts into email, so the two channels report separately. Because the destination tags survive the short-link redirect, the click is attributed even though the SMS app provides no referrer.
How it appears in analytics and logs
A visit with utm_medium=sms confirms a text-driven click. Because messaging apps often pass no useful referrer, an untagged SMS link usually lands in direct, undercounting the channel.
Diagnostic use case
Tag the links you send by SMS so text-driven visits are attributed to the SMS channel rather than dropped into direct.
What WebmasterID can help detect
WebmasterID reads utm_medium=sms at ingest and attributes the visit to your SMS campaign, so text traffic appears as a measured source instead of direct.
Common mistakes
- Putting a recipient's phone number or ID into the link as personalisation.
- Using utm_medium=email for texts so SMS and email blur together.
- Sending a bare short link with no UTM on the destination, so it lands in direct.
Privacy and accuracy notes
Never put a recipient's phone number, name, or account ID in an SMS link. Numbers are personal data, and the URL is logged and shareable. Use generic campaign labels and an opaque short link.
Related pages
- Push notification campaign tracking
Push notifications drive re-engagement, but their clicks blur into direct or app traffic unless tagged. This page shows how utm_medium=push keeps notification-driven visits as a distinct channel, with a worked example and the rule against personal data in the link.
- Newsletter campaign tracking with UTM
Email clients usually send no web referrer, so newsletter clicks need UTM tags to be attributed at all. This page gives a recommended utm_medium=email structure with per-send utm_campaign naming, and the hard privacy rule that subscriber identifiers must never appear in a UTM.
- Campaign links (docs)
Point SMS short links at UTM-tagged destinations.
Sources and verification notes
- MDN — Redirections in HTTPSMS short links redirect to a UTM-tagged destination.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.