Library · Traffic · How to run this
Voluum click-path fire SLA rack is not RedTrack tracker fire SLA shelf
Sit on one Voluum click-path fire SLA rack. Count S2S conversion fires that blew the click-path fire SLA. Divide by fires the campaign book still owed. Multiply by 100 for VL postback-timeout %. RedTrack tracker fire SLA shelves and MaxWeb offer fire deadline boards stay off this Voluum rack.
Pair: Postback-timeout share on Traffic. RedTrack twin: RT postback-timeout. Miss twin: VL postback-miss.
Click-path fire SLA columns
Timed-out postbacks — Voluum S2S fires the SLA rack marked past-click-path-deadline / SLA-expired.
Expected postbacks — Voluum S2S fires the campaign book says that path still owed.
VL postback-timeout % = timed-out postbacks ÷ expected postbacks × 100. A fat VL postback-timeout % chip means chase click-path endpoint latency on that rack — leave blank chips alone.
Guardrails
Do not invent VL postback-timeout %. Do not fold silent-gap or creative-reject rows into the SLA-expired tally. Do not paste RedTrack tracker-SLA or MaxWeb offer-deadline timeout CSVs into Voluum racks. Do not blend campaigns when one Voluum click-path owns the SLA cut.
Related: Traffic, RT postback-timeout, VL postback-miss, VL postback-kill.
Procedure
- Type timed-out postbacks and expected postbacks.
- Read VL postback-timeout %.
- Chase click-path fire SLA latency when VL postback-timeout % is material.
Failure modes
- Inventing VL postback-timeout %.
- Folding silent-gap or creative-reject rows into the SLA-expired tally.
- Pasting RedTrack tracker-SLA or MaxWeb offer-deadline timeout CSVs into Voluum racks.
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
- VL postback-timeout %
- Timed-out S2S fires ÷ owed fires × 100 on one Voluum click-path fire SLA rack.
Work with us — We run this job on your accounts. Services
FAQ
- Is this RedTrack postback-timeout share?
- Voluum click-path fire SLA rack vs RedTrack tracker fire SLA shelf. [Postback-timeout share](/manuals/redtrack-postback-timeout-share) stays on RedTrack. Timed-out / owed totals belong on this Voluum rack.
- Is this Voluum postback-miss share?
- SLA clock-out vs silent S2S gap. [Postback-miss share](/manuals/voluum-postback-miss-share) counts fires that never arrived. Here you count S2S fires Voluum stamped past the click-path fire SLA.
- What VL postback-timeout % should I invent?
- None. Source timed-out S2S fires and owed fires from the same Voluum click-path fire SLA rack.