Create a dataset and a Conversions API setup on Meta
Published on by the Oriva team. Updated on .
For a Conversions API send from Oriva to show up in Meta Ads Manager, you need a dataset (Events Manager also calls it a “pixel”, same identifier) and a Conversions API access token. Both are created in the same place, without writing a line of code. Unlike ChatGPT Ads, no extra object is needed for Meta to count a standard event (purchase, lead…).
Create the dataset (pixel)
In Events Manager (facebook.com/events_manager2), click Connect data, choose Web and click Connect, give the pixel a name (your site's name is enough), then Create pixel. The identifier appears right away.
Generate the Conversions API token
On that dataset, open the Settings tab, Conversions API section: click “Generate access token” under “Set up manually”, then copy it right away. Like an Oriva sk_ key, it does not show up again afterwards.
That link only appears if your account has developer privileges for the business (your business portfolio in Meta Business Suite); without them, ask whoever has them to generate it or pass it on to you.
Paste into Oriva
The Pixel ID and Access token go in the Meta Conversions API destination form (Destinations → Meta Conversions API).
Do you need to create anything else for it to count?
- A standard event (
purchase,lead,complete_registration,subscribe,start_trial) is recognized directly by Meta, with nothing more to create. - A custom event (
custom:*) shows up in Events Manager from the first send. To make it a campaign goal, Meta documents the custom conversion: you create it in Events Manager from that event, pick the closest standard event for optimization, then select it as the performance goal.
Who doesn't need this guide?
You already have a dataset and a Conversions API token: paste them straight into the Oriva destination form.
To understand the limits of the one-click Conversions API that Meta turns on by default, see Meta's one-click Conversions API: is it really enough?.
Start free trialKeep reading
- Meta Conversions API without Google Tag Manager: Send your purchases and leads to Meta from the server, with no GTM container: one line of code, one DNS setting, and a log that proves every delivery.
- Meta-enabled Conversions API: is it enough?: Meta turns on its one-click Conversions API by default. What it sends, what it cannot see, and when a server-side send changes things.
- Double counting pixel + server API: how to deduplicate: Meta, TikTok, Google Ads and ChatGPT Ads only deduplicate if the pixel and the server carry the same identifier. Each one's field, and the traps.