Library · Traffic · How to run this
Postback latency is not postback fail rate
p95 postback ms vs timeout ms make over-threshold %. Over-threshold % = max(0, (p95 − timeout) ÷ timeout × 100). Type both.
Pair: Postback latency p95 on Traffic. Fail $: postback fail rate. Payout clock: approved-to-paid lag.
What you type
p95 postback ms — 95th-percentile postback round-trip in the TUNE window.
Timeout ms — the timeout you hold postbacks to in that same window.
Over-threshold % = max(0, (p95 − timeout) ÷ timeout × 100). Fix endpoint / queue when over-threshold % is fat — do not invent a latency chip.
What not to do
Do not invent over-threshold %. Do not mix failed posts into p95 ms. Do not treat payout lag days as postback latency. Do not average every offer when one owns the hole.
Related: Traffic, postback fail rate, approved-to-paid lag, postback dedupe window.
Procedure
- Type p95 postback ms and timeout ms.
- Read over-threshold %.
- Fix endpoint / queue when over-threshold % is material.
Failure modes
- Inventing over-threshold %.
- Mixing failed posts into p95 ms.
- Treating payout lag days as postback latency.
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
- Postback latency over-threshold %
- How far p95 postback ms exceeds timeout ms, as a percent of timeout.
Work with us — We run this job on your accounts. Services
FAQ
- Is this postback fail rate?
- Sibling post grain. [Postback fail rate](/manuals/redtrack-postback-fail-rate) prices failed posts × CPA. This page is p95 postback ms vs timeout on TUNE.
- Is this approved-to-paid lag?
- Related TUNE clock. [Approved-to-paid lag](/manuals/tune-approved-to-paid-lag) is approval day to paid day. This page is postback latency p95.
- What over-threshold % should I invent?
- None. Type p95 postback ms and timeout ms from the same TUNE window.