Before you start#
- A pixel that already receives
PageViewandLead(How to track leads from Facebook ads on your website). - Admin access to the dataset in Events Manager.
1Decide whether you need it#
The browser pixel misses visitors who block scripts or decline tracking, and Apple’s rules limit what iOS browsers report. The Conversions API adds a second path from a server, and Meta deduplicates the two so a lead is counted once.
You set this up yourself, and Madder works with or without it. Skip it for now if any of these hold: your campaign runs on a lead form (no website events involved), you get fewer than a few leads a day, or you have not yet seen Lead in Test events.
2Switch on Meta’s one-click Conversions API#
Meta rolled this out between April and July 2026. Paths as of September 2026:
- Events Manager › your dataset › Overview.
- Click Activate Conversions API (on some accounts it sits under See other ways to set up › Set up with Meta).
- Approve. Meta stands up the server connection itself, mirrors every standard event the pixel already sends, and sets matching event IDs so nothing double-counts. It can be turned off from the same place.
It covers web events only: PageView, Lead and the other standard events. Custom events, offline uploads and app events still need one of the routes below.
3Partner integration (Shopify, Wix, WordPress …)#
If your site runs on a platform with a Meta integration, use that instead, because the platform maintains it:
- Events Manager › dataset › Settings › scroll to Conversions API › Choose a partner.
- Pick your platform and follow its steps; on Shopify the server path is one of the app’s data-sharing levels.
Site guides: Shopify, Wix, WordPress.
4Direct integration (developer)#
Only if you need custom events, CRM-qualified leads or a server you control. Your developer needs the pixel ID and an access token from Settings › Generate access token, then sends events with an event_id that matches the browser’s, following Meta’s developer guide.
5Check deduplication#
After a day, open Overview: each event should show both Browser and Server sources, and Diagnostics should not warn about duplicate events. Madder reads results from Meta, so it picks up the server events with no setup.
If it doesn’t work#
- No Activate Conversions API button
- The rollout reached accounts in waves; use step 3 or wait, and check you are looking at the dataset’s Overview, not the ad account.
- Lead count doubled
- Events arrive without matching IDs; on the one-click route turn it off and on again, on a partner route check the platform’s “deduplication” or “event ID” setting.
- Server events but no browser events
- The pixel code is missing on the page; the server path cannot replace it.
- “Event match quality” is low
- The partner sends few customer details; usually fine for lead campaigns, ignore unless Meta flags it.