iOS 14 attribution for ecommerce: what still works
How App Tracking Transparency, Safari tracking prevention and Link Tracking Protection affect Shopify ad attribution, and what still links orders to ads.
By DATALYR · · 3 min read
Contents
What iOS changed for store owners
Since iOS 14.5, apps must ask permission before tracking people across other companies' apps and websites, and a person who declines blocks the app from using their advertising identifier or other identifying details for tracking. For ecommerce, that reduced what ad platforms can observe inside their own apps after someone taps an ad and lands on your store.
Safari added its own limits on cookies and click IDs. Together they make browser-only attribution less complete on Apple devices. The order record and first-party data captured at the moment of the visit are what still hold up.
App Tracking Transparency in plain terms
ATT governs apps, not websites. Your Shopify store is a website, so ATT does not stop your pixels from loading. It changes what Meta, TikTok and other apps can do with activity that happens after their in-app browser sends someone to you.
Ad platforms leaned more on modeled reporting and on server-to-server conversion APIs. That is why platform numbers can include estimated conversions, and why sending verified orders from the server became standard practice for stores.
A related detail: many ad clicks open inside the Instagram, Facebook or TikTok in-app browser. If the buyer later opens your store in Safari to pay, the two browsers share no cookies.
Safari limits on cookies and click IDs
WebKit's tracking prevention deletes cookies created by JavaScript, and other script-writable storage, after seven days without a visit to the site. When a visitor arrives from a link decorated with click IDs from a domain WebKit classifies as a tracker, it caps cookies created by JavaScript on that landing page to 24 hours.
Link Tracking Protection, introduced with iOS 17, removes tracking parameters from links shared in Messages and Mail and from links opened in Safari Private Browsing. Reports from marketers testing it found click IDs such as fbclid and gclid removed. Apple does not publish the exact parameter list.
Illustrative example. A shopper taps a Meta ad on Monday at 9:00, lands on your store in Safari, and buys on Thursday at 9:00 after typing your URL. If the _fbc cookie was set by JavaScript on that landing page under the 24-hour cap, it expired on Tuesday at 9:00, 48 hours before the purchase. The Thursday purchase event has no click ID unless it was saved elsewhere.
Why a 72-hour purchase loses a 24-hour cookie (illustrative)
1. Monday 09:00
Ad click lands
fbclid in the URL; _fbc set by JavaScript.
2. Tuesday 09:00
Cookie cap reached
24 hours after the decorated landing.
3. Thursday 09:00
Purchase
72 hours after the click; the browser no longer holds _fbc.
What still links an order to an ad
The click ID is still in the URL when the visitor lands, unless something stripped it first. Capture it on that first page view and store it with the visit on your side, and a purchase days later can still be linked to it, as long as the visit and the order can be joined.
On Shopify, the join can travel with the cart. Shopify carries cart attributes onto the order, so an identifier written into the cart reaches the paid order through Shopify's own webhook, with no dependence on a browser event firing on the Thank you page.
The customer's email is the other durable key. Ad platforms match hashed email and phone, and those do not expire with a cookie. Collecting email early and sending it hashed with the conversion recovers matches that cookies alone lose.
How DATALYR handles it on Shopify
DATALYR records the click ID with the visit when the visitor lands. On Shopify, the App Embed writes the DATALYR visitor ID, the _fbc and _fbp cookies and the raw fbclid with its arrival time into the cart. Shopify carries them onto the order, and DATALYR resolves the visitor from them, then from the order email, then from click IDs in the order's landing URL.
When it sends the Meta conversion, DATALYR builds fbc from the time the fbclid first arrived, not the purchase time, and adds hashed email and phone when known. Inside the Instagram, Facebook and TikTok in-app browsers, the web SDK can carry the visit across when the visitor opens the page in their own browser.
Related articles.
Tracking ·
Server-side tracking: architecture, responsibilities and limits
Understand what moves to the server, what still depends on browser identity, and how to verify one conversion without creating duplicate events.
Tracking ·
First-party data: build an inspectable marketing measurement record
Inventory the data your business collects directly, separate measurement from advertising sharing, and verify each field’s purpose and destination.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
