Meta pixel and the Conversions API
One tracking call fans out to the Meta pixel in the browser and the Conversions API on the server. Set both up once and Meta sees your conversions even when browsers block the pixel.
The Meta pixel runs in the visitor's browser, and browsers increasingly get in its way. The Conversions API (CAPI) is Meta's server-side channel: your site reports the same events directly from the server, so ad blockers and tracking prevention cannot erase them. On adlens, one tracking call fans out to both, the pixel and the CAPI, so you set them up once and every event travels both roads.
Setting it up
Open Settings, then Tracking (/app/settings/tracking). Paste your Meta pixel id first. The CAPI token field only appears once a Meta pixel exists, because the token is useless without one.
Then paste the Conversions API access token from Meta Events Manager into that field and save. That is the whole setup: no server work, no code.
How the token is scoped
The CAPI token is deliberately workspace-wide: one token covers every site in the workspace. Pixel ids can vary per site, but the token does not, so you never juggle tokens as you add sites.
The token is also write-only. Once saved, the panel will not show it back to you. That is a security choice, not a bug: a secret you can read out of a settings screen is a secret anyone at your screen can read too.
Why Meta and GA4 disagree
Expect Meta and GA4 to report different conversion counts for the same period. They attribute differently: Meta's pixel and CAPI credit the click on the ad, while GA4 credits the last touch before the conversion. A gap of 10 to 30% between the two is normal. It is not double counting and it is not a bug, it is two honest systems answering two different questions.
When it does not work
No CAPI token field in the panel? Add the Meta pixel id first. The field only renders once a Meta pixel exists.
Cannot see the token you saved? You never will: it is write-only. If you are unsure the right token is in there, or you rotated it in Events Manager, paste the new one and save. The new value replaces the old.
Conversions differ between Meta and GA4? Reread the section above. If the gap sits inside 10 to 30%, everything is working. Chase a real problem only when one side reports nothing at all, and in that case check the pixel id and token in Tracking, then confirm events are arriving in Meta Events Manager.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.