The Facebook Conversions API (CAPI) lets Fourthwall send purchase-journey events to Meta server-to-server, so your ads keep learning even when cookies, ad-blockers, or iOS privacy prompts hide the browser Pixel. Running CAPI alongside the Meta Pixel gives Meta two chances to see every sale while automatically deduplicating overlaps.
How does it work?
Once connected, Fourthwall will send these standard events, with all relevant metadata, directly from our servers:
- PageView
- View Content
- Add To Cart
- Initiate Checkout
- Add Payment Info
- Purchase
Meta merges each server event with the matching browser Pixel event (using the shared event_id) so you never double-count.
When should I use the Facebook Conversions API?
Use this if you want more accurate and robust purchase tracking for your ad campaigns while avoiding the impact of ad blockers.
We recommend using the Facebook Conversions API and the Meta Pixel for the most complete data. You can read more on how to set up Meta Pixel here: Setting Up Meta Pixel for Retargeting Ads on Fourthwall.
How to set it up
Prerequisites
A Meta Business account with at least Apps and integrations access for the brand you advertise.
Your user should have at least this access
Step 1 – Create a new dataset
- Log in to Meta Business settings: https://business.facebook.com/latest/settings
- Open Data Sources → Datasets and Pixels
- Click Add and create a new DataSet
Step 2 - Generate access token
From Events Manager, select Data Sources
- Log into Meta Events Manager: https://business.facebook.com/events_manager2
- Open your Dataset
- Select settings
- Scroll down to “Set up direct integration” and generate an access token
Step 3 - Add the Pixel Id and Access Token to Fourthwall
- Go to the Meta Conversions App in Fourthwall
- Set your Pixel Id and Access Token. The Pixel Id will be your Dataset Id in the settings above.
- Within 2 hours, you should see events in your Events Manager