RROAS BREAK

Planning and measurement

Conversion Delay and Data Maturity

Spend can accrue before all attributed conversion value is reported. Use the account's own delay curve and a frozen reporting contract before treating recent ROAS as budget evidence.

60-second answer

An immature window supports sensitivity analysis, not a deterministic budget move.

Recent attributed ROAS is mature enough only when the decision window has accumulated the share of conversion value required by the business's predeclared rule. Build that rule from the account's own days-to-conversion history, not a generic lag assumption.

Before comparing periods, freeze the conversion action, attribution window, report date basis, timezone, currency, and value definition. A changed contract can look like conversion delay even when customer behavior did not change.

Reported ROAS at T+n = value reported for the frozen cohort by T+n / cohort spend

Delay sensitivity value = reported value / historical reported share at the same age

The sensitivity calculation is a range-planning aid, not booked revenue and not a forecast guarantee. When the most recent window is below the chosen maturity threshold, schedule a re-read and avoid a deterministic scale, pause, or target change based on that window alone.

Freeze the contract

Hold six reporting choices constant before measuring delay.

  1. Conversion action: Use the same purchase action, inclusion status, and value source.
  2. Attribution window: Record the selected click, engaged-view, or other applicable window rather than assuming a default.
  3. Date basis: State whether the cohort is organized by ad interaction date, conversion date, or another report date.
  4. Timezone and currency: Keep the account day boundary and any conversion rules fixed.
  5. Value boundary: State whether purchase value includes tax, shipping, discounts, cancellations, or later adjustments.
  6. Extraction age: Label every read T+1, T+3, T+7, or another explicit age from the same cohort cutoff.

Google Ads documents that conversion reporting can be delayed and provides account reporting that helps investigate the lag. Use the account's evidence because action mix, customer journey, import method, and reporting configuration can change how quickly value appears.

Transparent example

T+1 looks like 2.00x; T+7 matures at 2.70x.

A merchant's own comparable historical cohorts usually report 70% of eventual attributed conversion value by T+1, 90% by T+3, and are treated as mature at T+7. This curve is fictional and belongs only to this merchant's example. It is not a Google benchmark, a universal threshold, or a substitute for the current account's days-to-conversion distribution.

Cohort ageMerchant's historical reported sharePermitted use
T+1Usually 70%Sensitivity only
T+3Usually 90%Provisional read under the merchant's rule
T+7Treated as matureBudget comparison, subject to value corrections

The current cohort has already accrued $10,000 of spend. At T+1, Google Ads reports $20,000 of attributed value, so the observed ratio is 2.00x. Dividing $20,000 by the merchant's 70% historical share produces a sensitivity estimate of $28,571, or 2.86x. The estimated remaining value is $8,571.

At T+7, the cohort actually reaches $27,000 of attributed value and 2.70x ROAS. The result is below the T+1 sensitivity estimate, which is exactly why the estimate must not be booked or treated as certain. The mature observation replaces the sensitivity case.

LedgerT+1T+7
Cost accrued$10,000$10,000
Reported attributed value$20,000$27,000
Estimated remaining value$8,571 sensitivity$0 reporting-delay estimate
Observed ROAS2.00x2.70x
Refund maturityTracked separatelyStill tracked separately

Economic gate

Mature does not mean profitable enough.

Reporting maturity only says the attributed value is stable enough for the declared comparison. It does not set the business target. For a $100 net order, subtract $40 product cost, $8 fulfillment, $4 other variable cost, 3% payment and platform fees, and a 5% returns allowance. Contribution before advertising is $40.

Economic checkCalculationResult
Contribution before ads$100 - $40 - $8 - $4 - $3 - $5$40.00
Break-even ROAS$100 / $402.50x
Retained profit10% x $100$10.00
Target CPA$40 - $10$30.00
Target ROAS$100 / $303.33x
Mature T+7 ROAS$27,000 / $10,0002.70x

The mature 2.70x is above the 2.50x zero-profit floor but below the 3.33x retained-profit target. At 2.70x, modeled ad cost per $100 order is $37.04, leaving about $2.96 after advertising rather than the planned $10. Maturity makes that shortfall more decision-ready; it does not erase it.

Open the mature 2.70x profit-threshold scenario

Budget decision gate

Separate four states before acting.

StateEvidenceAllowed conclusion
Immature and below targetWindow has not reached the chosen historical maturity shareShow observed and sensitivity cases; wait for the scheduled read
Mature and below targetFrozen cohort reaches its maturity rule but misses 3.33xEvaluate a budget, bid, mix, or economics change
Mature and above targetFrozen cohort reaches maturity and clears 3.33xAssess volume and marginal profit before scaling
Reporting mature, value unresolvedConversions settled but refunds or cancellations remain openKeep a separate correction reserve and later value review

Define the maturity rule and action bands before seeing the newest result. Compare cohorts with similar conversion actions, windows, weekdays, seasonality, and value imports. A curve built during a different tracking setup is not a valid denominator for the current sensitivity estimate.

Decision boundary: This page determines when recent attributed ROAS is stable enough to compare. The Google target guide calculates the economic target. A separate refund-adjustment workflow should later replace attributed gross value with mature net value when refunds and cancellations settle.

Official sources and judgment

Google describes reporting delay; the merchant chooses the maturity rule.

Google Ads documents how to investigate conversion reporting delays and describes target ROAS bidding. ROAS Break supplies the fictional 70%/90%/T+7 curve, sensitivity calculation, contribution costs, and decision gate. None of those example thresholds is a Google recommendation.

Recheck the current product interface and documentation when conversion actions, imports, attribution settings, or bidding strategies change. Preserve dated exports so a later report can be compared with the exact earlier read rather than memory.