Zenovay gives you two ways to get alerted when something changes: automation rules (for traffic, error-rate, and conversion changes) and uptime alerts (for when a site goes down). This guide covers both.
Both features are available on Pro and above. Free workspaces can monitor uptime but can't create automation rules.
Automation Rules
Automation rules watch your analytics and fire an action when a condition is met. They live in each website's settings, not in a global alerts area.
Where to find them
- Open your website's dashboard
- Go to Settings → Automation
- Click Create rule
Pro allows up to 10 rules per website, and Scale allows up to 50. Enterprise has no rule limit.
Trigger types
| Trigger | Fires when |
|---|---|
| Traffic spike | Visits jump well above the recent baseline |
| Traffic drop | Visits fall by a set percentage versus the baseline |
| Error rate threshold | The error rate crosses the limit you set |
| Conversion rate below | A goal's conversion rate drops below a target |
| Bounce rate above | The bounce rate rises above a threshold |
For traffic rules you choose the baseline period (1, 7, 14, or 30 days) the current value is compared against.
Actions
When a rule triggers, it can run one of these actions:
| Action | What it does |
|---|---|
| Sends an alert to one or more email addresses | |
| Slack | Posts to a Slack channel via an incoming webhook URL |
| Webhook | POSTs a JSON payload to an HTTPS endpoint you control |
| Push notification | Sends a browser push notification to subscribed devices |
Cooldown
Each rule has a cooldown (in minutes) so a single ongoing condition doesn't fire repeatedly. The default is 60 minutes. Raise it for noisy signals; lower it for ones you want to hear about quickly.
Uptime Alerts
Uptime monitoring runs server-side checks against your site and alerts you when it goes down. You don't need the tracking script for this.
Configure uptime alerts
- Open your website's dashboard
- Open the Uptime tab
- Open the monitor configuration
From there you can set:
- Check interval — how often Zenovay checks the site. The tightest interval depends on your plan: 10 minutes on Free, 5 minutes on Pro, and 1 minute on Scale and Enterprise.
- Alert threshold — how many consecutive failed checks must occur before an alert is sent. The default is 3, which avoids alerting on a single transient blip.
- Expected status code and an optional keyword the response should contain.
- SSL monitoring (paid plans) to catch certificate problems.
Uptime alerts can be delivered by email, webhook, Slack, or Discord.
Webhook Payloads
When an automation rule or uptime alert uses a webhook action, Zenovay sends a POST request with a JSON body to the HTTPS URL you provide. Use it to forward alerts into your own tooling.
The webhook URL must use HTTPS.
Best Practices
Alert hygiene
- Avoid alert fatigue. Too many alerts get ignored. Start with a few high-signal rules.
- Set meaningful thresholds. Tune them against your actual baseline so they don't fire on normal variance.
- Use the cooldown. It's the simplest way to stop a single condition from spamming you.
- Review regularly. Adjust thresholds as your traffic patterns change.
Threshold guidelines
These are starting points, not rules. Watch your own data for a week or two and adjust.
| Signal | Reasonable starting point |
|---|---|
| Error rate | 2x your normal baseline |
| Traffic drop | 30% below baseline |
| Uptime | Alert after 3 consecutive failed checks |
Using the API for Deployment Checks
You can also pull analytics into your CI/CD pipeline to spot regressions after a deploy. This uses the external API, which is available on Pro and above.
# GitHub Actions example - check analytics after deploy
- name: Verify Post-Deploy Analytics
run: |
curl -X GET "https://api.zenovay.com/api/external/v1/analytics/${{ vars.ZENOVAY_WEBSITE_ID }}" \
-H "X-API-Key: ${{ secrets.ZENOVAY_API_KEY }}"
Generate an API key in your workspace under Settings → Security → API Keys. For automated alerts that don't require polling, set up an automation rule (above) with a webhook action so Zenovay notifies your team when a threshold is crossed.
Troubleshooting
Not receiving alerts
Check:
- The rule or monitor is enabled.
- For email actions, the recipient address is correct and the message isn't in spam.
- For Slack, the incoming webhook URL is valid and the channel still exists.
- For webhooks, your endpoint is reachable over HTTPS and returns a 2xx response.
Too many alerts
Adjust:
- Raise the threshold so it fires less often.
- Increase the rule's cooldown.
- Use a longer baseline period for traffic rules to smooth out normal variance.
False positives
Review:
- Whether the threshold matches your real traffic patterns.
- The baseline period a traffic rule compares against.
- Whether a recent change (a campaign, a deploy, a known maintenance window) explains the signal.