Six detectors.
One alert queue.
workers/cron/src/insights-detectors.ts runs delivery_quality, coverage_gaps, duplicate_events, identity_gaps, quota_trajectory, and latency_outliers. Schema drift and alert routing turn those findings into operational work.
Built from the product surface, not brochure claims.
What the team actually gets.
Delivery quality
Flags platform delivery rates below target with attempted, delivered, and failed counts.
Coverage gaps
Compares actual event names against recommended canonical events for connected platforms.
Quota trajectory
Projects month-end event volume before a merchant hits the plan ceiling.
Latency outliers
Catches p95 delivery latency jumps by platform and window.
How it compares to ordinary tracking work.
- delivery_quality
- attempted/delivered rate
- coverage_gaps
- taxonomy-aware
- duplicate_events
- event_id window
- identity_gaps
- match-key baseline
- quota_trajectory
- projected EOM
- delivery_quality
- manual dashboard
- coverage_gaps
- manual QA
- duplicate_events
- tag preview
- identity_gaps
- spot check
- quota_trajectory
- invoice surprise
- delivery_quality
- platform UI
- coverage_gaps
- limited
- duplicate_events
- reporting symptom
- identity_gaps
- EMQ view
- quota_trajectory
- plan page
Real merchant-shaped cases and measurable signals.
The references an operator can inspect.
Where this matters in production.
A flash sale doubled event volume by day 19.
quota_trajectory projected the overage early enough to upgrade before delivery was constrained.
Checkout moved domains and stopped preserving fbc.
identity_gaps alerted with fbc_presence_rate evidence and affected events.
TikTok p95 delivery latency climbed after a regional DNS change.
latency_outliers isolated the platform and time window for engineering.