The five protection modules
| Module | What it checks | Platforms |
|---|---|---|
| Setup Protection | Live setup vs the approved setup: objective, optimization goal and event, bid strategy, buying type, status, countries, age, gender, targeting expansion, placements, pixel, app, page, UTMs, URL domains, CTA, landing URL, deep link, lead form, budget, naming convention | Meta, Snapchat, TikTok, X, DV360 |
| Budget & Pacing Protection | Budget type, daily vs lifetime math, flight length, ad set budget split against the plan, spend pace vs elapsed flight | Meta, Snapchat, TikTok, X, DV360 |
| Performance Anomaly | Threshold, baseline and statistical outlier rules on live insights | Meta, Snapchat, TikTok, X, DV360 |
| Creative Placement Fit | Each live asset's aspect ratio against the placements it actually serves (9:16 Stories and Reels, 1:1 or 4:5 feed, 16:9 in-stream) | Meta |
| Automation guard | TikTok: Smart+, automatic placement, ACO, search and catalog automation switched on. Meta: Advantage+ settings the client preset says must stay off | TikTok, Meta |
How performance anomalies are detected
Each performance rule reads real platform insights for an account, campaign, ad set or ad. It compares the last 24 or 72 hours with a 7, 14 or 28-day baseline, using a fixed threshold, a percent change, or an outlier test against the auto-baseline. Ratios such as CPA and CTR are computed from summed parts, not averaged per day. A rule needs a minimum sample before it can fire: 5 conversions for CPA, 3 purchases for ROAS, 1,000 impressions for CTR or CPM, 20 clicks for CPC. You can also require a condition to stay true for 15 minutes up to 24 hours before alerting, which removes most one-hour noise.
Metrics: spend, impressions, reach, clicks, purchases, leads, conversions, add to cart, installs, CTR, link CTR, CPC, link CPC, CPM, frequency, CPL, CPA, CPI, ROAS and revenue. The picker only offers what each platform returns: X has no ROAS or revenue, link-click metrics are Meta only, and DV360 has no reach or per-event conversions.
Starting templates
| Template | Default rule |
|---|---|
| Cost efficiency | CPA up more than 25% in the last 24h vs the 14-day baseline, still true after 2 hours |
| Results performance | Conversions down more than 20% vs the 14-day baseline, still true after 2 hours |
| Spend movement | Spend up more than 40% vs the 14-day baseline, still true after 1 hour |
| Frequency level | Frequency above 4 over a rolling 7 days |
From alert to fix
Define "correct"
Save a client preset, or upload the approved media plan (XLSX, XLS or CSV). Each line item becomes a campaign monitor.
Get the alert
Alerts are deduplicated and show each affected entity with expected vs actual values. Email follows severity, quiet hours and digest settings; critical alerts always send.
Work it
Acknowledge, re-check, snooze, reassign, accept an exception, mark fixed or resolve. Every step is kept in the alert history.
Escalate if ignored
Each alert has an SLA. A reminder goes out at half the SLA, then it escalates from owner to specialist to manager. Weekend escalation can be paused.
Let it act, if you allow it
Rules can notify, pause, raise or lower budget, or open a ticket. Live writes run on Meta, X and DV360, only for critical alerts when automatic actions are on, and each can be undone.
Frequently asked questions
Is the Anomaly Engine available on every plan?
Not yet. It is in early access and switched on per workspace by the Whathead team. Contact us to request access for your workspace.
Which ad platforms does it monitor?
Meta, Snapchat, TikTok, X and DV360. Google Ads, LinkedIn and Reddit are not monitored yet.
Can it pause ads on its own?
Only if you turn on automatic actions, only for critical alerts, and only on Meta, X and DV360. Every automated change records what it did and can be undone. On Snapchat and TikTok it alerts only.
Where do alerts arrive?
In the Alert center and by email. Slack, Teams and webhook delivery are not available.
How is this different from Meta automated rules?
Meta rules act on one account's metrics. The Anomaly Engine also checks setup against an approved plan, covers five platforms in one place, and adds ownership, SLAs and escalation around each alert.
How does it avoid false alarms?
Minimum-data gates, sustain delays from 15 minutes to 24 hours, sensitivity levels, ratio-of-sums maths and fingerprinted deduplication, so one problem produces one alert with an occurrence count.
Run it from one workspace
Every plan starts with a 14-day free trial. Only successful live work is metered.