UTM Parameters for SMS Text Messages: The Short Link Trap I Keep Seeing
UTM parameters for SMS text messages are simple in theory and messy in practice, and the mess starts the moment someone pastes a full tagged link into a 160 character message and watches it eat half the text.
A client once showed me a GA4 report where SMS traffic appeared under three different sources, two campaigns that were really one campaign, and a large pile of direct traffic that smelled like text messages. The texts themselves were fine. The offers were fine. The tagging was the problem, and it was a problem made of small decisions: a capital letter here, a shortened link built before the tags were added there, a second person on the team who invented their own naming scheme on a Friday afternoon. None of those decisions felt important when they were made. Together they made the report useless.
Start with the values that work for SMS. The source should be sms, kept lowercase forever, because GA4 treats SMS and sms as different sources and will split your report without warning you. The medium is usually sms or text, and you must pick one and never mix them. The campaign names the specific send, like summer_sale or cart_recovery, and the content value separates two links or two message versions inside the same campaign, which is how you run an honest A/B test by text. Term is optional for SMS and most campaigns skip it. Three parameters do most of the work. Five parameters used inconsistently do damage.
The order of operations is the part people get backwards. Build the tagged link first, then shorten it. The short link must point at the full tagged destination, so that when a reader taps it, the UTM values arrive intact in analytics. Shorten first and tag the short link, and the redirect often strips the values or sends them somewhere useless. Test the full chain before you send to a list: tap the short link on a real phone, confirm the landing page loads, and confirm the tagged visit appears in your analytics test view. A test send to your own phone costs nothing and catches the mistake that a thousand person send cannot undo.
UTM parameters for SMS text messages: what about character count?
SMS messages have a hard reality that email does not: a standard text is 160 characters, and a full tagged URL can consume most of that in one gulp. That is why shortening is not cosmetic for SMS, it is the whole delivery method. A branded short domain is worth the setup, because a generic shortener hides the destination and lowers trust, and trust is the currency of a text message from a business. Readers decide in about a second whether a link looks safe, and a familiar domain passes that test while a random string of characters often does not.
There is a second cost to long links that nobody mentions until the bill arrives. Messages that exceed the character limit split into segments, and carriers charge per segment. A tagged link that pushes a message from one segment to two doubles the send cost for that message, quietly, across a whole list. Shortening the link is therefore a cost control measure as much as a tracking measure. Run the character count on the final message with the short link in place, not on the draft with a placeholder, because the placeholder always lies about length.
Attribution has a limit you should know before you promise numbers to anyone. Without UTM values, GA4 attributes SMS clicks as direct traffic, because a text message carries no referring URL the way a web page does. With UTM values, the click is attributed, but the SMS platform click count and the GA4 session count will still disagree, because some recipients tap and bounce, some block tracking, and some open the link in an in app browser that behaves differently. Report the two numbers side by side and explain the gap. A report that pretends they match is a report nobody should trust.
The naming rule I would write on the wall
Lowercase only, underscores instead of spaces, one source value forever, and a campaign name that a stranger could understand in six months. Write it down where the whole team can see it, because the person who breaks the rule is rarely the person who wrote it. They are the new hire, or the agency contractor, or you on a busy Friday. And one question I leave open: whether source should be sms or the name of your SMS platform. Platform names are more precise, but sms survives a platform change, and I have watched a team migrate platforms and lose a year of comparable data because their source value moved with the vendor. For now, I keep sms, and I let the platform keep its own click data.
Frequently asked questions
What UTM parameters should I use for SMS?
Use utm_source=sms, utm_medium=sms or text, and utm_campaign for the specific send. Add utm_content to separate two links or message versions in the same campaign. Utm_term is optional and most SMS campaigns skip it.
Should I shorten a UTM link before or after tagging?
Tag first, then shorten. The short link must point at the full tagged destination, so the UTM values arrive intact when the reader taps it.
Does case matter in UTM parameters?
Yes. GA4 treats SMS and sms as different sources. Use lowercase consistently, or one stray capital letter will split your report.
Why does SMS traffic show as direct in GA4?
A text message carries no referring URL, so without UTM values GA4 has no source to attribute the visit to and records it as direct traffic.
Why do SMS platform clicks and GA4 sessions disagree?
Some recipients tap and bounce, some block tracking, and some open links in in app browsers that behave differently. Report both numbers and explain the gap rather than forcing them to match.
Related reading: UTM Parameters for Email Marketing · UTM Parameters and Case Sensitivity · Why Your UTM Parameters Are Not Showing in GA4 · UTM Naming Conventions That Survive a Growing Team