What are modeled conversions, and how much should I trust them?
Modeled conversions are estimates the ad platform adds when it cannot observe a conversion directly, usually because of consent choices or browser restrictions. They are defensible at the account and campaign level and unreliable row by row. Use them for budget-scale decisions, not for judging a single keyword or a low-volume ad group, and never try to reconcile them one-for-one against CRM records.
Observed, modeled, and the gap between them
Platforms can still directly observe a portion of conversions. For the rest, they infer: they learn the relationship between observable behavior and conversion among users who can be measured, then apply that relationship to users who cannot. The reported number is a blend of the two, and most interfaces do not label which is which at the row level.
That is not fraud and it is not useless. It is a statistical estimate with an honest purpose, aggregated across a large population. The failure comes from treating an aggregate estimate as if it were a list of specific people.
There is a practical consequence buried in that blend. Modeling needs volume to be stable, so the smaller the slice you are looking at, the noisier the estimate. An account-level number can be quite good while the row for a single ad group with a handful of conversions is close to meaningless, and the interface presents both with the same confidence.
Why they cannot be reconciled to your CRM
A modeled conversion corresponds to no phone number, no email, no service address and no job. There is nothing to match. If your reconciliation process tries to tie every reported conversion to an operational record, modeling will show up as a permanent, unexplained shortfall and someone will spend a week hunting a bug that does not exist.
The correct handling is to compare the two counts as a ratio and monitor its stability, rather than expecting them to converge. A stable ratio means the plumbing is fine. A ratio that moves sharply means something changed in either the modeling or your measurement layer, and that is worth investigating.
Where modeling is safe and where it is not
- Reasonable: comparing campaigns with substantial volume, watching account-level trend, allocating budget between broad strategies.
- Risky: pruning individual keywords, judging a new ad group in its first weeks, any decision resting on a handful of conversions.
- Wrong: using modeled counts as the revenue basis for a client report or a vendor scorecard.
Keep an unmodeled counterweight
Your operational system produces a number nobody models: booked jobs. It is slower, it lags the click, and it is completely real. Holding booked jobs beside platform conversions gives you a stable denominator that privacy changes cannot move.
When those two series diverge, the interesting question is which one moved. That comparison is the backbone of how we build revenue reporting — the platform tells you what it thinks it caused, and the business tells you what actually got sold.
Topics: modeled conversions · consent · privacy · measurement
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.