Meta Pixel and Conversions API: A Setup Guide

Almost every Meta account we look at has a Pixel installed.

Rather fewer have one that reports correctly.

And the accounts that added the Conversions API without deduplicating events are in the worst position of all — they now have two sources confidently reporting the same purchase, and a reported return on ad spend that is roughly double reality.

What each one does

They are not alternatives. The Pixel sees things the server does not, and the server sees things the browser cannot report. Meta expects both.

Deduplication — the step that breaks silently

Once both are sending, Meta receives two reports of the same purchase. It needs a way to recognise them as one.

That is deduplication, and it works on two matching values: the event name and the event ID. Send the same pair from browser and server and Meta pairs them. Send a different ID from each and it counts two purchases.

1. Generate one event ID per action — not per page load. The same purchase must carry the same ID in both places.
2. Send identical event names. "Purchase" from the Pixel and "purchase" from the API will not pair.
3. Pass the ID to both. This is the part custom implementations get wrong; the ID is generated in one place and never reaches the other.
4. Verify in Events Manager. Deduplicated events are labelled as such. If nothing is being deduplicated, nothing is being paired.
5. Complete a real transaction yourself. One purchase, one event. If you see two, it is not working, whatever the setup guide said.
6. Re-check after every site change. Theme updates, checkout changes and plugin updates all break this quietly.

Which events to set up

The temptation is to implement every standard event. Resist it.

Every event you send is something the delivery system could be told to optimise toward. A cluttered event set makes it easier to optimise for the wrong thing.

Start with the one that represents money. Purchase for e-commerce. A qualified lead for services — not a form submission, which is a different and much weaker thing, as covered in Meta lead ads.

Then the steps before it, so you can see where people drop out. View content, add to cart, initiate checkout for e-commerce. For services, the step that separates a serious enquiry from a casual one.

Send accurate values. If you are targeting return on ad spend, the value on the purchase event has to be the real order value. A flat placeholder makes every ROAS figure meaningless, and a good ROAS becomes impossible to judge.

What the Pixel powers beyond reporting

It is easy to think of tracking as a measurement job. It is also the input for two things that decide performance.

Optimisation. The delivery system finds more people like the ones who triggered your conversion event. Feed it the wrong event and it will get very good at finding the wrong people, confidently and at scale.

Audiences. Every remarketing audience and every lookalike is built from Pixel and API data. Broken tracking means thin audiences, which means expensive delivery — usually diagnosed as a targeting problem when it is a measurement one.

The checks worth running quarterly

• Test Events in Events Manager, with a real transaction. Not a test mode click.
• Event Match Quality — Meta grades how well it can match your events to people. Passing more customer parameters from the server side improves it.
• Deduplication status — confirm events are being paired, not just received.
• Diagnostics tab — it flags missing parameters and dropped events, and nobody reads it.
• Reconcile against your own numbers — Meta-reported conversions against your back office for the same window. A persistent gap is a problem, in either direction.

None of this is glamorous, and all of it comes before campaign work. Launching before tracking is verified is the most expensive sequencing error available in paid media — the same point made in Facebook Ads structure and in conversion tracking.