Library · Traffic · How to run this
MaxWeb subid-fire ledger is not Digistore24 offer-fire clock
Pull one MaxWeb subid-fire ledger. Mark when the postback landed. Subtract when the subid click fired. Park clicks beside that span. The span is MW subid-fire lag hours — Digistore24 offer-fire clocks stay off this ledger.
Pair: Click-to-postback lag on Traffic. Digistore twin: DS offer-fire. Cash twin: MW approved-paid lag.
Subid-fire ledger columns
Click stamp — Hour MaxWeb recorded the subid click.
Postback stamp — Hour the conversion postback landed on that subid-fire ledger.
Clicks — Subid-fire rows on that click → postback slice.
MW subid-fire lag hours = postback stamp − click stamp. Rising MW subid-fire lag hours means chase the MaxWeb network postback desk — leave empty chips empty.
Hard stops
Do not invent MW subid-fire lag hours. Do not load Digistore24 offer-fire or Deluxe Ads pub-fire CSVs into MaxWeb subid-fire ledgers. Do not paste pixel/postback dollar gaps into hour fields. Do not fuse offers when one MaxWeb network owns the fire pile.
See also: Traffic, DS offer-fire, MW approved-paid lag, click-id miss.
Procedure
- Type click stamp, postback stamp, and clicks.
- Read MW subid-fire lag hours.
- Chase postback desk latency when MW subid-fire lag hours are material.
Failure modes
- Inventing MW subid-fire lag hours.
- Loading Digistore24 offer-fire or Deluxe Ads pub-fire CSVs into MaxWeb 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
- MW subid-fire lag hours
- Postback stamp − Click stamp on one MaxWeb subid-fire ledger.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Digistore24 click-to-postback lag?
- MaxWeb subid-fire ledger vs Digistore24 offer-fire ledger. [Click-to-postback lag](/manuals/digistore-click-to-postback-lag) stays on Digistore24. Click / postback stamps belong on this MaxWeb ledger.
- Is this MaxWeb approved-to-paid lag?
- Subid-fire latency vs cash-post clock. [Approved-to-paid lag](/manuals/maxweb-approved-to-paid-lag) aligns pay against approve. Here you align postback stamp against click stamp on fires.
- What MW subid-fire lag hours should I invent?
- None. Source click stamp, postback stamp, and clicks from the same MaxWeb subid-fire ledger.