How to Set Up the Meta Conversions API, Step by Step

Setting up the Conversions API means getting your server, rather than the visitor’s browser, to send events to Meta. Meta gives you a guided flow in Events Manager that splits the work in two: you pick which events and details to send, and a developer writes the code that sends them. If you have no developer, the Gateway option does the connection for you on a cloud account.

What do you need first?

1. Check that you hold full control of the business portfolio containing your Meta Pixel or dataset.
2. Make sure you, or your developer, have access to your business’s server.
3. Create a Meta Pixel or a dataset, depending on which types of events you’ll send.

How do you create the setup instructions?

This half is usually done by the advertiser.

1. Go to Meta Events Manager and click Datasets in the left menu.
2. Select the pixel or dataset you want to link to the Conversions API.
3. Click Add events, select Add new integration, choose Conversions API and click Set up.
4. Click Set up manually, then Next, read the overview and click Continue.
5. Select the events to send, using the dropdown for recommendations based on your business type.
6. Select the parameters for each event; Meta requires at least one customer information parameter.
7. Review your choices and click Confirm setup.
8. Click Send instructions to email your developer, or Open implementation guide to do it yourself.

If the person you email has no role in your business, Meta also asks them to accept developer access.

How does the developer finish it?

1. In Events Manager, open the same pixel or dataset and click Manage integrations.
2. Find the Conversions API integration and click Complete setup.
3. Click Generate access token, copy it and store it somewhere safe.
4. Use the listed resources to build and send events, including the payload helper and batching guidance.
5. Click Finish once you’ve confirmed events are arriving correctly.

Meta notes the completion bar won’t reach 100% until the developer sends the POST request.

When does the Gateway make more sense?

Gateway feature	Detail from Meta
Setup	Codeless and self-serve, chosen under Data connection platforms in Events Manager
Time	Installation cut from weeks to under 30 minutes
Cost	Cloud storage fees only, starting at $30 a month and varying by region and traffic
Hosting	Amazon Web Services or Google Cloud Platform; a new account takes a few minutes
Deduplication	Automatic between browser and server events

Meta suggests the Gateway if you already use the Meta Pixel, don’t send web events through the Conversions API yet, spend more than $300 a month on campaigns optimizing for web events, and don’t use an ecommerce partner. If a partner such as Shopify or WooCommerce manages your pixel, Meta recommends using that partner’s integration if it supports the Conversions API.

What should you check after launch?

Meta recommends sending the same events through both the pixel and the Conversions API. In your server event details, check these tabs regularly: Event coverage, where Meta suggests aiming for a 75% ratio against unique pixel events; Event deduplication; Event matching; Data freshness; and the Diagnostics tab.

FAQ

How do I test that server events work?

Use the Test events tool in Events Manager. Meta says it checks whether your server event payload is correctly formed and helps debug unusual activity. Test events should appear shortly; if they don’t, use the payload helper to check the structure.

Can I send events in real time?

Meta asks you to. The Data freshness tab shows the delay between when an event happens and when Meta receives it, and Meta recommends sending events in real time or as close to it as possible.

Can I change which events I send later?

Yes. In Events Manager, click Manage integrations on the right of the activity chart, open the dropdown next to Conversions API and select Configure events. This takes you back through the event and parameter choices.