Start a project
Work eventabee Guides Connect Meta (Conversions API)

Connect Meta (Conversions API)

Set up Meta CAPI with access token, dataset ID, and test events.

Updated

Operational

Meta’s Conversions API (CAPI) receives events server-side, which is the whole point of eventabee. Setup is three fields and a test event.

1. Create a system user in Meta Business Manager

In Business Settings → Users → System Users, create a new system user. Assign it to the ad account and Dataset (Pixel) you’ll be sending events to. Generate a token with the ads_management permission.

System user tokens don’t expire. Regular user tokens do — don’t use a regular user token in production.

2. Find your Dataset ID

In Events Manager → your dataset → Settings, you’ll see the dataset ID (a ~15-digit number). This is what Meta sometimes still calls the “Pixel ID.”

3. Paste into eventabee

In the eventabee dashboard, go to Destinations → Meta → Connect. Paste the access token and dataset ID. Save.

4. Enable test events

Meta lets you tag server events as test events so you can verify the pipeline without polluting real data. In the eventabee destination config, toggle Test mode and paste the test_event_code from Meta’s Events Manager → Test Events tab.

Now trigger a page view or purchase from your storefront. Within ~30 seconds Meta’s Test Events view should show the event arriving with its full payload. When it does, toggle Test mode off.

Meta is mapped to the Marketing consent category by default. EU / UK visitors who decline will not have events forwarded. If they later accept, eventabee replays up to 30 days of their stored events (tagged as backfill).

Troubleshooting

  • Events arrive but no match quality. Confirm you’re sending hashed customer data (email, phone) where available. eventabee hashes automatically when the fields are present in the event.
  • Invalid OAuth access token errors. Token was rotated or revoked. Generate a new one and paste it back in.
  • Duplicate events in Meta. Confirm the Meta browser pixel is also set up (by your theme or another app) with the same event ID — Meta dedupes on event_id across browser + server. eventabee stamps every event with an ID.