Stocky has shut down. Recover what you can and replace it free
Maintained benchmark · Last verified 2 July 2026 · Every figure sourced

The iOS attribution gap is
yours
to measure — not ours to average.

This benchmark documents how iOS App Tracking Transparency and Safari ITP remove purchase-conversion signal from Shopify stores, and what determines the size of that loss for any one store. It publishes the sourced third-party figures behind the mechanism rather than a single headline percentage, released under CC BY 4.0 with machine-readable JSON and CSV.

Apple's App Tracking Transparency and Safari ITP block the browser signals Meta, Google and TikTok depend on. How much any one store loses is set by its own mobile/iOS traffic mix and its own consent rate — which is why this page publishes the sourced evidence and a way to measure your store, rather than an industry average that describes nobody. Below: the sources, the method, and how to close the gap.

Free to read and cite (CC BY 4.0). The fix is documented at CAPI Shield.

~75%
iOS tracking opt-out, 2021 ATT launch (~50% by 2024–25)
7 days
Safari ITP cookie cap
74–78%
Shopify traffic is mobile
~$10B
Meta's own estimated 2022 ATT revenue hit
the evidence · verified 2 July 2026

What the published research actually shows

The 5 figures below are load-bearing: each comes from a named, dated, linked source. Together they bound the size of the gap.

iOS users who declined app tracking (opt-out) — 2021 launch
~75–80%

In the months after the April 2021 ATT prompt, most iOS users declined app tracking; early panels put opt-in in the low-20s%. Note: opt-in has since risen — AppsFlyer's global panel reported ~50% opt-in by 2024–2025 — so current app-tracking loss is lower than the 2021 launch figure. Web pixel loss (the basis of this benchmark) is driven by Safari ITP, ad blockers and consent rejection in addition to ATT.

Source: AppsFlyer — ATT opt-in rate data (2021 launch vs 2024–25 anniversary) · Apr 2025 ↗
Share of Shopify traffic that is mobile
74–78%

Mobile devices drive roughly three-quarters of Shopify store traffic — the exact segment most affected by iOS/Safari tracking restrictions.

Source: Shopify Mobile Commerce Statistics 2026 · Apr 2026 ↗
Attributable conversions lost relying on platform SDK alone (no CAPI)
~40%

A documented case found a brand losing approximately 40% of attributable conversions by relying solely on the platform's SDK without a server-side Conversions API complement.

Source: 021 Newsletter — Do You Still Need an MMP in 2025? · Jul 2025 ↗
Meta's own estimated 2022 revenue impact from ATT
~$10B

On Meta's Q4 2021 earnings call (Feb 2022), CFO David Wehner told analysts the iOS ATT headwind was 'on the order of $10 billion' for 2022 — roughly 8% of annual revenue. Meta reaffirmed the ~$10B order of magnitude on its Q2 2022 call.

Source: Meta Q4 2021 earnings call (David Wehner), via MacRumors · Feb 2022 ↗
Safari ITP: first-party cookie lifetime cap
7 days

Safari's Intelligent Tracking Prevention caps script-writable first-party cookies at 7 days and blocks third-party cookies entirely — structurally degrading browser-based attribution for the ~50%+ of Shopify mobile traffic on iOS Safari, independent of ATT opt-in trends.

Source: WebKit — Tracking Prevention (Apple) · Ongoing ↗
the synthesis

The Stack Architect Attribution Gap Index

No single published source states "the Shopify attribution gap is X%." This page used to answer that by synthesising one — a 20–40% range, rising to 50% on mobile-heavy stores, triangulated from the figures above. That range was withdrawn on 4 September 2026. It is documented below rather than quietly removed, because it was cited from here.

The inputs themselves are unchanged and still stand. Mobile is 74–78% of Shopify traffic, a large share of it iOS; ATT removed app-tracking consent for most of those users at launch (~75% opt-out in 2021, easing to roughly 50% by 2024–25); and Safari ITP independently caps script-writable first-party cookies at 7 days, degrading browser attribution regardless of ATT consent. Documented store-level cases land near 40% conversion loss without CAPI.

What that set of figures establishes is a mechanism and its drivers — not a magnitude. Two of the five rows are store variables rather than constants: the mobile/iOS share of your traffic, and the rate at which those visitors decline tracking. A store at the top of the mobile range with a high refusal rate and a store at the bottom with a low one do not share a number, and the average of the two describes neither. Only one row was even denominated in the retracted quantity — a single documented case, reported at second hand — and nothing in the evidence table derives the lower bound of 20% at all. So the range is gone rather than re-derived, and the sourced rows it was built from remain above, individually citable.

Revision, 3 September 2026. An earlier version of this table carried a sixth row citing a 30–40% reduction in Meta attribution accuracy, attributed to an AI answer library. That source does not meet the standard set out in how we test, which excludes AI-generated statistics, and we could not locate a primary source for the figure. The row has been removed. It was one of the inputs behind the headline range, and narrowing that evidence base is part of what led to the range being withdrawn outright a day later.

Yours

