Meta (Facebook/Instagram)
Connect ioZen to Meta Ads using dual-channel Pixel + CAPI. ioZen injects the Pixel automatically — no code to paste.
Send conversion events to Meta for accurate Facebook and Instagram Ads attribution. ioZen uses a dual-channel approach: a browser-side Meta Pixel (for Match Quality and Test Events visibility) plus a server-side Conversions API (CAPI) call. Both events share the same event_id so Meta deduplicates them automatically.
You never paste any Pixel code. ioZen handles injection on all published Intake Bot pages.
Prerequisites
- A Meta Business Manager account
- A Pixel (Dataset) created in Events Manager
- Admin access to the Business Manager
Step 1: Find your Pixel / Dataset ID
- Go to Meta Events Manager
- Select your Pixel under Data Sources
- Copy the numeric Pixel ID shown at the top (e.g.
1173378694081065)
Meta is migrating the "Pixel ID" label to "Dataset ID" — they refer to the same numeric ID.
Step 2: Generate an Access Token
- In Events Manager, select your Pixel
- Go to Settings → Conversions API
- Click Generate Access Token (or use an existing System User token)
- Copy the token — it starts with
EAAand is 150–300 characters long
The access token is NOT your Pixel ID and NOT a URL. If it doesn't start with EAA, you copied the wrong value.
Step 3: Configure in ioZen
- Open your Intake Bot → Settings → Attribution → Ad Platform Integrations
- Enable Meta (Facebook) and expand the section
- Paste your Pixel / Dataset ID
- Paste your Access Token
- Save
ioZen will automatically inject fbevents.js on your bot's published page and fire a Lead event on submission. The CAPI call fires server-side in parallel using the same event_id.
Step 4: Verify with Test Events (recommended)
The Test Events tab in Events Manager lets you see both the browser Pixel event and the CAPI event in real time, with a "Deduplicated" badge when the event_id matches.
To use Test Events:
- In Events Manager, go to your Pixel → Test Events
- Copy the Test Code (format:
TEST12345) - In ioZen, paste it into the Test Event Code field
- Click Test Connection — ioZen fires the CAPI call and opens your bot in a new tab to fire the Pixel event
- Click View in Events Manager to see the deduplicated pair in the Test Events tab
With a Test Event Code set, any test submission you run inside ioZen (the bot preview and single-field test view) also routes to the Test Events tab. This lets you verify your real submission and field-level conversion triggers end to end without touching live data.
The Test Event Code only affects test events — the Test Connection button and in-app test submissions. Real submissions from your published bot always go to your live dataset and ignore the code, so it's safe to leave it set. Test events never affect ad optimization or reporting.
How ioZen injects the Pixel
- Hosted bot (
yourdomain.com/i/slug): Pixel always injected when the integration is enabled - Embedded widget / popup / inline: Pixel injected by default; use the Track inside embed toggle to turn it off if your host page already has the same Pixel loaded
ioZen's own marketing Pixel (if present on your site) is separate and unaffected.
Match Quality
ioZen sends the following signals to improve Event Match Quality:
| Signal | Source |
|---|---|
em (email) | Hashed from submission data |
ph (phone) | Hashed from submission data |
fn / ln | Hashed from submission data |
fbp | _fbp cookie set by the injected Pixel |
fbc | _fbc cookie derived from fbclid at click time |
client_ip_address | Raw IP forwarded to CAPI (not stored by ioZen) |
client_user_agent | Browser UA from the submission request |
event_id | Browser-generated UUID — shared by Pixel and CAPI for deduplication |
Troubleshooting
| Symptom | Fix |
|---|---|
| "Invalid OAuth" error | Regenerate the access token in Events Manager → Settings |
| "Invalid pixel ID" error | Check that the Pixel ID is numeric (not the pixel name) |
| Real submissions not appearing in production | Confirm the submission was not a test run — test submissions route to the Test Events tab by design when a Test Event Code is set |
| Test submission not appearing in Test Events | Ensure a Test Event Code is set and the relevant event is enabled (On Submission / Field-Level Conversions) |
| Two events appear in Test Events without "Deduplicated" badge | The event_id may not be matching; re-test with the Test Connection button |
| Pixel Helper shows wrong dataset ID | Check that the Pixel / Dataset ID field matches the Pixel shown in Events Manager |
| Events not appearing in Test Events tab | Ensure the Test Event Code is pasted correctly; codes expire after 15 minutes of inactivity |