Settings
Detection rule configuration and system status.
Aurora PostgreSQL
Connected
Claude Sonnet
claude-sonnet-4-6
7 Detection Rules
Active
Detection Rules
| Rule | Trigger | Severity | Diagnosis & Action |
|---|---|---|---|
| Win Rate | < 15% | CRITICAL | Bids too low or targeting too narrow → Increase floor CPM or broaden audience segments |
| CPM Spike | > 40% vs 7-day avg | WARNING | Increased auction competition or audience overlap → Review bid strategy, check competitors, consider PMPs |
| Viewability | < 70% | WARNING | Low quality inventory, poor placement → Tighten whitelist, add viewability floor in DSP |
| Frequency Breach | > 8 / user / day | MONITOR | Audience too narrow, cap misconfigured → Expand audience or reduce frequency cap |
| Budget Pacing | under > 20% / over > 15% | MONITOR | Bid too low (under) or targeting too broad (over) → Adjust bid floor or tighten targeting |
| Video Completion | VCR < 60% | WARNING | Creative fatigue, wrong placement, poor match → Rotate creative, review placements, check skip settings |
| Brand Safety | < 90% | CRITICAL | Ads near unsafe content, whitelist not enforced → Audit placements, tighten adjacency, add exclusions |
Escalation Logic
When the same alert fires 3 times within 7 days for a campaign, PRISM automatically escalates its severity to
CRITICAL
. This surfaces persistent, unresolved issues that single-point checks would miss.Danger Zone
Permanently delete all campaigns, metrics, alerts, and benchmarks.