The Problem: Ad Was Clicked, Sale Happened — But the System Couldn’t See It
Meta ads ran for years on a small piece of code called the Pixel. It fired in the browser whenever a visitor landed on your site, telling Meta: “this person clicked your ad, then made a purchase.” In 2021, Apple started asking iPhone users whether they wanted to be tracked — and most said no. That meant the Pixel could no longer see purchases made by iPhone Safari users. According to Meta, the change significantly reduced the number of conversions that showed up in reporting. Your ad was making sales; the system just couldn’t measure them properly anymore.
The Fix: Send the Data From the Server Instead
Conversions API doesn’t replace the Pixel — it works alongside it. While the Pixel operates at the browser level, CAPI sends data directly from your website’s server to Meta. Even if the browser is blocked, cookies are cleared, or someone is browsing inside an app, the server-side connection still captures the event. When a customer completes checkout, that information is logged on the server and forwarded to Meta — not just through the browser. When Pixel and CAPI run together, the system matches events to avoid double-counting (a process called deduplication), so your measurement is both more complete and cleaner.
Typical improvement in measured conversions when Pixel and Conversions API are used together, based on Meta-published case studies.
- Lost iPhone purchases become measurable again — Safari’s privacy protections no longer block the data.
- Ad optimisation improves: Meta’s AI (Advantage+) gets more real purchase signals to work with, leading to better targeting.
- You can more clearly see which ad actually drove sales — a cleaner answer to ‘what am I getting for my ad spend?’
- Privacy compliance is maintained: personal data travels encrypted from your server, not through the browser.
- Retargeting audiences grow larger: visitors the Pixel missed can now be added to your lists.