Full Answer

The tracking loss stack is not a single failure — it is a filter chain. Each privacy or technical layer removes a percentage of visitors that the previous layer did not already block. A session that survives the ad blocker may still lose its cookie to ITP, have its click ID stripped by iOS 26, or never fire a consent-gated tag in the EU. The layers do not cancel each other out. They compound.

Here is how they stack in practice. Ad blockers affect roughly 31.5% of global users and suppress client-side tags entirely for those visitors. Safari ITP caps first-party JavaScript cookies at seven days, which breaks any attribution window longer than a week. iOS 26 now strips gclid, fbclid, and msclkid from all standard Safari sessions — not just Private Browsing. In the EU, consent rejection rates run between 40 and 70%, meaning tags that require consent never fire for the majority of European visitors. In-app browsers from Instagram and TikTok add another layer by breaking cross-domain tracking and suppressing third-party cookies.

The compounding effect is what makes this different from a single-cause problem. Fixing ad blockers alone does not recover the sessions lost to ITP or consent rejection. Each layer needs its own mitigation, and [server-side event capture](https://seresa.io/blog/data-loss/ad-blocking-didnt-peak-1-77-billion-users-entrenched-in-2026) addresses the largest share by moving event collection out of the browser entirely.