Why Facebook Pixel is No Longer Enough
If you are running Facebook Ads to promote affiliate offers, you have probably noticed a growing discrepancy between the sales recorded in your affiliate dashboard and the conversions reported in Facebook Ads Manager.
This is because traditional browser-based tracking (the standard Facebook Pixel) is being blocked by:
- iOS 14+ App Tracking Transparency: Over 80% of iPhone users opt out of tracking.
- Ad Blockers: Up to 40% of desktop users run extension blockers.
- Safari & Chrome Cookie Restrictions: Third-party cookies are blocked or deleted within 24 hours.
To solve this, Meta introduced Conversions API (CAPI). Instead of tracking events in the visitor's browser, CAPI lets your tracking server send conversion data directly to Meta's servers.
Here is the step-by-step guide to configure Meta CAPI for your affiliate campaigns using PostbackFlow.
---
Step 1: Generate your Meta Access Token
To send conversion events to Meta, you need a System User Access Token.
1. Go to your Meta Business Suite and open Events Manager.
2. Select the Data Source (your Pixel) you want to use.
3. Go to the Settings tab.
4. Scroll down to the Conversions API section and click Generate access token under "Set up manually".
5. Copy the generated token string (starts with EA...) and save it. You also need your Pixel ID (found at the top of the Settings tab).
---
Step 2: Configure Meta CAPI in PostbackFlow
Now, connect your Meta Pixel to PostbackFlow so the system knows where to route conversions.
1. Log in to your PostbackFlow console and go to the Ad Platforms page.
2. Find the Meta Conversions API card and click + Configure.
3. Fill in the required credentials:
* Pixel ID: The ID of the Pixel you got in Step 1.
* Access Token: The EA... token you generated.
4. Click Save and toggle the platform switch to Active.
---
Step 3: Link your Campaign and Network Postback
Next, configure your affiliate network to send conversion data to your unique PostbackFlow URL.
1. Go to the Tracking Links page and click + New Campaign.
2. Enter your offer URL and select your Affiliate Network Template (e.g., ClickBank, MaxBounty, ShareASale).
3. Copy your Campaign Postback URL generated by PostbackFlow.
4. Paste this URL into your affiliate network's postback settings.
For example, on MaxBounty, you would configure your postback URL as follows:
https://postbackflow.com/postback/YOUR_TOKEN?click_id={s1}&payout={payout}&event_type=purchase
---
How Event Deduplication Works
To ensure your ad reports are accurate, Meta recommends using both browser Pixel and server CAPI. However, this raises the risk of double-counting.
PostbackFlow solves this using automatic Event Deduplication:
1. When a visitor clicks your ad, PostbackFlow captures the unique Facebook Click ID (fbclid) and creates a unique click_id.
2. If the visitor converts, PostbackFlow forwards the event to Meta CAPI alongside the unique click_id mapped as the event_id.
3. If the browser Pixel also fires a browser event with the same event_id, Meta automatically merges the two events and records only one conversion.
By combining browser Pixel and PostbackFlow CAPI, you achieve 100% conversion accuracy while protecting your advertising budget.