Guides
Help center for Most conversion automation and pixel activation.
Lead Ads CRM CAPI: Closing the Lead Loop in Meta
A Lead Ads form fills your CRM; the lead that actually buys is the one worth telling Meta about. This guide wires the loop: from the form's instant delivery into your CRM, through confirmation and hashing, to a documented CAPI lead event - with dedup and the seven-day window deciding how late a confirmed lead can still count.
Share Pixel Ad Accounts: One Pixel Across Business Portfolios
One pixel, several ad accounts, maybe another business entirely - and Meta has a documented path for each hop. This guide walks the legitimate sharing contour: only the owning portfolio can share, partners get access through Assign Partners, and ad accounts receive the pixel through connected assets - plus what each side keeps and what the sharing does not change.
FBC FBP Construction: Building _fbc and _fbp by Hand
Server-side events never see the browser's cookies - so buyers construct the _fbc and _fbp values by hand from the data captured at click time. Done right, the format is simple; done wrong, a malformed value silently weakens matching. This guide covers the cookie formats, the fbc-from-fbclid construction, what travels hashed versus unhashed, and the mistakes that break matching.
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.
Pixel Disabled Diagnostics: Reading the Data Side
The pixel looks dead - or the account shows a restriction - and the temptation is to guess. This guide walks the data side instead: what Events Manager and Test Events can prove, how to separate a delivery failure from a quality problem, which fixes restore correct sending, and what to document while you work.
Bot Traffic Filtering Before It Reaches Your Pixel
A bot that converts into a lead poisons three systems at once: the tracker's reports, the network's approve rate, and the platform's optimization. This guide wires bot traffic filtering before the Conversions API hop - what to filter at the tracker, how the filtered labels flow into your event policy, and how to prove the stream stays clean.
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.
Click ID Prelander Loss: Where Click IDs Die
The platform appends its click ID to the ad URL; three hops later your postback arrives with an empty subid, and nobody can say which hop ate it. This guide walks a prelander funnel hop by hop - redirects, meta refresh, iframes, the offer jump - marking where click IDs survive, where they die, and how tracker-side capture and server-side reconstruction keep attribution alive anyway.
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.
Pixel Warming Without Burning Budget: A Practical Sequence
Warming is not a ritual - it is an ordering problem. Verify delivery before spend, feed clean well-attributed events while the baseline forms, and scale on evidence. This guide turns pixel warming into the sequence buyers actually follow, with the platform documentation behind each step and the affiliate-specific twists of warming a pixel you feed by postback.
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.