The Meta Pixel alone no longer sees your whole funnel. Ad blockers stop it, iOS limits it, and browsers delete its cookies. Meta’s Conversions API (CAPI) fixes that by sending events from your server instead of the visitor’s browser. But a rushed CAPI setup can be worse than none at all, because duplicate and mismatched events teach Meta’s algorithm the wrong lessons.
Here is the setup in the order we run it, with the checks that matter at each step.
Before You Start
You need four things ready: a Meta Business account with admin access, the Pixel (dataset) you will send events to, admin access to your website or tag manager, and a decision about how the server events will be sent. The common routes are a server-side Google Tag Manager container, the Conversions API Gateway, or a native integration from your platform, for example the Facebook app on Shopify. Any of them can work. Mixing them carelessly is where duplicates come from.
The Checklist
1. Confirm The Browser Pixel Is Healthy First
CAPI is a second signal, not a replacement for a broken first one. Check that your Pixel fires PageView and your key events correctly with Meta Pixel Helper before you add anything server-side.
2. Verify Your Domain In Business Settings
Domain verification in Meta Business Settings unlocks event configuration and protects your setup. Do it before you send events, not after something breaks.
3. Create The Access Token Carefully
In Events Manager, open your dataset settings and generate a Conversions API access token. Treat it like a password: it goes into your server configuration, never into emails, documents, or screenshots.
4. Map Your Events Before You Send Them
List the events that matter, usually ViewContent, AddToCart, InitiateCheckout, and Purchase for ecommerce, or Lead and CompleteRegistration for lead generation. For each one, write down which parameters it must carry: value, currency, and content IDs for commerce events. Sending a Purchase with no value makes the event nearly useless for optimization.
5. Send The Matching Parameters
Event quality depends on customer information parameters sent in hashed form: email, phone, and the click and browser identifiers (_fbc and _fbp cookies) where available. More quality parameters means better matching between your server events and real Meta accounts.
6. Set Up Deduplication Properly
Your browser Pixel and your server will both report the same purchase. That is correct, as long as both copies carry the same event name and the same event_id, and arrive within Meta’s deduplication window. Skip this step and Meta counts two purchases for every sale, and your ROAS reports become fiction.
7. Test In Events Manager Before Trusting Anything
Use the Test Events tool and place real test actions on your own site. You should see each event twice, once as Browser and once as Server, marked as deduplicated. If you only see one source, or three copies of anything, stop and fix it here.
8. Check Event Match Quality
In Events Manager, review the Event Match Quality score for your key events. Low scores usually mean missing customer parameters. This score is the closest thing Meta gives you to a grade for your CAPI setup.
9. Watch The First Week Of Data
Compare Meta’s reported conversions with your store or CRM every day for the first week. Small differences are normal. Sudden doubling, or Purchase values that do not match your revenue, mean deduplication or parameters need another look.
10. Document The Setup
Write down what sends events, where the token lives, and how deduplication is handled. The person who fixes this at 2 a.m. six months from now will thank you, and it might be you.
The Mistakes We See Most
Sending events from two server routes at once, so everything arrives twice even with deduplication. Forgetting the value and currency parameters on Purchase. Placing the access token in the browser code where anyone can read it. And never testing, because the events “looked fine” in the dashboard while the match quality sat at the bottom of the scale.
Prefer A Checked Setup Over A Fast One
If you would rather verify what you already have, our free Tracking Health Checklist covers the CAPI checks we run on every account, along with the rest of your tracking: https://growraya.com/resources/
And if you want a specialist to set it up or repair it properly, book a free strategy call. We will review your current setup and give you a clear priority plan: https://growraya.com/free-consultation/