Setting up Facebook CAPI & Pixel
Instructions on how to enable Facebook Conversion API and Facebook Pixel to track your social media ads.
We have a dedicated app in the Subbly App Store for Facebook CAPI and Facebook Pixel. It helps you track the performance of your ads. Follow the steps below to configure it.
Why do I need this app?
Facebook Conversion API, also called CAPI, helps improve measurement and data collection for your Facebook ad campaigns. Facebook Pixel records browser-side events during checkout.
When a Pixel ID is configured in the Facebook Pixel app, browser-side Pixel events continue to be sent. The Send via Pixel and Conversions API setting controls server-side events sent through CAPI. Turning this setting off does not turn off the Pixel.
The checkout events tracked by the app include:
- PageViews, the total number of page views.
- CompleteRegistration, when a customer passes the name and email step and creates an account.
- AddPaymentInfo, when a customer passes the card or PayPal step and provides a payment method.
- CustomizeProduct, when a customer completes the product survey, if applicable.
- Purchase, when a customer completes checkout and reaches the success page.
How Pixel and CAPI work together
For server-side CAPI events to be sent and tracked, you need to configure both sides:
- Enable Send via Pixel and Conversions API in the Subbly app.
- Enable or configure Conversions API as a data source in your Meta account.
Use these combinations to understand what to expect:
Configuration | Result |
Pixel ID configured, setting enabled, and Meta CAPI data source configured | Browser-side Pixel events and server-side CAPI events are sent. Meta automatically deduplicates matching events. |
Pixel ID configured and setting disabled | Browser-side Pixel events continue. Subbly does not send server-side CAPI events. |
Pixel ID configured, setting enabled, but Meta CAPI data source is not configured | Browser-side Pixel events continue, but server-side CAPI events are not sent or properly tracked. |
No Pixel ID configured | Subbly does not send Pixel events. CAPI behavior depends on the app's configuration and validation. |
This setting applies to Subbly's Facebook or Meta app. It does not control separately installed Pixels, custom scripts, Google Tag Manager, or other tracking tools. Meta handles deduplication when matching browser-side and server-side events are both sent. If deduplication is not working as expected, check your Meta configuration and tracking implementation.
How do I set it up?
Head over to the Facebook Pixel app inside the Subbly's App Store. Side drawer will open showing the settings of an app.
Extract the information from your Meta Pixel and paste the values in corresponding fields (Pixel ID and Access Token can be retrieved from the Meta profile, cross-check Meta's help documentation on how to retrieve them).
Explanation on what each toggle does can be found below:
- Send via Pixel and Conversions API - sends both browser and server-side events to connected Meta (CAPI needs to be pre-configured as the data source in your Meta Events Manager in order for server-side events to be sent.
- Track Renewal Event - controls whether Subbly sends the Renewal event to Meta as a Purchase event (if enabled, it basically tracks customer's renewals as purchases as well)
- Enabled - controls whether the app is enabled on your checkouts or not.
How did we do?
How to use other shipping services with Subbly?
Setting up Google Tag Manager
