Campaign Analytics Agent
Reports ROAS and acquisition cost by campaign.
- Industry
- Retail
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- E-commerce Director
- Code
- MKT-09
It reports return on ad spend, cost per new customer and promotion lift by campaign and channel for a period, reconciles platform-reported revenue against orders in the order management system net of returns, and explains what drove the change from the comparison period. It publishes the report to the marketing dashboard and flags campaigns that miss target or whose reported revenue the orders do not support. **The problem it solves:** Why return on ad spend, new-customer cost or promotion lift changed against the comparison period, and which campaigns' revenue the orders do not support.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the order management system: orders, revenue and returns by attributed campaign for both periods, with spend from the ad accounts..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the marketing dashboard: it publishes the campaign report for the period. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The marketing measurement standard: the attribution model, ROAS and new-customer cost targets, how promotion lift is measured against a baseline, how returns are netted off, and the seasonal comparison rules (like-for-like weeks).
Reads from
the order management system: orders, revenue and returns by attributed campaign for both periods, with spend from the ad accounts.
Acts in
the marketing dashboard: it publishes the campaign report for the period.
Hands back
An object with totals (spend, revenue_net, roas, new_customers, cost_per_new_customer), campaigns (a list, each with campaign, spend, revenue_net, roas, new_customers, cost_per_new_customer and flag or null), drivers (a ranked list, each with cause, evidence and confidence) and revenue_gaps (a list).
Asks a person when
The report recommends cutting a campaign that carries a live promotion, or the revenue gap points to a tracking failure that affects reported results.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Attribution model | position-based | How order revenue is credited to campaigns. |
| Target ROAS | 6 | Campaigns below this are flagged. |
| Target cost per new customer (USD) | 35 | Campaigns acquiring new shoppers above this cost are flagged. |
| Explain changes above (%) | 15 | A metric moving this much from the comparison period is explained. |
| Revenue gap that is flagged (%) | 10 | Platform-reported revenue this far above order-system revenue for a campaign is flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Credit revenue by the position-based model, from orders in the order management system net of returns.
- Compare like-for-like trading weeks: a week with a promotion or holiday is compared with the matching week last year, not the week before.
- Flag campaigns below 6 ROAS or above 35 USD per new customer.
- Explain any metric that moved more than 15 percent by weighing competing causes: spend mix, promotion depth, stock availability, price changes, seasonality and tracking changes.
- Flag a campaign whose platform-reported revenue is more than 10 percent above the order system's figure.
See the Campaign Analytics Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.