Library · Traffic · How to run this
TUNE network postback silence is not payout hold
Score never-landed fires against owed fires on one TUNE network book. That ratio × 100 is TN postback-miss %.
Pair: Postback-miss share on Traffic. Tracker twin: RedTrack miss. Hold twin: payout hold.
Network fields
Never-landed fires — TUNE conversion pings the endpoint never recorded.
Owed fires — TUNE conversion pings the network book said that offer owed in the same window.
TN postback-miss % = never-landed fires ÷ owed fires × 100. Hot TN postback-miss % means lander or CRM wiring on that TUNE offer — chase it; leave blank chips alone.
Guardrails
Skip inventing TN postback-miss %. Skip parking payout-hold rows in the never-landed pile. Skip pasting RedTrack miss exports into TUNE boxes. Skip blending offers when one TUNE advertiser owns the silent gap.
Related: Traffic, RedTrack miss, payout hold, click-id miss.
Procedure
- Type missed postbacks and expected postbacks.
- Read TN postback-miss %.
- Chase lander / CRM fire wiring when TN postback-miss % is material.
Failure modes
- Inventing TN postback-miss %.
- Folding payout-hold rows into the miss count.
- Folding RedTrack miss rows into TUNE boxes.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- TN postback-miss %
- Missed postbacks ÷ expected postbacks × 100 on one TUNE network book.
Work with us — We run this job on your accounts. Services
FAQ
- Is this RedTrack postback-miss share?
- TUNE network book vs RedTrack tracker book. [Postback-miss share](/manuals/redtrack-postback-miss-share) stays on RedTrack. Landed / owed totals never leave TUNE here.
- Is this TUNE payout-hold share?
- Silent conversion vs held payouts. [Payout-hold share](/manuals/tune-payout-hold-share) scores held payouts. Here you only score conversion fires that never landed.
- What TN postback-miss % should I invent?
- None. Pull never-landed fires and owed fires from the same TUNE network book.