Monitors: incidents for CPA spikes, ROAS drops, delivery and tracking
Monitors watch for problems and raise incidents — without proposing changes. They are the alarm system for your accounts.
What it does
Available monitor types: CPA spike, ROAS drop, not delivering, spend pacing, tracking gap, budget exhausted, Meta pixel health and spend without GA4 key events. Each rule applies to a client or an account and runs hourly or daily.
An incident is deduplicated per rule, campaign and day, so one problem does not produce a flood. Incidents appear as notifications in the app and can be sent to webhooks. Each monitor also has a ready prompt you can paste into Claude or ChatGPT to investigate with MCP tools.
Why it helps
- Know about problems before the client does.
- No alert fatigue thanks to deduplication and severities.
- Easy hand-off to AI for investigation.
How to set it up
- Open Agents → Monitors and create a monitor for a client.
- Choose the type, thresholds and schedule.
- Optionally add a webhook.
- Review incidents and use the prompt to investigate.
Good to know
- Monitors only notify; changes are made by people or agents through proposals.
- Severity (info, warning, critical) depends on the monitor type.



Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace