Attribution lag is the gap between when a marketing touch happens and when the revenue it contributed to gets recorded. A buyer reads a benchmark report in February, becomes an opportunity in May, and signs in September. The cost landed in Q1. The credited revenue lands in Q3.
Why lag makes new spend look weak
Most marketing reports compare spend and credited revenue inside the same period. That structure punishes any channel with a long path to close. February spend is measured against revenue credited in February, and that revenue came from touches that happened last year. New campaigns carry full cost with no matured revenue behind them, so their in-period return reads low even while they perform well.
The distortion grows with growth. A team that raises spend 40% quarter over quarter will watch reported return decline every quarter, because the denominator expands faster than the lagged revenue in the numerator.
Lag is not the attribution window
The attribution window is a rule you choose: how far back the model looks when assigning credit. Attribution lag is a property of your buying process. Setting a 90 day window on a business with a 210 day median cycle does not shorten anything. It deletes the touches that started the deals.
| Concept | What it is | Who sets it |
|---|---|---|
| Attribution window | Lookback rule inside the model | RevOps configures it |
| Attribution lag | Real elapsed time from touch to close | The buying committee sets it |
Report by touch cohort, not close date
Group every opportunity under the month of its first credited touch, then let that cohort mature. A February cohort keeps accumulating pipeline and closed revenue for several quarters, and you read its return as a curve instead of a snapshot.
Two practices make cohort reporting usable:
- Publish a maturation curve per channel showing the share of eventual pipeline that appears at 30, 90, and 180 days after touch. Once the curve stabilizes, you can project a young cohort's full value from its early share. - Pair a leading pipeline number with the lagging revenue number so budget calls are not made only on revenue that has finished maturing.
Forecasting teams solve the same problem by modeling creation instead of waiting for it. ORM customer data shows that of the pipeline carrying in-quarter close dates on day one of a quarter, roughly 20% closes in that quarter, so most of the period's revenue comes from motion that is not visible yet. Marketing return behaves the same way, and forecast accuracy improves when the model expects the lag rather than reacting to it.
Frequently Asked Questions
How long is attribution lag in B2B SaaS?
It equals the median time from first credited touch to closed won, which is always longer than opportunity age because it includes the pre-opportunity research period. Measure it from your own data by taking closed-won deals from the last four quarters and calculating the days between the earliest credited touch and the close date. Report the median and the 75th percentile, because the tail drives most of the reporting distortion.
Does a longer attribution window fix attribution lag?
No. The window controls how far back the model looks for touches. The lag is set by how long buyers take. Widening the window from 90 to 365 days recovers early touches that would otherwise be dropped, which improves credit accuracy, but the revenue still arrives months after the spend. The reporting fix is cohorting, not window length.
How do you compare two channels with different lags?
Compare them at the same maturity point. If paid search converts to pipeline in 20 days and field events take 120 days, a same-quarter return comparison will always favor paid search. Group each channel into monthly touch cohorts and compare pipeline per dollar at day 90 for both, then again at day 180.
Should you cut a channel that shows no return this quarter?
Not on that evidence alone. Check the channel maturation curve first. If the cohort is younger than the median time to opportunity for that channel, the missing revenue is expected and cutting spend removes pipeline you already paid to start.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like attribution lag into prescriptive action for your team.
Schedule a Demo