Create a dataset and a Conversions API setup on Meta
Published on by the Oriva team.
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. Meta asks you to review a new custom event there once, to check it comes from your business; after that you can optimize a campaign on it. A rule-based “custom conversion” is optional, only if you want extra rules on top.
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 trial