Are your newest campaigns being unfairly penalized by math?
The question: you compare last week's campaign to last quarter's and the new one looks worse. But conversions take time to land. Could the comparison itself be structurally rigged against anything recent?
What's happening: yes — this is conversion lag bias (sometimes called the delayed-feedback or attribution-maturation problem). Conversions arrive on a distribution: some same-day, many over the following days and weeks. Any campaign you measure 'now' has only collected its early conversions; its long-tail hasn't matured. Compared against a fully-matured older campaign, the recent one looks artificially weak — not because it performed worse, but because it isn't done converting.
What the research formalizes: delayed-feedback models in computational advertising treat each conversion's delay as a random variable and model the survival curve, so a campaign's expected final performance can be estimated before all conversions land. Without that correction, optimization systems that judge campaigns too early will systematically kill long-cycle channels prematurely — the channels whose conversions arrive slowest get cut before they can prove themselves.
The nuance: the bias is worst for considered purchases and B2B, negligible for impulse e-commerce. It also interacts nastily with the attribution window — a short window plus lag bias double-penalizes long cycles.
What to actually do: never compare a fresh campaign's raw conversions to a matured one's. Either wait for maturation or model the lag curve and compare projected finals. Build a 'cohort maturity' check into reporting.
Bottom line for practitioners: recent campaigns aren't underperforming, they're under-aged. Compare like-aged cohorts or you'll execute your slowest-converting channels for the crime of being measured too soon.
Credit Where Due
@CreditWhereDue
Are your newest campaigns being unfairly penalized by math?
Этот пост опубликован в Telegram-канале Credit Where Due. Подписаться можно по ссылке: @CreditWhereDue.