Reports and alerts
There are two kinds of email here and they have opposite jobs. The weekly report is the pleasant one you read with coffee. The alerts are the ones you hope never to see, and every threshold below exists to keep them rare enough to still mean something. Both are configured under Settings → Email Reports.
The weekly report
The weekly email covers the previous calendar week: your hits, unique hits if you use them, your top pages up to thirty of them, and kudos by page if kudos is switched on. It follows your Week starts on setting, so a week that begins on Monday for you is not summarised Sunday to Saturday.
By default it arrives at 9am in your timezone on the morning the new week begins. Ultra can move it to a different day, which is worth doing if Monday morning is not when you want to think about numbers.
Send Report Now on the same screen sends the current week immediately, which is the quickest way to see what the email actually looks like.
Alerts
Uptime emails you on confirmed downtime, on recovery, and about certificate problems and renewals. Test Down and Test Up live under Email Reports so you can check the whole path — including your own spam filter — without waiting for an outage.
Content monitoring emails you about broken links and mixed content once they are confirmed, and those emails can be paused while you are mid-maintenance.
Who gets what
The account owner always receives everything. That is not configurable, and it is the safest default we could pick.
Extra recipients are an Ultra feature, and each address chooses its own subscriptions from weekly reports, traffic spikes, and collection dropoff. They do not inherit the owner’s full set, so you can send the weekly summary to a client without also sending them every alert.
Traffic spikes
Traffic spikes are an Ultra feature, under Settings → Notifications → Traffic Spikes. Tinylytics emails you when live traffic crosses a visitor threshold — ten by default — inside a five-minute window, which is usually your cue that something of yours is being discussed somewhere. A twelve-hour cooldown follows each alert, so one busy afternoon produces one email rather than forty. If Insights is enabled, the email includes a one-off analysis of the spike itself, so you find out where it came from in the same message that told you about it.
Spike protection, on the same page, is the defensive half: it caps repeated hits from the same browser, path, and country within a twelve-hour window, so a single stuck tab cannot manufacture a spike.
Collection dropoff
Collection dropoff catches the failure nobody notices, because it looks like silence. It is an Ultra feature on the same screen, and it emails you when collection appears to have stopped rather than merely slowed.
The conditions are deliberately conservative: the site must be at least fourteen days old, it must have had a steady week averaging at least ten hits a day, and the last 24 hours must have dropped to 5% or less of that average. There is also an optional Verify embed script before alerting, which fetches your page and looks for the Tinylytics script — so a genuinely quiet Sunday does not get reported as a broken deploy. The check runs every six hours, with a seven-day cooldown after an alert.