Use this setup when you want a Quiz or Paywall to send Meta events to a Pixel different from the project-wide Pixel. This is useful for testing, for separating tracking between funnels, or for running a different Pixel on another domain.
There are two different ways to do this:
- Add a custom Pixel ID and Access token in Quiz/Paywall/After Pay settings - use this when you need CAPI.
- Add an additional Pixel with custom code in HTML to HEAD - browser events only.
| Setup | Browser events | CAPI events |
|---|---|---|
| fbq('init', 'PIXEL_ID') in HTML to HEAD | Yes | No |
| Custom Pixel ID in Quiz/Paywall/After Pay settings | Yes | Not by itself |
| Custom Pixel ID + Access token in Quiz/Paywall/After Pay settings | Yes | Yes |
Custom Pixel for a Quiz/Paywall/After Pay + CAPI
This lets you keep tracking separate from the project-wide Pixel without changing the main project settings. Use this option when the custom Pixel should receive server-side Conversions API events in addition to browser events.
Use this when:
- You want the custom Pixel to work with CAPI.
- You want to separate tracking between domains or funnels.
- You want browser and server events to go to the same Pixel.
Important: fbq('init') alone is not enough for CAPI. If you need CAPI for the custom Pixel, add the Access token in settings for that Pixel.
- Open the Quiz -> Go to the settings tab.
- Add the custom Pixel ID and Facebook Access Token.
- If the flow includes a Paywall and After Pay page, add the same custom Pixel there too.
Important: if the Quiz uses a Paywall and After Pay page, configure the Pixel there too. Otherwise, different parts of the funnel may send events to different Pixels
Add a second Pixel with custom code
Use this option when you want to add one more Meta Pixel in parallel without changing the main Pixel setup. Add the code in the Quiz, Paywall, After Pay, or project HTML to HEAD field
Code for Quiz/Paywall settings, section "HTML to HEAD"
<script>
fbq('init', 'XXXXXXXXXXXXXX'); // the second pixel
</script>Use this when:
- You want to test a second Pixel.
- You want browser tracking for another domain.
- You do not want to change the project-wide Pixel settings.
In the Quiz, Paywall or After Pay "Settings" tab, add additional browser pixel code. This way you will collect only browser events, not CAPI.
<script>
const hostname = window.location.hostname;
if (hostname.includes(’[newdomain.com](http://newdomain.com/)')) {
fbq(‘init’, NEW_PIXEL_ID);
}
</script>
Adding script for domain in the HTML to HEAD in the Project settings
Important: this method adds an additional browser Pixel only. It does not enable Conversions API for that Pixel. Meta’s browser Pixel code uses fbq, while Conversions API is a separate server-side integration which requires input of the Facebook Access token.
Q: How can you configure events for custom Pixel CAPI?
A: A custom Pixel CAPI uses the same event configuration as the main Pixel. Configure the events in Project Settings → Analytics → Conversion Events settings.