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

Everflow offer-fire clock is not Affise click-fire ledger

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

Open one Everflow offer-fire board. Note the postback mark. Subtract the click mark. That span is EF offer-fire lag hours. Keep clicks beside the span so volume stays honest.

Pair: Click-to-postback lag on Traffic. Affise twin: AF click-fire. Cash twin: EF approved-paid lag.

Offer-fire columns

Click mark — Hour Everflow recorded the click on the offer-fire board.

Postback mark — Hour that conversion fired back as a postback on the same board.

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

EF offer-fire lag hours = postback mark − click mark. Rising EF offer-fire lag hours means chase the Everflow advertiser postback desk — leave empty chips empty.

Hard stops

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

Related: Traffic, AF click-fire, EF approved-paid lag, postback-miss.

Procedure

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

Failure modes

  • Inventing EF offer-fire lag hours.
  • Dumping Affise click-fire CSVs into Everflow 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

EF offer-fire lag hours
Postback mark − Click mark on one Everflow offer-fire board.

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

FAQ

Is this Affise click-to-postback lag?
Everflow offer-fire board vs Affise click-fire ledger. [Click-to-postback lag](/manuals/affise-click-to-postback-lag) stays on Affise. Click / postback marks belong on this Everflow board.
Is this Everflow approved-to-paid lag?
Offer-fire clock vs payout-post clock. [Approved-to-paid lag](/manuals/everflow-approved-to-paid-lag) aligns pay against approve. Here you align postback mark against click mark on fires.
What EF offer-fire lag hours should I invent?
None. Source click mark, postback mark, and clicks from the same Everflow offer-fire board.