The playbook
ROAS Analysis: Review Process
A useful ROAS analysis review ends with a supported decision for each item examined. Define the evidence required before opening the report: revenue basis, ad spend, window, excluded costs. These fields give reviewers a shared basis for agreeing what is working, what needs attention, and who should act.
Put the task in context
ROAS is attributed revenue divided by ad spend. An illustrative $8,000 in attributed revenue on $2,000 in spend equals 4× ROAS. It does not establish profit: margin, returns, fulfillment, management, and other costs still affect the business result.
Set the review boundary
Choose the records or journeys that matter to the current question. Include a normal case, a recently changed case, and an exception where available. This is a diagnostic sample, not a claim that every item has been checked. Record how the sample was selected and what would justify expanding it.
Use explicit review criteria
| Criterion | Review question |
|---|---|
| Choose the revenue basis and attribution window | Is the supporting revenue basis current and traceable? |
| Calculate revenue divided by advertising spend | Does ad spend support the decision being made? |
| Review margins returns and costs excluded from the ratio | Can the next owner verify excluded costs? |
Inspect the evidence before assigning a result
For each item, compare the intended behavior with the observed behavior. Pay particular attention to treating revenue-based ROAS as profit. If it appears, record where it occurs and which assumption it contradicts. Distinguish a verified defect from an unanswered question and from a preference about how the work should look.
Where the evidence supports the known correction, pair ROAS with contribution economics and disclosed assumptions. Give that action to an accountable owner with a description of the expected result. If you cannot yet identify the cause, assign a diagnostic action rather than prescribing a speculative repair.
Record a decision that can be acted on
| Decision | When to use it |
|---|---|
| Keep | The current state serves the intended task and the evidence is adequate. |
| Revise | A specific gap is confirmed and the proposed action addresses it. |
| Investigate | Important information is missing or conflicting. |
| Retire or combine | The item has no distinct useful purpose in the current scope. |
Verify corrections and expand selectively
Recheck the affected campaign or conversion record after the owner completes the action. Then inspect other items sharing the relevant cause. A shared template, process rule, or data source may justify expanding the review. Similar wording or appearance alone is a weaker reason.
Turn the review into a decision summary
Summarize the affected scope, confirmed findings, actions, and open questions. Connect the findings to attributed revenue per advertising dollar using the same definition as the baseline. A good summary lets the responsible person decide what happens next without reading every working note.
Treat audience, offer, creative, destination, and tracking as connected parts of the campaign. If several change together, the result does not identify which change mattered. Record the differences before using the result to set a new budget.
Skip the manual steps. Let AgentixFLO run this for every client.
Start now