Table Of Contents

• How to Set Up Postback and Conversion Tracking in 2026: S2S Integration Guide
  • How to Set Up S2S Postback: Step-by-Step
  • What Changed in Conversion Tracking in 2026
  • Why Browser Pixels Alone No Longer Work
  • Pixel vs CAPI vs S2S Postback: Which Tracking Method to Use
  • Setting Up S2S Postback: The Full Technical Flow
    • Step 1: Choose and Configure Your Tracker
    • Step 2: Configure the Affiliate Network Side
    • Step 3: Connect the Ad Platform
      • Facebook (Meta) — CAPI Setup
      • Google Ads — Enhanced Conversions
      • TikTok — Events API
  • Click ID Mapping: The Core of Attribution
  • Deduplication: Avoiding Double-Counted Conversions
  • Verifying Your Setup: Postback Testing Checklist
  • Postback Parameters Reference
  • Quick Start Checklist
  • What to Read Next

Updated: April 2026

How to Set Up Postback and Conversion Tracking in 2026: S2S Integration Guide

TL;DR: S2S postback tracking is the only reliable method for measuring conversions in 2026 — browser-based pixels lose 30-40% of data due to iOS restrictions and ad blockers. This guide walks you through the full setup: tracker → affiliate network → ad platform. If you need verified ad accounts with Pixel and CAPI already configured — browse Facebook accounts for advertising — ready to run from day one.

How to Set Up S2S Postback: Step-by-Step

1. Choose a tracker (Keitaro, BeMob, Voluum, RedTrack) and create a campaign
2. Generate your campaign tracking URL with click ID macro (e.g., {clickid})
3. In your affiliate network, paste the postback URL: https://tracker.domain/postback?clickid={AFCLICK}&payout={PAYOUT}&status={STATUS}
4. In your ad platform (Facebook/Google/TikTok), set up the conversion event to fire on the landing page
5. Connect CAPI or S2S at the platform level to pass conversion signals server-to-server
6. Test the full chain with a real conversion — verify click ID matches in tracker and affiliate dashboard
7. Enable auto-optimization rules: pause underperforming placements when CPA exceeds target by 20%
8. Verify data parity: tracker conversions ± 5% vs affiliate network stats is acceptable

What Changed in Conversion Tracking in 2026

• Apple's ATT framework now affects 68% of iOS users globally — browser pixels miss most in-app conversions (Apple, 2025)
• Meta requires CAPI v2 for all conversion optimization — legacy pixel-only setups are deprioritized in delivery
• Google's Privacy Sandbox eliminated third-party cookies in Chrome stable — Enhanced Conversions are now the baseline
• TikTok Events API v1.3 added deduplication by event_id — essential to avoid double-counting conversions
• Voluum, Keitaro, and BeMob all released native CAPI bridge integrations in Q1 2026

Why Browser Pixels Alone No Longer Work

Every media buyer still running conversion tracking exclusively through browser-based pixels is losing data. According to Voluum's 2025 industry report, cookieless attribution gaps leave 30-40% of conversions unmeasured on average, with iOS traffic showing losses as high as 60%.

The root causes are structural: iOS ATT opt-out rates hover around 75-80% in Tier-1 markets, ad blockers strip tracking pixels on roughly 25% of desktop sessions, and Meta's own attribution window changes have made click-attribution increasingly unreliable for campaigns longer than 24 hours.

S2S postback solves this by moving the conversion signal from the browser to the server. When a user converts, the affiliate network sends a server request directly to your tracker — no cookies, no browser permissions required.

Need accounts that work with CAPI right out of the box? Check verified Facebook ad accounts — these come with Business Manager access ready for CAPI integration.

Pixel vs CAPI vs S2S Postback: Which Tracking Method to Use

The right answer for most media buyers in 2026: hybrid tracking — browser pixel for retargeting audiences, CAPI or S2S postback for conversion optimization signals. Using them together with deduplication by event_id captures the best of both.

⚠️ Important: Running CAPI alongside your pixel without deduplication will inflate reported conversions by 40-80%. Always pass an identical event_id from both pixel and CAPI for the same event. Meta uses this to deduplicate — if event_id values don't match, both events get counted.

Setting Up S2S Postback: The Full Technical Flow

Step 1: Choose and Configure Your Tracker

The four trackers dominating the space in 2026 — Keitaro, BeMob, Voluum, and RedTrack — all support S2S postback natively. Here's how they compare for solo buyers vs teams:

In Keitaro (the most common choice for CPA arbitrage), create a new campaign and note your campaign URL. It will contain a {clickid} macro that captures the unique click identifier — this is the backbone of the entire attribution chain.

Step 2: Configure the Affiliate Network Side

Log in to your affiliate network's dashboard. Find the postback URL field — it's usually under "Profile" → "Postback" or inside each individual offer settings.

Your postback URL format will look like:

https://yourdomain.keitaro.io/postback?token=YOUR_TOKEN&status=2&payment={payout}

Replace {payout} with the dynamic payout macro your network uses. Common ones: - Alfaleads: {payout}, status confirmed = 2 - Leadbit: {income}, approved postback - Dr.Cash: {payout}, global postback in profile settings

Test by triggering a test conversion — your tracker should log it within seconds.

Step 3: Connect the Ad Platform

Facebook (Meta) — CAPI Setup

CAPI passes conversion events from your server to Meta's servers, bypassing browser restrictions entirely. According to Meta Business Help, advertisers using CAPI alongside pixel see 7-10% more attributed conversions on average, with significantly better delivery to high-intent audiences.

