Vireo Pro watches your traffic and sends an alert when it moves sharply. The settings are under Traffic alerts on the Reports screen, Vireo Analytics, Reports.
Spikes
When today’s pageviews reach a multiple of the average of the last seven days, Vireo sends “Traffic spike detected!” with the pageviews so far today against that average and a “View Dashboard” button.
The multiple is set under Spikes, “Once today reaches”, from 1.1 to 20 times the 7-day daily average. It starts at 2. Spike alerts are on by default.
Vireo waits until there are at least three days of history and ten pageviews today, and sends at most one spike alert every 24 hours. A spike is checked through the day.
Drops
A drop is judged each morning on the day just finished. Under Drops, “Once a day finishes” takes a percentage from 10 to 90, starting at 50: if yesterday’s pageviews came in that far or further below the 7-day daily average, Vireo sends “Traffic drop detected”.
Drop alerts are off until you tick “Alert me when traffic drops”. They need at least three days of history and an average of ten pageviews a day or more, so a quiet site isn’t alerted over a handful of visits. A day with no pageviews at all counts as a drop, which is usually the tracking script failing to load.
The same percentage is used for store alerts when a site is connected to WPShake, described below.
AI crawlers
Two more alerts cover AI crawlers. One watches for AI crawlers going quiet, covered in AI monitoring and crawler alerts. The other watches the weekly AI visibility scan for a check that stops passing, covered under access alerts.
AI answers
If you’ve turned on the mention alert in What AI assistants say about you, it uses the channels below too. Neither it nor the scan access alert is sent to WPShake.
Where alerts go
Alerts go to every channel you set up.
- Email: the addresses under “Email recipients”, one per line. Left blank, alerts go to the site’s admin email address.
- Slack: an incoming webhook from Slack. The alert is posted as a message to its channel. The address has to be a
hooks.slack.com/services/address. - Webhook: any https address of yours. It receives a JSON POST with an
eventfield, the site and the numbers behind the alert, and anX-Vireo-Eventheader. The event istraffic_spike,traffic_drop,ai_crawler_drop,ai_crawler_recovered,ai_scan_access_failed,ai_scan_access_recoveredorai_answers_mention_lost. - WPShake: see below.
Slack and webhook addresses are stored encrypted. Each field shows a masked version of the stored address. Leave it blank to keep the address, paste a new one to replace it, or tick “Remove the stored address”. An address that isn’t valid is refused, and the one already stored stays.
Webhook addresses must start with https:// and point to a public address. Vireo refuses addresses on your own network, such as localhost or a private IP range, and doesn’t follow redirects.
Test it
“Send test alert” sends a sample spike, marked as a test, to every channel you’ve saved. The Reports screen then lists each channel as delivered or failed with the reason, and when the last alert went out.
WPShake
WPShake is RebelCode’s site management dashboard. Connected, Vireo’s alerts arrive in WPShake next to the site’s other events, such as a plugin update shortly before a drop.
To connect, issue a token from the site’s Analytics tab in WPShake and paste it into the WPShake field. It starts with wpsv_. A value that isn’t a WPShake token is refused. Tick “Disconnect from WPShake” to remove the connection.
Once connected, WPShake receives:
- Traffic spikes and drops.
- AI crawler drop and recovery alerts.
- A daily summary of yesterday’s pageviews and visitors against the day before, with the top referring site.
- Order and revenue drops, when Vireo has store data and the site averaged at least three orders a day over the week before. They use the same percentage as traffic drops.
- A note when Vireo’s own recording checks find a critical problem, and another when they clear.
Only aggregate numbers are sent: pageviews, visitors, orders and revenue totals, and the host of a referrer. Nothing about individual visitors, customers or pages. Vireo checks every payload against a list of visitor-level fields and doesn’t send one that has any. Each event is signed with the token’s secret, which is stored encrypted, and goes over https.
Daily summaries and store drops go out whenever WPShake is connected, whatever the spike and drop settings say.