You set up the Conversions API by choosing a method, connecting it to the same pixel you already use, sending your events with customer details, giving each event an ID that matches the pixel's, and testing in Events Manager. The method you choose decides how much work it is.
TL;DR
- Pick a method first: a platform integration, a gateway, or a direct build.
- Use the same pixel ID for server events as for browser events.
- Send the same events as the pixel, plus customer details for matching.
- Give each event the same name and event ID from both sources.
- Test with a real order and confirm Meta shows one purchase.
- Recheck after site changes.
What you need
- Access to your Meta pixel in Events Manager.
- Admin access to your store or site platform.
- A developer, only if you choose a direct build.
- A test order you can place.
Setup methods compared
| Method | Work needed | Suits |
|---|---|---|
| Platform integration | Low, mostly settings | Stores on a platform with a built-in connection |
| Gateway | Medium, a hosted service | Teams without developers who want more control |
| Direct build | High, code on your server | Custom stores and offline or CRM events |
Meta compares the Conversions API setup options and your platform's own documentation lists the choices it supports.
Step 1: Pick your method
Choose the lowest-effort option that sends the events you need. If your platform has a built-in Meta connection with a higher data sharing level, start there. Choose a gateway if you want a hosted setup, and a direct build only if you need custom events.
How to check: you can name the method and who owns it.
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)Step 2: Connect it to your existing pixel
Meta says to use the same Pixel ID for server events as for browser events. A new pixel would split your data. Our answer on finding your pixel ID shows where to look.
How to check: in Events Manager, the server events appear under the same pixel.
Step 3: Send the right events
Mirror the pixel events you use: PageView, ViewContent, AddToCart, InitiateCheckout and Purchase. Each Purchase should carry value and currency.
How to check: Test events shows each event with its parameters.
Step 4: Add customer details
Meta matches events to people using details such as email, phone, the browser ID and the click ID from the ad link. Hash personal details as Meta requires, and send only what you have permission to use. More matching details raise Event Match Quality.
How to check: the Event Match Quality score for your purchase event rises after the change.
Step 5: Match event IDs to remove duplicates
Meta deduplicates events only when the event name and event ID match between the pixel and the server. Use the order number or another stable value for the ID, and send it from both.
How to check: place a test order and confirm one Purchase, not two.
Step 6: Test, then watch for a week
Use Test events with the test code from Events Manager, place a real or test order and check each field. After a week, compare Meta's purchases with your store's orders.
How to check: the two counts are close, and the source column lists both Browser and Server.
What is the most common mistake?
Sending purchases from both sources with different event IDs. The result is double-counted sales, which makes ads look better than they are and sends automation after the wrong signals. Always test with one order.
What should I do next?
Keep an eye on Event Match Quality monthly, and recheck after theme, checkout or platform updates. Then use the cleaner data: set your attribution setting and read results against revenue. See what the Conversions API is for the background.
Where Madgicx fits
Madgicx can do the server side for you. Madgicx Cloud Tracking hosts Meta's Conversions API Gateway and Signals Gateway and sends conversions to Meta from your server. That means Meta sees and attributes more of your conversions, without code on your side. You stay in control of setup.
FAQ
How long does Conversions API setup take?
A platform integration can take minutes, and a direct build can take days. The testing week adds time either way.
Do I need to remove my pixel when I add the Conversions API?
No, keep the pixel. Meta recommends running both and matching event IDs.
What is a Conversions API access token?
It is a key that lets your server send events to your pixel. Keep it private, like a password.
How do I know if my Conversions API is working?
Open Events Manager and check that events show Server as a source. A test order should appear once.
Can I set it up on Shopify?
Yes, through Shopify's Meta data sharing settings. Pick the level that includes the Conversions API.
Related
- Answers: What is the Conversions API?
- Answers: Conversions API vs Meta pixel
- Glossary: Conversions API
Go deeper
For a longer walkthrough with screenshots of each option, read the Facebook Conversions API guide.
Sources
- Compare Conversions API setup options, Meta Business Help Center
- Get started with the Conversions API, Meta for Developers
- Handling duplicate Pixel and Conversions API events, Meta for Developers
