Postback and API Integration for Keitaro, Binom, and Voluum: The iGaming Affiliate Setup

What Is S2S Postback and Why Pixel Tracking Fails for iGaming

A postback is a server-to-server HTTP request that sends conversion data directly between systems without relying on the user's browser. Unlike tracking pixels, postbacks are not affected by ad blockers, cookie deletion, Safari ITP, or iOS privacy restrictions.

Common pixel tracking failure points:

• Ad blockers prevent scripts from firing.
• Browser privacy tools limit cookie storage.
• Failed confirmation-page loads cause lost conversions.
• Backend deposit events cannot reliably trigger browser pixels.

According to attribution research referenced by WeCanTrack, a campaign showing 200 qualifying deposits in a database but only 165 recorded conversions creates a 17.5% attribution gap. Advanced S2S tracking setups also report up to 30% higher measured conversion rates compared with basic pixel-based methods.

The attribution loop is simple: the tracker assigns a unique click ID when a visitor clicks an ad, passes it through the affiliate link, and receives it back from the affiliate platform upon conversion. Token formats vary across systems, including {token}, [token], and %token%, but the principle remains the same.

“Affiliates can lose significant revenue when they spread traffic across multiple affiliate programs and leave a 17% attribution gap unaddressed. Missing conversions compound quickly and make optimization decisions less reliable.”

Sara

Content Strategy Lead iGaming

How Postback Tracking Works: Click ID, Parameters, and the Attribution Loop

The standard attribution process follows these steps:

1. User clicks an ad.
2. Tracker assigns a unique click ID.
3. Click ID passes through the affiliate link.
4. Player registers or deposits.
5. The affiliate platform sends a postback containing conversion data.

The click ID is the critical element because it connects the conversion to the original visit. Most systems reject conversions without a valid click identifier.

Parameter	Purpose
Click ID	Matches conversion to the original click
Payout	Real-time commission value
Conversion Type	Registration, FTD, deposit, NGR
Transaction ID	Separates multiple events from one user
Status	Confirmed, pending, declined

Affilka supports six separate event triggers: registration, FTD, any deposit, prequalification, disqualification, and NGR. GET requests pass data via URL parameters, while POST requests send data in the request body. For security, trackers should use HTTPS, IP allowlisting, and verification tokens.

Keitaro Postback Setup: Templates, Traffic Sources, and Campaign URL

Keitaro is a self-hosted tracker that provides full data ownership and avoids per-click pricing. RichAds documentation highlights its library of more than 500 templates covering many affiliate platforms and traffic sources.

Setup process:

1. Create a Traffic Source and select a template.
2. Create an Affiliate Network entry and copy the generated postback URL.
3. Paste the URL into the affiliate platform and configure click ID passthrough using sub_id.
4. Create an Offer and add the tracking URL.
5. Create a Campaign and use the generated campaign URL as the destination link.

The sub_id parameter carries the click ID through the entire attribution chain. Keitaro also supports API-based conversion tracking for integrations that do not use traditional postbacks. Affilka supports custom parameters such as clickID and webID, which can be mapped to sub_id.

You can manually test postbacks by triggering the postback URL directly with test values before launching traffic.

Binom Postback Setup: Self-Hosted Speed and 100+ Network Templates

Binom focuses on speed and simplicity. RichAds benchmarking lists click processing speeds as low as 7 milliseconds, making it attractive for high-volume PPC campaigns.

Setup process:

1. Add a traffic source template.
2. Create an affiliate network and copy the generated postback URL.
3. Create an offer and enter the tracking link.
4. Build a campaign.
5. Use the generated campaign URL inside the traffic source.

Key Binom parameters include:

• cnv_id — click ID.
• payout — commission value.
• cnv_status — conversion status.
• cnv_currency — payout currency.
• to_offer — offer routing parameter.

Binom starts from €61 per month (approximately equivalent to the published $69 pricing) and includes API-based cost synchronization. Compared with Keitaro, it offers fewer templates but a streamlined setup process.

When does 7ms processing matter?

For affiliates handling large PPC volumes, faster click processing reduces delays and improves attribution consistency during traffic spikes.

Voluum Postback Setup: Cloud Tracker with Native iGaming FTD Tracking

Voluum uses a cloud architecture, eliminating server management. This makes it attractive for affiliates operating multiple affiliate programs simultaneously.

FTD setup process:

1. Add the promoted page as an offer.
2. Configure the traffic source.
3. Create a campaign and copy the campaign URL.
4. Copy the Voluum postback URL and add token substitutions.
5. Map affiliate platform parameters to click ID and payout values.

Example structure:

https://your_voluum_postback_url?cid={clickid}&payout={commission}&conversion_type=FTD

Voluum supports separate conversion tracking for registrations, FTDs, deposits, and custom events. According to the 2025 Affilka-Voluum integration announcement, direct API connectivity can eliminate the need for manual postback configuration.

“Affiliates managing several affiliate programs often benefit from centralized cloud reporting because operational overhead becomes more important than infrastructure ownership.”

Sara

Content Strategy Lead iGaming

Tracker Comparison: Keitaro vs Binom vs Voluum for iGaming Postback Workflows

Feature	Keitaro	Binom	Voluum
Architecture	Self-hosted	Self-hosted	Cloud
Pricing Model	License-based	Monthly	Per-click
Speed	High	7ms benchmark	Cloud-managed
Templates	500+	100+	Extensive
API Coverage	Advanced LP API	Moderate	Extensive
FTD Tracking	Yes	Yes	Yes
Affilka Compatibility	Yes	Yes	Direct API

High-volume PPC campaigns often use Binom for its fast click processing and flat monthly pricing. Affiliates commonly select Keitaro for projects that require extensive template coverage and advanced integration flexibility.

Affiliates managing multiple affiliate programs frequently use Voluum to centralize reporting and performance data within a cloud environment. SEO affiliates can work effectively with any of the three platforms, depending on their integration requirements and reporting preferences.

Big Betty Partners, an affiliate program operating across 20+ regions with a strong presence in Europe and a marketing portfolio of 8 brands, supports Affilka-based tracking compatible with all three platforms.

Research highlighted by WeCanTrack indicates that marketers using multi-touch attribution report approximately 15% higher payout accuracy.

Affilka Postback Integration: Configuring Big Betty Partners Tracking

Affilka supports native S2S tracking and custom parameters directly from the affiliate interface.

Available event types:

• Registration
• FTD
• Any Deposit
• Prequalification
• Disqualification
• NGR

Available parameters include:

• Visit ID
• Deposit Amount
• Wager Amount
• Net Revenue
• Transaction ID
• clickID
• webID

Practical integration workflow:

1. Generate the tracker postback URL.
2. Open Affilka postback settings.
3. Select an event such as FTD.
4. Paste the tracker URL.
5. Map visit_id to the tracker click ID parameter.
6. Add payout values using deposit amount or net revenue variables.
7. Perform a manual test.

Big Betty Partners uses Affilka technology with real-time reporting and postback/API support, allowing affiliates to connect to Keitaro, Binom, or Voluum without complex customization. Affiliates remain responsible for their traffic sources and campaign compliance.