Topic
Guides on: Trackers & TDS
Настройка Keitaro, Binom, постбэков, кликовых ID и сравнение с MMP
Implement first-party data consent in server-side delivery
A server queue does not automatically know a visitor's current choices. Keep the decision record, event and destination policy connected so each send can be explained.
Preserve event time through queues and time zones
A timestamp can be validly formatted and still describe the wrong moment. Compare source, queue and payload values before blaming a reporting window.
Tracker Migration Without Losing Conversions
Changing trackers is easy; changing them mid-flight is not. Every click already sent to the old tracker expects its postback at the old address, and every platform window keeps running. This guide lays out the migration order that loses nothing: parallel running, postback continuity, cutover sequencing, and the checks that close each stage.
Voluum S2S Tracking: The Postback Contour From Click to Platform
Voluum's S2S contour is one loop: a token rides the click to the offer, and the affiliate network returns it in a postback whose cid parameter carries the value back home. This guide walks the loop - token propagation, the postback URL, platform integrations - and the verification that proves every conversion completes the circuit.
RedTrack Conversions API: One Conversion, Several Platforms
One click, several ad platforms that deserve to hear about its conversion. RedTrack's CAPI integrations make that a configuration job rather than a coding one: the clickid token matches conversions through S2S postbacks, and each platform integration maps those conversions into its own events. This guide walks the multi-platform setup with the documented fields, matching rules, and dedup pitfalls.
Binom Postback: Conversion Delivery to Ad Platforms
Binom's postback contour follows one rule: the {clickid} token goes out with every click, and the network returns it in a postback so the tracker can match the conversion. This guide walks the contour end to end - the postback v2 URL and its parameters, statuses and upsell sums, currency - and then the delivery hop that turns matched conversions into Conversions API events.
Keitaro Macros: The S2S Postback and Sub ID Reference
Every Keitaro S2S postback is a template, and the placeholders are its vocabulary. This reference collects the documented macros in working groups - identifiers, money, statuses with mappings, timestamps, campaigns and offers, geo and device - plus the sub ID fields and the encoding and currency rules that keep substituted URLs intact.
Keitaro Cost Import: Facebook Ad Spend Into Your Tracker
ROI without imported spend is a guess. Keitaro's Facebook Costs integration pulls ad spend straight from your ad account into tracker reports - and this guide wires it end to end: the integration fields, the {{adset.id}} parameter requirement that silently breaks everything when missing, the Marketing API token, the update schedule, and the troubleshooting list.
Keitaro Conversion Status: What to Do With Each
Every Keitaro conversion carries a status - and the status decides what leaves the tracker, what reaches the platform, and what only lives in reports. This guide walks the documented status list, the transition rules that keep records honest, the status-to-event mapping that feeds your pixels, and the correction each status allows.
Keitaro S2S Postback: Setup From Scratch
The S2S postback is the exit through which every Keitaro conversion reaches a traffic source or an ad platform - and its setup decides what leaves the tracker and what stays behind. This guide builds the setup from an empty campaign: postback URL anatomy, the placeholders that matter, status-based routing, queue behavior, and the log checks that prove each delivery.
Offer Rotation Tracking: Many Offers, One Pixel, No Mixed Conversions
Rotating three offers through one pixel is safe; rotating them through one event name is not. This guide wires offer rotation tracking so every conversion stays attached to the offer that produced it - click-side labeling, per-offer events and values, custom conversions per offer, and the traps that quietly merge your offers' data.
Tracker ROI vs ROAS: Why the Numbers Never Match
The tracker computes ROI on confirmed payouts; Ads Manager computes ROAS on the revenue value inside the events you sent. Two different numerators over two different denominators - and both are correct. This guide walks every documented reason the money numbers diverge, then gives a reconciliation procedure that separates counting rules from real leaks.
Subscription Conversion Events: Mapping a Recurring Funnel
A subscription funnel produces many money moments - trial start, first payment, every rebill - and one flat Purchase cannot carry them. This guide maps each stage to its event, wires rebill identity through the tracker, handles cancellations, and draws the line between what the platform can attribute and what only your tracker knows.
COD Approve Rate Tracking: Which Event Fires on Confirmation
In COD offers the sale is not real until a call center says so. This guide wires the two-event stream - lead at registration, sale on confirmed approval - through the tracker's statuses, explains how approve rate shapes what you feed the platform, and keeps confirmation lag inside the platform's acceptance window.
FTD Custom Event: Deposits as Optimization Signals
Registrations tell the platform someone signed up; deposits tell it someone paid. This guide wires deposits and first-time deposits into your ad platforms as custom events - tracker statuses, the standard-versus-custom choice, custom conversions for optimization, deposit value, and the timing rules that decide whether a late deposit still counts.
Duplicate Conversions Tracker: Three Systems, Three Numbers
The tracker says 80, the network balance says 74, Ads Manager says 92 - and all three are working as documented. This guide separates genuine duplicate conversions from counting-rule differences, walks the dedup mechanisms each system actually provides, and gives a reconciliation procedure that finds the one real bug hiding among the definitional noise.
Conversion Value Payout: Passing Affiliate Payout as Event Value
A flat Purchase counts actions; a Purchase with the network's payout counts money. This guide traces the payout number from the network postback into the event's value and currency fields, then through the messy parts - partial approvals, rebills, clawbacks, and currency mismatches - to a value policy the algorithm can actually optimize on.
Conversion Hold Status: Which Conversions Belong in Your Pixel
The network confirmed a lead, put it on hold, and will approve or reject it in a week. Your pixel needs to know now. This guide sorts out which conversion statuses deserve a platform event, when to send them so they still count, and how to correct the record when a held conversion resolves the wrong way.
From CPA Network Postback to Conversions API: Where the Chain Breaks
Between a conversion confirmed by a CPA network and a conversion counted by the ad platform stand two handoffs: the postback into your tracker and the server event out of it. This guide walks both contracts, lists the documented ways each one tears, and shows how to put a broken chain back together.
Server-Side Conversions Without Site Access: A Media Buyer's Playbook
The conversion happens on a page you will never edit. Here is the working path from that page back to the ad platform: what you actually control, how the server event gets built, what the landing domain's absence costs in match keys, and how to test before scaling.
Affiliate Conversion Tracking: The Complete Guide
The entry point to our affiliate tracking cluster: how a conversion that lands on someone else's offer travels through a postback, a tracker, and a Conversions API call, and where each specific failure has its own deep-dive guide.
Tracking Stack: MMP + Tracker + CAPI for App-Install Campaigns
A practical assembly guide for an app-install tracking stack: which layer measures installs, which one keeps your ROI reporting, how an event ID travels from ad click to Meta CAPI and the TikTok Events API, and which checks prove the stack works before you scale spend.
Keitaro vs Binom vs Voluum vs RedTrack: Full Comparison for Media Buyers
A side-by-side comparison of four affiliate trackers: self-hosted versus cloud hosting, current pricing pages, event limits, Meta CAPI and TikTok Events API support, postback mechanics, and clear scenarios for choosing between them without overpaying.
TikTok Events API Affiliate Trackers: Setup Guide
A practical guide to sending conversions from affiliate trackers to TikTok Events API: ttclid, user_data hashing, deduplication, attribution windows, testing, and troubleshooting.
TikTok Conversion Discrepancy: Ads Manager vs Events API vs Third-Party Tracker
Five root causes of TikTok conversion discrepancy and a diagnostic workflow to reconcile Ads Manager, Events API, and third-party tracker data.
Server Side Conversion Delivery: From MMP and Tracker to Meta and TikTok CAPI
A practical map of the app-install conversion chain: who generates the click ID, where postbacks carry it, what Meta CAPI and the TikTok Events API expect from every event, and where the chain usually breaks.
rdt_cid: The Reddit Click ID From Ad Click to CAPI Payload
The Reddit click id (rdt_cid) is the strongest match key a Reddit conversion event can carry. Where it appears, where it breaks, and the chain that delivers it to the CAPI payload.
Postback vs Conversions API: Two Server Channels With Different Jobs
A postback tells your tracker about a conversion; the Conversions API tells the ad platform. They are not rivals - most profitable funnels run both.
Postback Not Firing? 12-Point Troubleshooting Checklist for Keitaro, Binom, and Voluum
A 12-point checklist for postback not firing problems in Keitaro, Binom, and Voluum. Verify the click ID round trip, tokens, statuses, payout, response codes, and logs, then escalate to the network with evidence instead of guessing.
MMP Postback to CAPI Mapping: How an MMP Event Becomes a Platform Server Event
An MMP postback and a Conversions API payload describe the same conversion in different vocabularies. The mapping layer: click identity, event names, revenue, and hashed identifiers, field by field.
fbclid ttclid: Keeping Click IDs Alive Through Your Funnel
One rewritten URL and your Meta or TikTok conversions stop attributing. The official mechanics of fbclid and ttclid, and a preservation checklist.
Keitaro Snapchat Integration: Tracker Postbacks Into the Conversions API
Keitaro records the conversion; Snap's Conversions API needs the match key. The Keitaro Snapchat wiring: traffic source, S2S postback, and a delivery layer that assembles Snap's payload.
Keitaro Reddit Integration: Tracker Postbacks Into the Conversions API
Keitaro records the conversion; Reddit's Conversions API needs it in a specific shape. The Keitaro Reddit wiring: custom traffic source, rdt_cid capture, S2S postback, and the delivery layer that formats the v3 payload.
Keitaro Postback Setup for Facebook and TikTok Conversions
Wire Keitaro goal postbacks into Facebook CAPI and TikTok Pixel, then verify delivery in each platform's events panel.
Keitaro Pinterest Integration: Tracker Postbacks Into the Conversions API
Keitaro records the conversion; Pinterest's Conversions API needs it in a specific shape. The Keitaro Pinterest wiring: traffic source, S2S postback, and a delivery layer that formats the v5 payload.
Keitaro ChatGPT Ads Integration: oppref Capture, Postbacks, and the CAPI Gap
Keitaro has no ChatGPT Ads preset yet - here is the manual traffic source setup, oppref capture, and the postback-to-CAPI bridge that closes the loop.
Facebook CAPI Custom Conversions for Affiliate Offers: Setup Without a Website
A practical guide for affiliates who need to fire Facebook CAPI custom conversions through tracker postbacks because they have no pixel on the advertiser domain.
Facebook Conversion Discrepancy: Why Ads Manager and Your Tracker Show Different Numbers
Why Facebook Ads Manager and your affiliate tracker disagree on conversions, and how to reconcile the numbers without losing budget insight.
Cross-Platform Conversion Parameters Matrix: One Event, Six Networks
Routing one conversion to Meta, TikTok, Reddit, Snap, Pinterest, and Google? This matrix maps which deduplication and click parameter each network expects.
Cookieless Attribution for Affiliate Marketing: What Actually Works
Server-side tracking, Meta CAPI, TikTok Events API, and Consent Mode v2 assembled into a post-cookie attribution stack for affiliate teams.
Binom Facebook CAPI Integration: From Tracker Postback to Conversions API
Binom tracks the conversion; Meta's Conversions API needs a server event. Here is the documented architecture that connects the two without guesswork.
Server-Side Tracking for Performance Marketing: How the Stack Works in 2026
A conceptual entry point to server-side tracking for performance marketers. See how the pipeline is built, when browser pixels stop being enough, which stacks exist, and where to go next for Meta CAPI, TikTok Events API, and sGTM migration details.
MMP vs Affiliate Tracker: Key Differences, Overlaps, and When You Need Both
A practical breakdown of MMPs, affiliate trackers, postbacks, CAPI delivery, and the stack media buyers need for app-install and web campaigns.
Facebook CAPI Keitaro setup guide without losing conversions
A step-by-step breakdown of the Keitaro and Facebook Conversions API integration: the built-in module, a manual postback build, the fbc-from-fbclid format, deduplication, and Event Match Quality.