Every store owner has heard “iOS killed tracking.” It’s half true. iOS App Tracking Transparency (ATT), Safari’s Intelligent Tracking Prevention (ITP), and the broader death of the third-party cookie didn’t stop your ads from working — they broke attribution. Knowing the difference tells you exactly what to fix.
What actually breaks
- Your ads still run and still convert. Sales happen whether or not they’re perfectly tracked.
- Fewer conversions get attributed via the browser. When a user opts out of tracking or their browser blocks cookies, the platform can’t reliably connect the sale back to the click.
- Attribution windows shrink and view-through attribution suffers — so platform-reported conversions under-count real performance.
- Audience matching weakens — remarketing pools shrink as cookie-based identifiers expire faster.
The net effect: your Meta/Google dashboards show fewer conversions than really happened, ROAS looks worse than reality, and optimization runs on thinner signal. That’s an attribution problem, not a demand problem.
Why server-side + first-party data fixes it
Cookies were the old way to recognize a shopper. The recovery is to identify conversions with hashed first-party data you already have — email, phone, name — sent server-side, where ad blockers and ITP can’t intercept it:
| Lever | What it recovers |
|---|---|
| Conversions API (CAPI) | Sends conversions server-side, bypassing browser blocking |
| Event Match Quality | More hashed identifiers → more conversions matched to people (raise EMQ) |
| Enhanced Conversions (Google) | Uses hashed first-party data instead of cookies |
| Advanced Consent Mode | Models conversions from non-consenting EEA users (details) |
| Server-side tracking (sGTM) | The delivery layer for all of the above (verify it works) |
And through all of it, Shopify’s server-side order record stays your source of truth — it never depended on cookies in the first place. Reconcile everything against it.
The practical takeaway
Don’t try to “get cookies back.” Build the first-party stack: server-side tracking + CAPI + strong EMQ + Enhanced Conversions + Advanced Consent Mode, and judge performance against Shopify, not against a browser-attributed number that structurally under-counts.
FAQ
How did iOS ATT affect Shopify tracking? It let users opt out of cross-app tracking, so fewer conversions get attributed via the browser and platforms under-count — fixed with server-side + first-party data.
Do cookies still work? First-party cookies mostly do; third-party/cross-site tracking is increasingly blocked. Server-side + CAPI + Enhanced Conversions recover attribution.
How do I recover the lost conversions? CAPI with high EMQ, Enhanced Conversions, Advanced Consent Mode, and reconcile against Shopify.
Related
Sources
- Meta — About the Conversions API
- Google — About Enhanced Conversions
- Stape — Server-side tracking for Shopify