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.