Skip to article
ecomservices.io
Traffic · How to run this
TargetsCalculatorContributionNot on this page yetPlatformsCalculatorTrackersCalculatorAudiencesNot on this page yetLandingsCalculatorAttributionCalculatorAffiliatesCalculatorPacingNot on this page yetOptimisationCalculatorImplementationNot on this page yet

Library · Traffic · How to run this

RedTrack tracker-fire ledger is not MaxWeb subid-fire clock

How to run thisTraffic3 steps
CalculatorRedTrack click-to-postback lag · Calculator lives in the articleOpen

Grab one RedTrack tracker-fire ledger. Note when the postback returned. Subtract when the tracker click landed. Park clicks next to that span. The span is RT tracker-fire lag hours — MaxWeb subid-fire clocks stay off this ledger.

Pair: Click-to-postback lag on Traffic. MaxWeb twin: MW subid-fire. Veto twin: RT lander-veto.

Tracker-fire ledger columns

Click stamp — Hour RedTrack recorded the tracker click.

Postback stamp — Hour the conversion postback landed on that tracker-fire ledger.

Clicks — Tracker-fire rows on that click → postback slice.

RT tracker-fire lag hours = postback stamp − click stamp. Rising RT tracker-fire lag hours means chase the RedTrack postback desk — leave empty chips empty.

Refuse these shortcuts

Refuse inventing RT tracker-fire lag hours. Refuse loading MaxWeb subid-fire or Digistore24 offer-fire CSVs into RedTrack tracker-fire ledgers. Refuse pasting pixel/postback dollar gaps into hour fields. Refuse fusing campaigns when one RedTrack tracker owns the fire pile.

See also: Traffic, MW subid-fire, RT lander-veto, click-id miss.

Procedure

  1. Type click stamp, postback stamp, and clicks.
  2. Read RT tracker-fire lag hours.
  3. Chase postback desk latency when RT tracker-fire lag hours are material.

Failure modes

  • Inventing RT tracker-fire lag hours.
  • Loading MaxWeb subid-fire or Digistore24 offer-fire CSVs into RedTrack boxes.
  • Folding pixel/postback dollar gaps into hour fields.

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 tracker-fire lag hours
Postback stamp − Click stamp on one RedTrack tracker-fire ledger.

Work with us — We run this job on your accounts. Services

FAQ

Is this MaxWeb click-to-postback lag?
RedTrack tracker-fire ledger vs MaxWeb subid-fire ledger. [Click-to-postback lag](/manuals/maxweb-click-to-postback-lag) stays on MaxWeb. Click / postback stamps belong on this RedTrack ledger.
Is this RedTrack creative reject share?
Tracker-fire latency vs lander veto rate. [Creative reject share](/manuals/redtrack-creative-reject-share) ratios vetoed landers. Here you align postback stamp against click stamp on fires.
What RT tracker-fire lag hours should I invent?
None. Source click stamp, postback stamp, and clicks from the same RedTrack tracker-fire ledger.