Overview, digest and uptime

The Overview shows every site in your account on one page. Sites that need you come first, each with the one thing to do next.

What counts as needing attention

Worst first:

• Site down. Two uptime checks in a row failed.
• Tag stopped. No visits in 24 hours, on a site where a usual day brings 10 or more.
• Conversions or visitors fell. The last 7 days came in under 70% of a usual week, and well outside how much the site usually swings. A usual week is the average of the 4 weeks before. Small sites are left out: under 70 visitors or 5 conversions a week, a drop says little.
• Ads spent with no results. Ads spent in the last 7 days, and the site's goal got nothing. With no goal yet, it asks you to add one.
• SSL or domain ending soon. The certificate ends within 14 days, or the domain within 30.
• A sync stopped. A connected tool, such as Shopify, stopped syncing.
• Tracking health is low. The site's tracking health score is under 60 of 100 (when shipped).
• A report waits for your OK. A report set to Check first is ready for you.

Visits refresh every hour and goals once a day, so the page loads fast however many sites you have. Pick a client name above the list to see only that client's sites.

The digest

Under Digest and chat alerts on the Overview, choose Every day or Every Monday, the hour and your time zone. The digest lists each site that needs you with its action, then how many look fine. It goes to your email, and to Slack or Teams when you add them. Studio and Agency include it.

Slack

1. In Slack, add the Incoming Webhooks app to the channel you want.
2. Copy its webhook address. It starts with https://hooks.slack.com/.
3. Paste it on the Overview and press Save, then Send a test.

Microsoft Teams

1. In Teams, open Workflows and pick Post to a channel when a webhook request is received.
2. Choose the team and channel, then copy the address it gives you.
3. Paste it on the Overview and press Save, then Send a test.

The address lets anyone who has it post to that channel, so Sporetag stores it encrypted and shows only its last four characters.

Uptime, SSL and domain checks

On paid plans, Sporetag loads each site's home page every 15 minutes.

• Each check tries three times before it counts as failed, and a site is called down only after two failed checks in a row. One slow minute never wakes anyone up.
• A site is up when it answers. Server errors (500 and up), "page not found" on the home page and no answer in 15 seconds count as down.
• The SSL date comes from public certificate logs, looked up once a day. Certificates usually renew a month early, so one that ends within 14 days usually means renewal is failing.
• The domain date comes from the registry, looked up once a day. Some registries do not publish it; then the page says so.

You get an email when a site goes down and when it is back, and when a certificate or domain is about to end. Each kind goes at most once a day per site. Tick Also post site down, SSL and domain alerts there to send them to Slack or Teams too. Each site's Alerts tab shows its uptime for the last 30 days. Add the Uptime block to a report to show it to your client.

The report summary

Every client report opens with a short summary: What happened, Why, What we did and What's next, written from that period's numbers.

• What we did lists changes made in Sporetag during the period, such as goals added and email flows set up.
• What's next comes from the site's Autopilot plan.
• With the Assistant on, AI writes it and uses one AI action per report period. Sporetag then checks every number in it against your data. If one does not match, the plain version written from the numbers goes instead.

In the report's Summary card, pick Automatic to send it with each report, Check first to get an email when it is ready and send the report when you approve, or Off. You can change the words in either mode.