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

Voluum campaign-fire ledger is not RedTrack tracker-fire clock

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

Open one Voluum campaign-fire ledger. Mark when the postback landed. Subtract when the campaign click fired. Park clicks beside that span. The span is VL campaign-fire lag hours — RedTrack tracker-fire clocks stay off this ledger.

Pair: Click-to-postback lag on Traffic. RedTrack twin: RT tracker-fire. Reject twin: VL postback-reject.

Campaign-fire ledger columns

Click stamp — Hour Voluum recorded the campaign click.

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

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

VL campaign-fire lag hours = postback stamp − click stamp. Rising VL campaign-fire lag hours means chase the Voluum postback desk — leave empty chips empty.

What not to do

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

Related: Traffic, RT tracker-fire, VL postback-reject, click-id miss.

Procedure

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

Failure modes

  • Inventing VL campaign-fire lag hours.
  • Loading RedTrack tracker-fire or MaxWeb subid-fire CSVs into Voluum 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

VL campaign-fire lag hours
Postback stamp − Click stamp on one Voluum campaign-fire ledger.

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

FAQ

Is this RedTrack click-to-postback lag?
Voluum campaign-fire ledger vs RedTrack tracker-fire ledger. [Click-to-postback lag](/manuals/redtrack-click-to-postback-lag) stays on RedTrack. Click / postback stamps belong on this Voluum ledger.
Is this Voluum postback-reject share?
Campaign-fire latency vs rejected postback rate. [Postback-reject share](/manuals/voluum-postback-reject-share) ratios rejected postbacks. Here you align postback stamp against click stamp on fires.
What VL campaign-fire lag hours should I invent?
None. Source click stamp, postback stamp, and clicks from the same Voluum campaign-fire ledger.