Stop optimizing on half the data
The algorithm is only as smart as the conversions you report to it. Since iOS 14.5, the browser pixel alone misses a large share of sales, so delivery optimizes on a thin, distorted picture. We rebuild measurement with the Meta Pixel and the server-side Conversions API, tune Event Match Quality, and validate every event so the system learns from real outcomes.
Why pixel-only tracking fails now
Apple's App Tracking Transparency prompt changed the math. Across prompted users, only about 25% opt into tracking (Flurry), so a browser pixel sees a fraction of what it once did. Industry estimates of iOS conversion-signal loss commonly land between 30% and 60%, depending on traffic mix. The result is under-reported conversions, conservative bidding, and an algorithm that cannot find more buyers because it never saw the last ones.
What we rebuild
Meta Pixel + CAPI
Browser pixel paired with server-side Conversions API, with events deduplicated so nothing double-counts.
Event Match Quality
Hashed first-party data passed through to raise match quality, which directly feeds delivery.
Server-side tracking
Google Tag Manager server-side or native, configured to your platform and checkout.
Events Manager hygiene
Clean event setup for the post-eight-event, AEM-era system, validated and monitored.
What changed in measurement, and what we ignore
Meta's measurement rules keep moving. As of mid-2025, the old eight-event limit and manual event-prioritization workflow are gone, and domain verification is no longer required for conversion processing (platform changelog). Aggregated Event Measurement still operates quietly for opted-out iOS users. We set up tracking for how the system works today, not for a guide written three years ago.
Clean data is the foundation everything else stands on. It makes our Meta ads management scaling decisions trustworthy and tells our creative testing which ads truly drove revenue. One representative home and lifestyle brand cut cost per acquisition by 34% in 60 days, largely by rebuilding tracking before touching anything else.
Tracking & attribution FAQ
What is the Conversions API and why do I need it?
The Conversions API (CAPI) sends conversion events from your server directly to Meta, instead of relying only on the browser pixel. Since iOS 14.5, only about a quarter of prompted users opt into tracking (Flurry), so pixel-only data is thin. CAPI restores much of that signal and raises Event Match Quality, which feeds better delivery.
How much tracking did iOS 14.5 actually break?
Enough to matter. With roughly a quarter of prompted users opting in, browser-side measurement misses a large share of conversions, and industry estimates of iOS signal loss commonly range from 30% to 60%. The exact figure depends on your traffic mix, which is why we measure your account before and after the rebuild rather than quoting a blanket number.
Do I still need to verify my domain and pick eight events?
Largely no, as of mid-2025. Meta removed the eight-event limit and the manual event-prioritization step, and domain verification is no longer required for conversion processing (Conversios). Aggregated Event Measurement still runs behind the scenes for opted-out iOS users. We configure events for the current system, not the 2021 one.
How do you set up server-side tracking?
Either through Google Tag Manager server-side or a native integration with your platform, depending on your stack. We deduplicate pixel and CAPI events, pass hashed first-party data to lift Event Match Quality, and validate everything in Events Manager so you can see the signal improve.