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

Affise click-to-fire clock is not approved-to-paid lag

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

Open one Affise click-fire ledger. Note the postback stamp. Subtract the click stamp. That span is AF click-fire lag hours. Keep clicks beside the span so volume stays honest.

Pair: Click-to-postback lag on Traffic. Cash twin: AF approved-paid lag. Dollar twin: AF pixel-postback.

Click-fire columns

Click stamp — Hour Affise recorded the click on the click-fire ledger.

Postback stamp — Hour that conversion fired back as a postback on the same ledger.

Clicks — Row count on that Affise click → postback cut.

AF click-fire lag hours = postback stamp − click stamp. Rising AF click-fire lag hours means chase the Affise advertiser postback desk — leave empty chips empty.

Hard stops

Do not invent AF click-fire lag hours. Do not load pixel/postback dollar gaps into hour boxes. Do not paste TUNE click-to-sale CSVs into Affise fields. Do not fuse offers when one Affise advertiser owns the click-fire pile.

Related: Traffic, AF approved-paid lag, AF pixel-postback, postback-miss.

Procedure

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

Failure modes

  • Inventing AF click-fire lag hours.
  • Dumping pixel/postback dollar gaps into hour boxes.
  • Folding TUNE click-to-sale CSVs into Affise 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

AF click-fire lag hours
Postback stamp − Click stamp on one Affise click-fire ledger.

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

FAQ

Is this Affise approved-to-paid lag?
Click-fire clock vs cash-post clock. [Approved-to-paid lag](/manuals/affise-approved-to-paid-lag) aligns pay against approve. Here you align postback stamp against click stamp on fires.
Is this Affise pixel-vs-postback gap?
Fire lag hours vs dollar credit gap. [Pixel-vs-postback gap](/manuals/affise-pixel-vs-postback-gap) stacks pixel $ against postback $. Here you only measure postback stamp minus click stamp.
What AF click-fire lag hours should I invent?
None. Source click stamp, postback stamp, and clicks from the same Affise click-fire ledger.