Weekly summary and alerts

Two kinds of email. The weekly summary is one message every Monday morning with last week next to the week before. Alerts go out within 15 minutes of an order, a goal, or a traffic spike. Both are email only for now.

The weekly summary

Settings → Weekly summary. It is off until you switch it on. Enter the recipients one per line or separated by commas; every entry has to be an email address or the whole list is refused rather than a typo silently dropped. The list is the same one report delivery reads, so the two never disagree about who gets mail. Pick the timezone the Monday should be judged in; the default is UTC.

The email is due on Monday at or after 08:00 in that timezone. The worker checks every hour at five past, so it leaves at 08:05 local in a whole-hour zone and later in the hour elsewhere, once per Monday. A send is recorded against that Monday, so two ticks cannot send it twice, and a Monday that was missed is not sent on Tuesday: the email says "Monday morning" and should arrive then or not at all.

It covers the last complete Monday-to-Sunday week, subject to the plan's allowance and the data available when the email is generated:

• Visitors, orders, revenue and net revenue, next to the week before.
• Your top three sources, ranked by revenue when any source earned and by visitors otherwise (the email says which).
• Imported daily traffic and money excluded from USD reporting, with their scope explained.

Traffic uses the same tracked-plus-imported daily assembly as the dashboard and window API. Imported visitors are not deduplicated across days. Money totals are USD only, with no conversion. The summary includes an ad-platform monetary comparison when every included platform has known USD claims and compatible processor-confirmed payment currency. Otherwise it explains the omission rather than combining unknown or non-USD amounts. Re-sync old ad records that lack currency.

The renewal setting from the Stripe connection applies here too. The test button on the card sends last week's summary to the address you are signed in with.

Alerts

Order alerts can include the amount, time, source and today's count. Goal alerts can include the goal name, time, source and count. These details go through the email provider to the recipients you choose.

Settings → Alerts. Three kinds of rule, up to 20 per site:

• Every new order.
• A goal being reached, by the goal's name exactly as your site sends it. Recent names are suggested.
• A traffic spike: more than N people on the site, where N is a whole number from 1 to 100,000.

Recipients work like the summary's; leave the box empty and the rule goes to the address you are signed in with. Switching a rule off keeps it and its position in the stream; deleting it is separate.

When they fire

The worker judges every rule every 15 minutes. A new rule starts from the moment it was created, so it never emails the history behind it; the first email is the next matching event after the following tick. Each rule reads at most 200 events per tick, and the rest wait for the next one.

Order and goal alerts send one email per matching event, at most 25 emails per site per UTC day. The cursor advances past the cap, so a flood is capped rather than replayed the next day. A ledger keyed by rule and event means an event that was already emailed can never be sent twice, whatever the cursor says.

A spike is unique visitors above the threshold in both of the last two five-minute windows, ten minutes running, so one busy minute does not fire it. Once it fires, that rule stays quiet for six hours.

Questions? Email us at hello@datastated.com.