The only gap figure worth acting on is your store's, and it is two numbers you already have: conversions your ad platform reported last month, against paid orders Shopify recorded for the same period. Work it out below — you get the result immediately, and submitting it anonymously is what will let this page publish a first-party figure.

Everything above is published third-party figures, each named, dated and linked — not proprietary primary data, and no longer resolved into a headline of our own. The original contribution this page can honestly make is first-party: a figure measured from real stores, published as "based on N stores" once the sample supports it.

methodology

How this benchmark is built and maintained

  • Every figure in the evidence table is drawn from a named, dated, publicly accessible third-party source and linked directly. No figure is invented or un-attributed.
  • The headline range is a transparent triangulation of those inputs, presented as a synthesis — explicitly not as proprietary measurement.
  • The page is re-verified periodically; the "last verified" date at the top reflects the most recent check. Figures and sources are updated as newer research is published.
  • Store submissions (below) are stored anonymously and in aggregate only. No store name or identifying data is published. Once the sample is large enough to be meaningful, a first-party figure is added alongside the synthesised range.
  • Spot an out-of-date figure or a better source? Tell us — corrections are welcomed and dated.
build the data

Contribute your store's gap

Anonymous. Two numbers from your own dashboards. Helps turn this synthesis into original first-party data the whole industry can cite.

of 10 stores needed to publish

Loading current count…

Stored anonymously and in aggregate. We never publish individual store data or any identifying detail. Your two numbers join the dataset that produces a future first-party benchmark.

citing this data

Cite this benchmark

Writing about iOS, ATT or Shopify conversion tracking? You're welcome to cite this benchmark. Suggested attribution:

Shopify purchase-conversion signal lost to iOS ATT and Safari ITP is store-specific, driven by a store's mobile/iOS traffic mix and its consent rate (Stack Architect Attribution Gap Benchmark, 2 July 2026). — stackarchitect.xyz/shopify-ios-attribution-gap-benchmark

Download the underlying data (every row sourced and dated, CC BY 4.0): CSV · JSON. Both files are generated from the same data as this page at build time, so they can never drift from the published table.

Released under CC BY 4.0 — free to quote with a link. Publications wanting the full source list: every figure is linked in the evidence table above.

Luke Sandelands
Written by Luke Sandelands
Founder, Stack Architect · Shopify Automation Specialist
Developer of StockLog and author of the open-source shopify-capi-validator npm package. Certified in Shopify server-side tracking, Meta CAPI, and Google Apps Script engineering.
Full profile and credentials · Last reviewed
FAQ

Common questions

What is the iOS attribution gap for Shopify stores?

The iOS attribution gap is the share of real purchases that ad platforms like Meta, Google and TikTok fail to attribute because Apple's App Tracking Transparency (ATT) and Safari Intelligent Tracking Prevention (ITP) block the browser signals those platforms rely on. Its size is store-specific: it is set by how much of your traffic is mobile and iOS, and how many of those visitors decline tracking. This page publishes the sourced figures behind the mechanism, and a calculator that turns two numbers from your own dashboards into your own gap.

How is the Stack Architect Attribution Gap Index calculated?

It is a transparent synthesis of published third-party figures — ATT opt-out rates (~75% at the 2021 launch, ~50% by 2024–25), the mobile share of Shopify traffic (74–78%), Safari ITP's 7-day cap on script-writable first-party cookies, and documented conversion-loss case data (~40% without CAPI). We do not present this as proprietary primary data; every input is named, dated and linked in the methodology. The index no longer resolves those inputs into a single headline percentage — that synthesis was withdrawn in September 2026, because none of the inputs measures it and two of them show the quantity is store-specific. What the inputs bound is the mechanism, not a number. A first-party figure is published here once enough real store submissions accumulate to compute one.

Why does server-side tracking (CAPI) close the gap?

Server-side tracking sends the purchase event from the store's server directly to the ad platform's Conversions API — bypassing the browser entirely, so iOS and ad blockers cannot strip it. With hashed first-party data (email, phone) attached, the platform can still match the sale to the click even when the device identifier is gone. This is why brands with clean CAPI pipelines materially out-recover those relying on browser pixels alone.

Can I cite this benchmark?

Yes. This page is maintained and dated specifically so it can be cited. Use the suggested attribution in the "Citing this data" section, and link to https://stackarchitect.xyz/shopify-ios-attribution-gap-benchmark/. If you represent a publication and want the underlying source list, every figure is linked in the methodology table.

Related guides and tools from Stack Architect.

GA4 vs Shopify revenue reconciler →Meta EMQ score estimator →Shopify vs Meta attribution gap calculator →

Embed this live benchmark

Writing about iOS tracking loss, ATT, or Shopify attribution? Embed the live figure — it updates automatically as more stores contribute. Copy the snippet (the source line keeps the data attributed):

<iframe src="https://stackarchitect.xyz/embed/gap-index/" width="360" height="220" style="border:0;border-radius:14px" loading="lazy" title="Shopify iOS Attribution Gap — live benchmark"></iframe>
<p style="font-size:.85em">Source: <a href="https://stackarchitect.xyz/shopify-ios-attribution-gap-benchmark/">Shopify iOS Attribution Gap — first-party benchmark by Stack Architect</a></p>