Mistake: postback fires on pending, not approved
Failure mode: the network sends the postback the instant a lead is captured, before fraud and quality checks. Your tracker shows green, you scale, then 40% of those leads get scrubbed and the postback for the reversal never arrives.
Fix — 5 steps:
— Identify which event your postback is bound to: lead created (pending) or lead approved (confirmed). Ask the affiliate manager directly; do not assume.
— Bind your primary conversion to the approved status. Track pending as a separate, secondary event for early signal only.
— Configure a reversal postback (status=rejected) so scrubbed leads decrement your count automatically.
— In Keitaro: map statuses to conversion states. In Voluum: use the status parameter in the postback URL.
— Watch the gap between pending and approved counts. A widening gap is a quality problem, not a tracking one.
Verify: ask the network to fire one test approval and one test reversal. Both must move your numbers correctly.
Save this SOP. Run this before every launch.
Tracker Playbook
@TrackerPlaybook
Mistake: postback fires on pending, not approved
Этот пост опубликован в Telegram-канале Tracker Playbook. Подписаться можно по ссылке: @TrackerPlaybook.