Campaign Analytics Agent
Reports ROAS and acquisition cost by campaign.
- Industry
- Hotel
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Investigator
- Approver
- Revenue Manager
- Code
- MKT-09
It reports return on ad spend and cost per direct booking for each campaign and hotel, and explains why they moved. It separates real demand changes from tracking gaps, rate-parity losses to online travel agencies and cancellations, and posts the report to the marketing dashboard. **The problem it solves:** Why ROAS or cost per direct booking moved: the campaigns and hotels, the figures for both periods, when the change began, and what changed in demand, rate parity, spend, targeting, creative or tracking.
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 central reservation system: net direct bookings and revenue by source and hotel for both periods, with campaign spend from the ad and metasearch platforms..
- 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 Revenue Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the marketing dashboard: it posts the campaign report for the period. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The measurement plan: attribution model, the definition of a direct booking (net of cancellations), target ROAS and cost per booking by hotel, and the known tracking gaps between the booking engine and analytics.
Reads from
the central reservation system: net direct bookings and revenue by source and hotel for both periods, with campaign spend from the ad and metasearch platforms.
Acts in
the marketing dashboard: it posts the campaign report for the period.
Hands back
An object with campaigns (a list, each with name, hotel, spend_usd, direct_revenue_usd, roas, cost_per_booking, change_percent), causes (a list, each with cause, evidence and likelihood), tracking_gap_percent and actions.
Asks a person when
A tracking gap would change reported revenue, or the report recommends cutting a hotel's budget.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Attribution model | last non-direct click | How bookings are credited. |
| Target ROAS | 8 | Direct room revenue per USD of spend. |
| Target cost per booking (USD) | 45 | Spend per net direct booking. |
| Move worth explaining (%) | 15 | A change this large or larger is explained. |
| Tracking gap that flags a data problem (%) | 10 | When analytics bookings differ from reservation-system bookings by more than this, tracking is checked first. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Credit bookings by last non-direct click, net of cancellations.
- Explain any campaign whose ROAS or cost per booking moved 15 percent or more against target 8 or 45 USD.
- When analytics and the reservation system differ by more than 10 percent, check tracking before anything else.
- Weigh demand, rate parity against online agencies, spend, targeting, creative and tracking as causes, with evidence for each.
- Never report a cause without the figures behind it.
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.