Library · Traffic · How to run this
Click-to-CRM lag is not campaign disapproval
CRM hit day minus Outbrain click day is CRM lag days. Type those two plus click rows.
Pair: Click-to-CRM lag on Traffic. Gate: campaign disapproval rate. Funnel: article-to-offer drop.
What you type
Outbrain click day — day index of the native click cohort.
CRM hit day — day index when that cohort first hits CRM.
Click rows — click rows in that same cohort window.
CRM lag days = CRM hit day − Outbrain click day. Patch pixel / lander when CRM lag days run long — do not invent a CRM lag chip.
What not to do
Do not invent CRM lag days. Do not fold disapproval counts into day indexes. Do not treat article-to-offer drop % as lag days. Do not blend every campaign when one lander owns the delay.
Related: Traffic, campaign disapproval rate, article-to-offer drop, click-to-sale lag.
Procedure
- Type click day, CRM landing day, and clicks.
- Read lag days.
- Fix pixel / landing when lag days are material.
Failure modes
- Inventing lag days.
- Mixing campaign disapprovals into day indexes.
- Treating article-to-offer drop as lag days.
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-CRM lag
- CRM landing day − click day.
Work with us — We run this job on your accounts. Services
FAQ
- Is this campaign disapproval rate?
- Sibling Outbrain gate. [Campaign disapproval rate](/manuals/outbrain-campaign-disapproval-rate) is disapproved ÷ submitted. This page is CRM hit day − Outbrain click day.
- Is this click-to-sale lag?
- Related affiliate clock. [Click-to-sale lag](/manuals/maxweb-click-to-sale-lag) is sale day − click day. This page is native click → CRM hit lag only.
- What CRM lag days should I invent?
- None. Type Outbrain click day, CRM hit day, and click rows from the same window.