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