Put ROAS in the context of the product’s costs
Compare revenue and spend with break-even ROAS and the testing decision estimate. Check Finance separately for profit after all recorded costs.
A good-looking ROAS can hide weak margins, incomplete data or a test that has barely started. Compare performance with break-even ROAS, costs and decision rules before deciding what deserves more spend.
Opening the workspace…
Compare revenue and spend with break-even ROAS and the testing decision estimate. Check Finance separately for profit after all recorded costs.
Review testing days, sales and data coverage. A low-volume product needs a different conversation from one that has consumed substantial spend.
Move between Portfolio, Meta and Google views. Open a campaign’s products and daily history instead of relying only on its period average.
Review the applied rules and record a reason. Link a task for new creatives, a cost negotiation or a closer product check.
Review the selected dates, spend, sales and available data.
Inspect break-even ROAS, the decision estimate and the relevant daily history.
Record the reason and assign the creative, cost or research work that follows.
Decision rules help interpret the recorded test data. Review the dates, testing depth, costs and data coverage before making the budget decision. The testing estimate and Finance profit use different calculations.
Portfolio and Meta use a product-first decision grid. Google uses a campaign-first grid, with product contributions and daily rows.
No. Review the evidence, mark rows reviewed and record your reason. The Testing decision grid does not directly execute advertising changes.
Review what the test actually shows before deciding where more budget belongs.
Get started