Every campaign on Meta, TikTok or Google works on the same principle: you send the platform a signal when someone performs the action you want (a purchase, a sign-up, an order), and the algorithm looks for more people like them. The quality of those signals is the quality of the learning. If they are incomplete, no campaign setup makes up for it.

What is the pixel?

The pixel is a small piece of code on your site that runs inside the visitor's browser. When they buy or sign up, the pixel sends the event to the platform directly from the browser.

The problem is that the browser has become an unreliable place to send signals from:

  • iOS privacy changes restricted tracking in apps and browsers (see Apple's user privacy and data use guidance).
  • Ad blockers and browser privacy settings sometimes stop the pixel from firing.
  • Slow pages: if the visitor closes the page before the pixel loads, the event is lost.

The result: part of your real sales never reaches the platform, and the algorithm learns from an incomplete picture.

What is the Conversions API?

The Conversions API (CAPI) sends the same events from your server instead of the browser. When an order is recorded in your store's system, the server sends the event directly to Meta. No ad blockers, no dependence on the page loading. Meta's own documentation is on the Conversions API developer page.

TikTok's equivalent is the Events API, and Google offers enhanced conversions and conversion imports.

Why you need both

The current recommendation is to run the pixel and the Conversions API together. The pixel captures browser signals, the server captures what the pixel misses. But that creates a new problem: the same purchase can be recorded twice.

Deduplication

For Meta to know that the event from the pixel and the event from the server are the same purchase, both must carry the same event name and the same event ID (event_id). Without that, sales are counted twice, campaigns look better than they are, and you make decisions on doubled numbers. Meta explains the rules in deduplicating pixel and server events.

Check it in Events Manager: if server and browser events are not being merged, you have a problem.

Event match quality

When an event arrives, Meta tries to match it to a user on its platform. The more data you send (such as hashed email and phone, and browser identifiers), the more accurate the match. Meta shows a quality score for this on each event in Events Manager.

Poor matching means part of your sales is attributed to no one, so the algorithm cannot learn from it.

More important than the technology: which event you send

Correct tracking of the wrong event does not help. Examples from real accounts:

  • On a cash-on-delivery store, sending "purchase" at order submission rewards phantom orders. Better to add an event at order confirmation or delivery. Details in reducing COD returns.
  • On a services app, optimising for installs brought people who install and delete. Moving optimisation to the activation event cut cost per active user from SAR 95 to SAR 21. See app install campaigns.
  • At a contracting company, sending lead status (qualified or not) back to the platform made it look for more qualified-looking prospects. See qualified leads.

The server lets you do something the pixel cannot: send events that happen off the website, such as order confirmation or a closed deal. That is often the most important use of the Conversions API.

Quick tracking checklist

  1. Does the pixel fire on every important page? (Use Meta Pixel Helper.)
  2. Is the Conversions API enabled? (From your store settings, a partner, or a direct integration.)
  3. Are duplicate events merged with a shared event ID?
  4. What is the event match quality for your purchase event?
  5. Is the event you optimise for the result you actually want?
  6. Are platform numbers close to real sales? A large gap in either direction means a problem.

The bottom line

Before changing targeting, creative or budget, make sure the platform sees what is really happening. Tracking is not a technical detail to leave to a developer; it is the foundation every campaign decision stands on. Any serious media buyer starts here.

If you want the tracking in your ad accounts reviewed, get in touch from the freelance media buyer page.