In Business Manager: 1. Go to Events Manager → Data Sources → your Pixel 2. Select "Set Up" → "Conversions API" 3. Choose "Partner Integration" if your tracker has a native bridge (Keitaro, Voluum, RedTrack all do) 4. Generate your access token and paste it into your tracker's CAPI settings 5. Map your conversion event (Lead, Purchase, Complete Registration) to the correct postback status

⚠️ Important: CAPI requires a verified Business Manager to function properly. If your BM is unverified, Meta will accept the events but discount their weight in optimization. Use a verified Business Manager to ensure full signal credit.

Google Ads — Enhanced Conversions

Google's Enhanced Conversions work similarly to CAPI — they hash user data (email, phone) and send it server-side to match against Google's signed-in user graph. This recovers conversions lost to cookie blocking.

Setup flow: 1. Google Ads → Tools → Conversions → Settings → Enhanced Conversions 2. Enable "Enhanced conversions for web" 3. In your landing page, fire the gtag conversion event with user_data object containing hashed email 4. Alternatively, use Google Tag Manager's Enhanced Conversions variable

TikTok — Events API

TikTok's Events API v1.3 (2026) requires deduplication by event_id. In TikTok Ads Manager: 1. Assets → Events → Web Events → Create Pixel 2. Select "Events API" integration mode 3. Connect via your tracker's TikTok Events API integration 4. Set event_id = same value you pass in the pixel's ttclid parameter

Running TikTok campaigns? Browse TikTok Ads accounts — verified accounts with Business Center access for multi-campaign setup.

Click ID Mapping: The Core of Attribution

The entire S2S system depends on passing and preserving the click ID through the conversion funnel. Here is where most setups break:

Common failure points: - The landing page doesn't pass {clickid} to the pre-lander URL - The offer page URL drops the click ID parameter on redirect - The affiliate network's postback fires with an empty {clickid} value - URL parameters are stripped by the server on the offer landing page

Fix: Use sub-ID parameter chaining. Pass your tracker's click ID as sub1 or aff_sub (check your network's parameter name). Test the full chain before scaling by checking your tracker logs for received postbacks.

Case: Media buyer running nutra offers on Facebook, $150/day budget. Problem: Affiliate network showed 47 conversions in 7 days. Facebook attributed only 12. ROAS looked negative at 0.6x — campaign was paused. Action: Investigated click ID chain — pre-lander was dropping the sub1 parameter on redirect. Fixed with a server-side redirect preserving all URL params. Enabled CAPI through Keitaro's native bridge. Result: Facebook's attribution recovered to 38 conversions in the next 7 days. ROAS jumped to 2.1x. Campaign resumed profitably.

Deduplication: Avoiding Double-Counted Conversions

Running both pixel and CAPI (or pixel + S2S) without deduplication is one of the most expensive mistakes in tracking setup. Inflated conversion counts cause the algorithm to over-optimize toward false signals, driving up CPMs while real ROAS stays flat.

Deduplication rules by platform:

• Meta: Pass identical event_id from both pixel and CAPI for the same conversion event. Meta docs specify this should be a unique string per event instance.
• TikTok: Pass event_id in both pixel and Events API calls. TikTok deduplicates within a 48-hour window.
• Google: Enhanced Conversions uses order ID / transaction ID for deduplication — always pass a unique transaction_id.

Your tracker should generate the event_id automatically and pass it to both channels. In Keitaro, this is handled via the "Meta CAPI" integration module. In Voluum, it's the "S2S Connection" with deduplication toggle.

Verifying Your Setup: Postback Testing Checklist

Before scaling spend, verify every link in the attribution chain:

• [ ] Send a test click through your tracker URL — confirm click is logged
• [ ] Trigger a test conversion — confirm postback fires in tracker logs
• [ ] Check affiliate network's postback log — confirm click ID received matches tracker
• [ ] Check ad platform's events manager — confirm conversion event registered
• [ ] Compare tracker conversions vs affiliate stats — acceptable variance is ±5%
• [ ] Confirm deduplication is active if running pixel + CAPI simultaneously
• [ ] Set up auto-pause rules: if daily spend > 3× target CPA with 0 conversions, pause

⚠️ Important: Never scale budget before verifying postback fires correctly. Scaling a campaign with broken tracking means optimizing on zero signal — Meta/Google will spend your budget on the wrong audience. Check tracker logs after your first 10-20 conversions, not after 100.

Postback Parameters Reference

Quick Start Checklist

• [ ] Sign up for a tracker: Keitaro ($49/mo) or BeMob (free tier for testing)
• [ ] Create a campaign and grab your tracking URL with {clickid} macro
• [ ] Paste tracker's postback URL into your affiliate network's postback settings
• [ ] Create an ad platform pixel/event and link to your tracker via CAPI bridge or S2S
• [ ] Configure deduplication: pass matching event_id in pixel + CAPI
• [ ] Run a test conversion and verify end-to-end in tracker logs
• [ ] Set auto-optimization rules in your tracker before launching spend

Ready to scale with clean tracking data? Get Facebook accounts for advertising with unlimited BM access — structured for multi-campaign CAPI setups.

What to Read Next

• Tracking on Facebook: Setting Up Tracking on Facebook: Postback, S2S Conversions and Goals
• Choosing a Tracker: How to Choose a Tracker for Facebook Media Buying: The Best Options
• Beginners: What Is Traffic Arbitrage and How Does It Work in 2025

• Best Tracker for Media Buying 2026: Keitaro vs Binom vs BeMob vs RedTrack
• Media Buying Workflow: Daily Routines, SOPs, and Team Structure