Show how an assumed completion fraction changes apparent CPA
Analysis
By Isaac Turner, Measurement Editor — 2 min read
View author profile
Recent conversion totals can still be incomplete. A reproducible synthetic example with editable inputs and explicit limits.
Recent conversion totals can still be incomplete. This lab separates observed CPA from a sensitivity calculation that assumes a fraction of eventual conversions has arrived. The assumption is visible and editable, so a forecast cannot quietly masquerade as a measured result.
Define the calculation before using it
Enter spend, observed conversions and a completion fraction supported by comparable mature cohorts if such evidence exists. Divide observed conversions by that fraction to obtain the scenario total, then calculate spend per scenario conversion. Preserve both outputs in the review. Do not replace the actual conversion count with the adjusted figure in a table labelled observed performance.
Work through the synthetic example
At 1,000 units of spend and 40 observed conversions, measured CPA is 25. If the illustrative completion fraction is 0.8, the scenario contains 50 conversions and a CPA of 20. That difference is an assumption-driven projection. A new product, conversion definition or reporting disruption can make a historical lag pattern inappropriate.
| Output | Worked-example result |
|---|---|
| Observed CPA | 25.0000 |
| Scenario eventual conversions | 50.0000 |
| Scenario CPA | 20.0000 |
Use the artifact and preserve its assumptions
Open the editable calculator to change the inputs and inspect the sensitivity view. The CSV records synthetic inputs and expected outputs; the JSON fixture keeps the equations available for reproduction. These calculations have been checked against the stated example. No measured campaign data is included.
The sensitivity rows vary only completion by 20% below and above the entered value. They are scenarios, not confidence limits or a forecast distribution. A row outside the model’s constraints is labelled rather than turned into a plausible-looking result. Save the chosen inputs with the decision so another reader can distinguish a changed assumption from a changed formula.
Evidence and limits
Google describes conversion lag as a reason recent CPA and ROAS can change. The worksheet’s scenario assumptions are supplied by the reader, not generated or endorsed by Google’s forecast system. See About conversion lag reporting, especially “How it works; Campaign types eligible for conversion lag reporting”.
No completion fraction is supplied by campaign evidence here. The calculator neither predicts actual late conversions nor substitutes for the platform’s own documented lag estimates and eligibility rules.
Background: UA metrics explained: CPI, ROAS, LTV and payback and Reading an MMP dashboard without fooling yourself. These existing articles provide context; the present calculation does not verify every archived claim.
Featured
Related posts
measurement
media buying
·1 min read
Using predicted LTV in bids: disclosure checklist for the UA team
measurement
media buying
·1 min read
Blended ROAS targets that hide channel failure in F2P portfolios
measurement
media buying
·2 min read
Web-shop LTV with VAT-inclusive prices versus store net proceeds (labelled synthetic)
measurement
media buying
·1 min read
View-through attribution windows on F2P rewarded and interstitial traffic
More from the Measurement desk
measurement
·2 min read
Airbridge adds Amazon Ads as an app measurement channel
measurement
·2 min read
When to freeze a cohort for payback review (and when not to)
measurement
·1 min read
Web-shop purchaser quality vs store IAP purchaser quality
measurement
·1 min read