Meta (Facebook/Instagram)
Set up Meta Conversions API (CAPI) to send server-side conversion events from ioZen to Meta Ads.
Send server-side conversion events to Meta for accurate Facebook and Instagram Ads attribution using the Conversions API (CAPI).
Prerequisites
- A Meta Business Manager account
- A Meta Pixel created in Events Manager
- Admin access to the Business Manager or Pixel
Step 1: Get Your Pixel ID
- Go to Meta Events Manager
- Select your Pixel under Data Sources
- Your Pixel ID is the numeric ID shown at the top (e.g.,
1173378694081065) - Copy this value
Step 2: Generate an Access Token
- In Events Manager, click on your Pixel
- Go to Settings
- Scroll down to Conversions API
- Click Generate Access Token
- Copy the generated token
Important: The access token is a long string (150–300 characters) that starts with EAA. It is NOT a URL and NOT your Pixel ID. If your token doesn't start with EAA, you may have copied the wrong value.
| Credential | Format | Example |
|---|---|---|
| Pixel ID | Numeric, ~16 digits | 1173378694081065 |
| Access Token | Starts with EAA, 150–300 chars | EAAMxxxxxxxx... |
Step 3: Configure in ioZen
- Open your Intake Bot in ioZen
- Go to Settings → Marketing & Attribution
- Under Ad Platform Integrations, toggle Meta (Facebook) on
- Paste your Pixel ID and Access Token
- Optionally add a Dataset ID if you use one
- The settings auto-save — wait for the "Saved" indicator
Step 4: Test the Connection
- Click the Test Connection button below the credentials
- A successful test shows a green "Connected" badge
- If the test fails, see the Troubleshooting section below
Conversion Events
On Submission
When On Submission is enabled in the Conversion Events section, ioZen sends a Lead event to Meta every time someone completes your Intake Bot. You can configure a custom event name and dollar value.
Field-Level Conversions
You can configure individual questions to trigger conversion events. In the field settings panel for any question, enable Conversion Tracking and optionally:
- Set a custom Event Name (defaults to
Lead) - Set a Conversion Value
- Restrict to specific answer values (e.g., only trigger when "Yes" is selected)
Field conversions are sent in addition to submission-level conversions if both are enabled.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| Invalid OAuth access token | Token is expired, revoked, or malformed | Generate a new token in Events Manager → Settings → Conversions API. Make sure it starts with EAA. |
| Cannot parse access token | A URL or wrong credential was pasted instead of the token | The access token is not a URL. Go to Events Manager → Settings → Conversions API and click "Generate Access Token". |
| Bad signature | Token was corrupted during copy/paste | Re-copy the token carefully. Avoid trailing spaces or line breaks. |
| Invalid parameter | Event payload has invalid fields | This is usually a temporary issue. If it persists, contact hello@iozen.ai. |
| Invalid Pixel ID | The Pixel ID is wrong | Go to Events Manager → Data Sources and copy the correct numeric Pixel ID. |
| OAuthException | General authentication failure | Ensure the token has ads_management and ads_read permissions. Generate a new token if needed. |
Best Practices
- Use a System User token — System User access tokens don't expire. Personal admin tokens may expire after 60 days.
- Verify in Events Manager — After a successful test, check the Test Events tab in Events Manager to confirm events are arriving.
- Enable both UTM and Click ID capture — This improves Meta's ability to match conversions to ad clicks.