The playbook
ROAS Analysis: Template and Field Guide
This ROAS analysis template turns a broad task into a record another person can use. It captures revenue basis, ad spend, window, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| revenue basis | Record the revenue basis associated with this campaign or conversion record. Use a stable reference so later updates can be matched. |
| ad spend | Record the ad spend associated with this campaign or conversion record. Keep the value specific enough for another owner to interpret. |
| window | Record the window associated with this campaign or conversion record. Keep the value specific enough for another owner to interpret. |
| excluded costs | Record the excluded costs associated with this campaign or conversion record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with revenue basis. Use the same reference throughout the record so notes are not attached to the wrong item. Then choose the revenue basis and attribution window. This establishes the information required before the worksheet becomes a request for action.
Next, calculate revenue divided by advertising spend. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as treating revenue-based ROAS as profit, rather than a broad instruction to “improve performance.”
Finally, review margins returns and costs excluded from the ratio. Put pair ROAS with contribution economics and disclosed assumptions in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Treating revenue-based ROAS as profit |
| Action | Pair ROAS with contribution economics and disclosed assumptions |
| First check | Choose the revenue basis and attribution window |
| Follow-up check | Review margins returns and costs excluded from the ratio |
| Outcome to define | attributed revenue per advertising dollar |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If ad spend changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep attributed revenue per advertising dollar connected to the item so the team can later assess whether the action was useful.
Choose an observation period that reflects the buying process. Immediate clicks, later inquiries, and completed sales happen at different times. Keep the attribution window and any incomplete outcomes visible when comparing campaigns.
Skip the manual steps. Let AgentixFLO run this for every client.
Start now