UTM Tracking Is Pretty Much Dead — What Replaced It — LiquidLift

Someone in r/shopify said it plainly last week: "UTM tracking is pretty much dead."

They're right. And most stores haven't adjusted.

What killed UTMs

UTM parameters — those ?utm_source=facebook&utm_medium=cpc strings you append to every ad link — were designed for a world where browsers cooperated with marketers. That world ended in 2021.

iOS App Tracking Transparency strips tracking parameters when users opt out. That's roughly 75% of iPhone users.

Safari's Intelligent Tracking Prevention actively truncates URL parameters it identifies as tracking-related. Your carefully crafted UTM strings get silently deleted.

Ad blockers prevent the JavaScript that reads UTMs from loading in the first place. The parameter is in the URL, but nothing on the page captures it.

Cross-device journeys break the chain entirely. A visitor clicks your ad on their phone (with UTMs), browses your store, then buys on their laptop (no UTMs). Shopify sees a direct visit.

The result: UTMs now capture maybe 40–50% of the journey. The rest is invisible.

The affiliate UTM nightmare

If UTMs are bad for paid ads, they're catastrophic for affiliate tracking. One Shopify merchant described it: "UTM mapping is the biggest pain, especially affiliate traffic — ~20–25% of revenue not showing up right."

Affiliate links pass through redirects, link shorteners, social media platforms, and messaging apps — each one a potential point where the UTM gets stripped, rewritten, or lost. You end up manually mapping UTMs to figure out what came from where, and you're always wrong by a quarter of your revenue.

What actually works now

The stores and agencies that have moved past UTMs use a layered approach:

Server-side event tracking (CAPI)

Instead of relying on browser-side JavaScript to read URL parameters, server-side tracking sends conversion data directly from your server to ad platforms. No browser involved, no ad blocker interference, no iOS stripping.

Meta's Conversions API (CAPI) is the most common implementation. When a purchase happens on Shopify, your server sends the event — with customer identifiers, order value, and deduplication keys — directly to Meta. The pixel can be blocked. The server can't.

First-party session tracking

Rather than trusting a URL parameter to survive the journey, assign a first-party session ID the moment someone lands on your store. Link that session to every subsequent action: page views, add-to-cart, checkout, purchase.

This works because first-party cookies (set by your own domain) survive where third-party tracking parameters don't. The session chain stays intact across pages, across actions, and through most privacy restrictions.

Platform-reported metrics for relative comparison

Meta, Google, and TikTok all have their own attribution models. They all over-report. But they over-report consistently — so they're still useful for comparing campaigns, creatives, and audiences within each platform.

Use platform dashboards for "which campaign is better?" Use your own server-side data for "how much did I actually make?"

MER as the unifying metric

Marketing Efficiency Ratio — total revenue ÷ total ad spend — doesn't need UTMs, doesn't need attribution models, and doesn't break when iOS updates. It tells you one thing: for every pound you spend on marketing, how many pounds come back.

It's blunt. It doesn't tell you which channel is responsible. But it's the only metric that's immune to tracking degradation.

The practical shift

If you're still building your attribution strategy around UTMs, you're building on sand. The shift is:

From: URL parameters read by browser JavaScript
To: Server-side events sent directly from your backend
From: Last-click attribution based on which UTM was present
To: Session-based attribution linking the full visitor journey
From: Trying to get one "true" number
To: Accepting that signal recovery is the game, and better signal means better ad performance

UTMs aren't completely useless — they still work for some traffic on some browsers. But they're no longer the backbone. Server-side tracking is. And the sooner your store makes that shift, the sooner your ad platforms have enough data to actually optimise.