Library · Traffic · How to run this
Sale lag is not geo bleed
Sale day − click day make lag days. Type both plus clicks.
Pair: Click-to-sale lag on Traffic. Cap: geo-cap exhaustion. Credits: conversion lag bucket.
What you type
Click day — day index of the affiliate click in your window.
Sale day — day index of the attributed sale for that click cohort.
Clicks — clicks in that same lag window.
Lag days = sale day − click day. Retune postback or offer windows when lag days are fat — do not invent a lag chip.
What not to do
Do not invent lag days. Do not mix geo-cap fill into day indexes. Do not treat CPA dollars as clicks. Do not average every SubID when one owns the lag.
Related: Traffic, geo-cap exhaustion, conversion lag bucket, SubID fraud cut.
Procedure
- Type click day, sale day, and clicks.
- Read lag days.
- Retune postback windows when lag days are material.
Failure modes
- Inventing lag days.
- Mixing geo-cap fill into day indexes.
- Treating CPA dollars as clicks.
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
- Click-to-sale lag days
- Sale day − click day for the typed click cohort.
Work with us — We run this job on your accounts. Services
FAQ
- Is this geo-cap exhaustion?
- Sibling MaxWeb clock. [Geo-cap exhaustion](/manuals/maxweb-geo-cap-exhaustion) is mid-day cap fill. This page is sale day − click day.
- Is this conversion lag bucket?
- Related affiliate lag. [Conversion lag bucket](/manuals/everflow-conversion-lag-bucket) prices delayed credits × CPA. This page is click-to-sale lag days.
- What lag days should I invent?
- None. Type click day, sale day, and clicks from the same MaxWeb window.