<b>Conversion reconciliation — weekly 4-step SOP</b>
Your tracker and the network will disagree. The job is knowing by how much and why, before payout day.
Every Monday, for each active offer:
— 1. Pull tracker conversions for the prior 7 days. Pull network-reported conversions for the same window, same timezone. Timezone mismatch alone can show a 'gap' that's just date-boundary noise — normalize first.
— 2. Calculate the match rate: tracker / network. Healthy is 95-100%. Under 90% means lost postbacks; over 100% means you're double-counting.
— 3. For gaps, bucket the missing conversions by hour. A cluster at one hour points to a postback outage or your tracker downtime. A flat smear points to a token/dedup issue.
— 4. Spot-check 5 missing click IDs. Search them in your click log. Present = postback never arrived (network or firewall). Absent = click ID never made it into the funnel (token/redirect break).
Document the variance per offer. A consistent 3% under-count is a known, budgetable leak. A jump to 15% is an incident.
Run this before every payout cycle.
Tracker Playbook
@TrackerPlaybook
<b>Conversion reconciliation — weekly 4-step SOP</b>
Этот пост опубликован в Telegram-канале Tracker Playbook. Подписаться можно по ссылке: @TrackerPlaybook.