Library · Traffic · How to run this
Click-to-conversion lag is not paid lag
Conversion day − click day make lag days. Type both plus clicks.
Pair: Click-to-conversion lag on Traffic. Payout: approved-to-paid lag. Postback: postback latency p95.
What you type
Click day — day index when the TUNE click fired.
Conversion day — day index when that cohort’s conversion posted on TUNE.
Clicks — clicks in that same lag window.
Lag days = conversion day − click day. Widen the conversion window or fix delayed posts when lag days are fat. Do not invent a lag chip.
What not to do
Do not invent lag days. Do not fold payout-hold days into click indexes. Do not paste MaxWeb sale lag onto a TUNE offer. Do not blend SubIDs when one offer owns the lag.
Related: Traffic, approved-to-paid lag, postback latency p95, click-to-sale lag.
Procedure
- Type click day, conversion day, and clicks.
- Read lag days.
- Retune postback / offer windows when lag days are material.
Failure modes
- Inventing lag days.
- Mixing approved-to-paid into day indexes.
- Treating MaxWeb sale lag as TUNE conversion lag.
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-conversion lag days
- Conversion day − click day.
Work with us — We run this job on your accounts. Services
FAQ
- Is this approved-to-paid lag?
- Cash clock. [Approved-to-paid lag](/manuals/tune-approved-to-paid-lag) is payout day after approve. This page is conversion day − click day.
- Is this click-to-sale lag?
- Different network grain. [Click-to-sale lag](/manuals/maxweb-click-to-sale-lag) is MaxWeb sale day. This page is TUNE conversion lag on the tracker.
- What lag days should I invent?
- None. Type click day, conversion day, and clicks from the same TUNE export.