Outcome. Each day, an admin gets a Slack alert only when that day's form submission volume drops well below the trailing 7-day average, so a broken form or a tracking outage gets caught the same day instead of at month end.
flowchart TD
A[Daily schedule: 09:00] --> B[Custom code: fetch submission counts, last 8 days]
B --> C[Compute average of prior 7 days]
C --> D{Yesterday below threshold and baseline met?}
D -->|yes| E[Post Slack alert]
D -->|no| F[Exit silently, no anomaly]

When to use it, when not to
- UseUse it on portals with steady daily form traffic, where a sudden drop is a meaningful signal, a form embed breaking, a page going down, or a tracking script failing.
- UseUse it as an early-warning layer on top of, not instead of, uptime monitoring for the site itself.
- SkipDo not use it on a portal with naturally spiky or low-volume form traffic, a handful of submissions a day. The 7-day average will be noisy and the alert will fire on ordinary variance.
- SkipDo not use it as the only signal for a marketing campaign's health. Pair it with the actual campaign performance report for that.
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





