Conversion tracking is the practice of recording the valuable actions people take after seeing or clicking your ad, such as a purchase, a lead form or a sign-up, and tying each action back to the ad that led to it. In Meta ads it is what lets Ads Manager report results, and what gives Meta's delivery system something to learn from.
The three layers of tracking on Meta
| Layer | Where it runs | What it does |
|---|---|---|
| Meta Pixel | The visitor's browser | Records actions on your website as events |
| Conversions API | Your server, platform or CRM | Sends the same events to Meta without relying on the browser |
| Madgicx Cloud Tracking | A hosted server setup | Sends conversions to Meta from the server for you |
Meta describes Events Manager as the place to view and manage your event data, and to set up, monitor and troubleshoot integrations such as the Conversions API and the Pixel. It is where you check that tracking works. Our Events Manager entry covers its menus.
Let Madgicx's AI do the work
Its AI marketer finds what's working and prepares the next move. You approve.
Try for Free ($0 Trial)How a conversion gets counted
- Someone sees or clicks an ad.
- They take an action on your site, in your app or in a conversation with your team.
- The Pixel, the Conversions API or both send an event, such as Purchase, to Meta.
- Meta matches the event to a person who saw or clicked the ad.
- If the action falls inside the attribution window, Ads Manager reports it as a result for that ad.
When the same action arrives from both the browser and a server, deduplication keeps it from being counted twice.
What to set up first
- Pick the actions that matter. Track the end goal, such as a purchase or a booked call, plus the steps before it, so you can see where people drop off.
- Send value and currency. A purchase without them can't feed ROAS reporting.
- Add the server connection. Send the same events through the Conversions API, so a blocked browser doesn't hide a sale.
- Tag your links. UTM parameters show your analytics tool which ad each visit came from, so you can compare Meta's numbers with your own.
- Test before you spend. Trigger each event yourself and confirm it appears in Events Manager once.
Common mistakes
- Counting the wrong action. Optimizing for page views or button clicks tells Meta to find people who click, not people who buy.
- Two installs of the Pixel. A theme and a plugin that both add it count each event twice.
- Browser-only tracking. Ad blockers and privacy settings stop some browser events. Server-side tracking covers part of that gap.
- Trusting one source. Ads Manager, your analytics tool and your store will never match exactly, because each counts differently. Compare trends and gaps, not single numbers.
Example. A dental clinic runs ads for new-patient bookings. Its booking page has the Pixel, but ads report 40 bookings a month while the front desk logs 55. The clinic adds the Conversions API with a shared event ID for each booking, and fixes a form that fired the event before the patient picked a time. Ads Manager and the front desk now differ by a few bookings, which the team puts down to people who booked by phone.
In Madgicx. Madgicx Cloud Tracking hosts Meta's Conversions API Gateway and Signals Gateway for you and sends conversions to Meta from the server. Meta's AI can only optimize on the conversions it can see, so Madgicx aims to let Meta see and attribute more of them.
FAQ
What is conversion tracking in Facebook ads?
It is the setup that records what people do after an ad, such as buying or filling in a form, and reports it in Ads Manager. On Meta it runs through the Meta Pixel, the Conversions API or both.
How do I set up conversion tracking on Meta?
Create a Pixel in Events Manager, add it to your site with the key events, then add the Conversions API for the same events. Check Events Manager to confirm each event arrives once, then place a test order.
What is the difference between a conversion and conversion tracking?
A conversion is the action itself, such as a purchase. Conversion tracking is the system that detects and reports that action.
Why does Meta show fewer conversions than my store?
Some browser events never reach Meta, and platforms count and attribute orders differently. Adding the Conversions API and fixing duplicate or missing events usually narrows the gap, though it rarely closes it fully.
Do I need both the Pixel and the Conversions API?
Meta recommends sending the same events through both, then deduplicating them. The Pixel covers browser actions, and the Conversions API covers what the browser misses.
Related
- Related terms: Meta Pixel, Conversions API, Deduplication, Server-side tracking
- In depth: Facebook Pixel guide
Sources
- About Meta Events Manager, Meta Business Help Center
