ioZen injects the Meta Pixel on published Intake Bot pages and fires a browser-side Lead event alongside the server-side CAPI event. Both share the same event ID so Meta deduplicates them correctly.
Meta’s Conversions API has been part of ioZen for a while. The problem with server-side-only attribution is that Meta needs both a browser signal and a server signal to deduplicate correctly. Without the Pixel, CAPI events can end up competing with browser events fired by other tools on the same page, or just missing the browser signal entirely.
Starting today, ioZen injects the Meta Pixel automatically on every published Intake Bot page. When a submission comes in, a browser-side Lead event fires alongside the CAPI event. Both carry the same event_id, so Meta knows they’re the same conversion and counts it once.
Match quality also improves. The _fbp and _fbc cookies are now passed through alongside the raw IP via CAPI, which means Meta has more signals to match the conversion to an ad click. In practice this shows up as better attribution in Events Manager, not higher conversion counts.
The Test Connection button opens the bot in a new tab to fire a real Pixel event, then links you to the Events Manager Test Events tab so you can confirm the deduplicated pair arrived. A Test Event Code field lets you use Meta’s official sandbox without touching live data.
Available on all plans.
ioZen now injects the Meta Pixel automatically on published Intake Bot pages and fires a browser-side Lead event alongside the server-side CAPI event. Both events share the same event_id so Meta deduplicates them correctly. The Test Connection button opens the bot in a new tab to fire a real Pixel event, then links you directly to the Events Manager Test Events tab to verify the deduplicated pair. A Test Event Code field lets you use Meta's official sandbox. Match quality improves with _fbp/_fbc cookies, shared event IDs, and raw IP forwarded via CAPI.
