Conversions API (server copy)
Ad blockers block the pixel's domain, not yours. Pixelonce can send a server-side copy of every event to Meta's Conversions API, under the same event id, so blocked browser events still count.
How it works
- The browser decides whether an event fires — scopes, consent and all.
- If it fires, the browser sends it to the pixel and posts a copy to your own site (with
sendBeacon, so the visitor never waits). - Your site forwards that copy to the Conversions API with the same event id.
- Meta keeps one of each browser/server pair. If the browser copy was blocked, the server copy counts.
The server only relays; it never decides anything. That is what stops the server copy re-creating the duplicate-event problem the scopes exist to fix.
Setting it up
- In Meta Events Manager, open your dataset and generate a Conversions API access token.
- Paste it in the setup wizard's Server copy step (or later under Settings).
- Optionally add a test event code from Events Manager's Test events tab and watch the server events arrive. Remove it when you are done. The
STEPCOUNT_CAPI_TEST_CODEconstant inwp-config.phpoverrides the setting.
Things to know
- The server copy obeys consent exactly like the browser event.
- Dry-run hosts never send a server copy.
- Events listed under Events sent elsewhere are never mirrored — if your payment system already sends a server-side Purchase, Pixelonce leaves it alone.
- Malformed click-id cookies (
_fbc) are cleaned before sending; malformed ids silently break attribution.