1. Home
  2. /
  3. Resources
  4. /
  5. How iOS 14.5, App Tracking Transparency, and cookie deprecation cut into US ad signal
Article

How iOS 14.5, App Tracking Transparency, and cookie deprecation cut into US ad signal

Taoufik El Jamali
Taoufik El Jamali
Journify
July 13, 2026 5 min read
Share
How iOS 14.5, App Tracking Transparency, and cookie deprecation cut into US ad signal

Three separate changes, not one, are responsible for most of the signal loss US e-commerce brands are running into today: Apple's App Tracking Transparency prompt, the long, uneven death of the third-party cookie, and a growing stack of state privacy laws that require consent before tracking. Each one closed off a different slice of what a browser pixel used to see. Together, they explain why browser-only tracking in the US now commonly misses 30 to 40% of real conversions, quietly, with no error, no alert, nothing in the dashboard that says why.

Treating this as one problem with one fix is the mistake. It's three structural changes stacked on top of each other, and each one needs to be understood on its own before anyone can talk seriously about fixing the gap.

What's causing signal loss for US e-commerce brands right now?

Three changes, stacked together: Apple's App Tracking Transparency prompt removed IDFA from most iOS devices since 2021, third-party cookie blocking by Safari and Firefox removed persistent browser identity, and state privacy laws like California's CPRA added consent-driven opt-outs on top of both. Together they account for the 30 to 40% of conversions browser-only tracking misses in the US today. Closing that gap means capturing conversions server-side instead of depending on the browser pixel, which is what ad signal infrastructure platforms like Journify are built to do.

What iOS 14.5 and App Tracking Transparency actually changed

Since April 2021, iOS has required apps to ask explicit permission before tracking a user across apps and websites owned by other companies. That's the App Tracking Transparency prompt, and industry-wide opt-in rates have stayed low. Most iOS users never grant it.

The practical effect: IDFA, the device identifier Meta, TikTok, and Snap relied on to link an ad click to a conversion, is unavailable for most of the iOS install base. Ad platforms didn't lose the ability to run campaigns. They lost the identifier that let them connect what happened on the app or website back to the ad that caused it. Every platform running ads to iOS users has been operating with a partial picture since 2021, and the gap hasn't closed on its own.

Safari has blocked third-party cookies by default since 2020 under Intelligent Tracking Prevention. Firefox did the same under Enhanced Tracking Protection. Chrome's own timeline has shifted more than once, but the direction across every major browser has been the same for years: third-party cookies, the mechanism browser pixels used to persist an identity across sessions and sites, are being switched off by default, not eventually, already.

A pixel that depends on a third-party cookie to recognize a returning visitor stops recognizing them the moment that cookie is blocked. That's not a future risk. For Safari and Firefox users, it's already the default state of the browser.

Why this compounds specifically in the US

GCC brands deal with consent requirements too, but the US adds a layer that's easy to underweight: state privacy law. California's Consumer Privacy Act and its expansion under the CPRA require businesses to honor opt-out requests for the sale or sharing of personal information used in targeted advertising, and Virginia, Colorado, and a growing list of other states have followed with their own versions. Every opt-out is another conversion a browser-only pixel will never see, on top of what ATT and cookie deprecation already removed.

Stack all three, IDFA loss on iOS, cookie loss on Safari and Firefox, and consent-driven opt-outs under state law, and a browser pixel in the US market is working with a fraction of the signal it had five years ago. That's the mechanism behind signal loss as a category: not a single bug, but the accumulated effect of tracking restrictions layered on top of each other. The 30 to 40% signal loss baseline isn't a rounding error. It's the sum of three separate, permanent structural changes.

What actually closes the gap

None of these three changes are reversible. Apple isn't bringing back IDFA by default. Browsers aren't reinstating third-party cookies. States aren't repealing privacy law. The fix isn't waiting for the environment to go back to how it was in 2019, it's building a data path that doesn't depend on the browser pixel being the only source of truth.

That means capturing conversions server-side, from the website, the app, the CRM, and offline sources, validating that data before it reaches an ad platform, and delivering it in real time so the platform's algorithm is learning from a complete picture instead of whatever fraction survived ATT, cookie blocking, and consent opt-outs. This is ad signal infrastructure, and it's the same problem whether the ad platform is Google, TikTok, Snap, or Amazon. It doesn't get solved by adjusting a campaign or a budget.

The brands that treat this as a data infrastructure problem, not a tracking inconvenience, are the ones whose ad platforms are actually learning from what's real. Everyone else is optimizing against a shrinking, incomplete signal and calling it strategy.

Taoufik El Jamali
Taoufik El Jamali
Journify

Taoufik El Jamali is CEO and Co-Founder of Journify. He has spent two decades building venture-backed products focused on growth and data infrastructure. At Journify, he is building the category for ad signal infrastructure across the GCC and US markets.

You might also find this useful

More from the Article series.