Notifications: what reaches you, and how
TagEasy watches your tracking around the clock and tells you when something changes. The preference center at Settings → Notifications is where each person decides, per organisation, which of those messages reach them and through which channel. Every sender in the product honours it.
Categories
- Anomaly alerts — a tracked event drops, spikes or goes silent; a funnel stops converting; a synthetic journey fails; and the all-clear when each recovers. Email, Slack and PagerDuty.
- Weekly health summary — Monday roundup of OK / WARN / BROKEN events per website. Email.
- Weekly insights — AI-written analytics insights for a website, sent to the website owner on their chosen day. Email.
- Monthly recap — what TagEasy did for the organisation over the last 30 days. Email and Slack.
- Publish requests — a request needs your approval, or one you raised was decided. Email and Slack.
- Usage and quota warnings — the organisation crossed 75%, 90% or 100% of its monthly event quota. Email, admins and owners.
- Onboarding tips — reminders to finish a website's setup and the one-time note when you have room for more sites. Email.
- Product updates — occasional notes about features that affect your setup. Email.
- Public audit updates — listed for completeness; subscribers to the public checker manage those from the link in each audit email.
Who decides what
Email is personal. Each member switches it per category, and alert-type categories can be delivered immediately or as a daily digest: one email at 08:00 UTC with everything held since the last one. A member who has not chosen gets the organisation default, and failing that the catalogue default (everything on).
Slack and PagerDuty are organisation channels. The webhook URL and the routing key are set once for the organisation, so which categories post there is decided by an admin or owner in the Organisation defaults card, not per person. Agency override webhooks linked to a client organisation keep receiving everything, since they belong to the agency.
Recipients are still chosen by role: anomaly alerts, summaries, recaps and quota warnings go to admins and owners; a weekly insight goes to the website's owner; a publish request goes to the reviewers the policy names. Preferences narrow that set — they never add someone who would not otherwise be told.
A different address
Set a notification address on the same page to route these emails somewhere other than your login email — a shared alerts inbox, for instance. Sign-in, invite and billing emails always go to the login address. Two members routing to the same inbox get one copy.
Unsubscribe links
Every email in the categories above carries a footer with Manage notifications and a one-click Unsubscribe for that category and organisation, plus the standard List-Unsubscribe headers so your mail client can offer the same action. Unsubscribing turns off that one category's email and nothing else; you can turn it back on, or switch to a digest, from the preference center.
Always sent
Transactional email has no switch: password resets and magic links, email-change confirmations, two-factor changes, organisation invites, billing notices, scheduled GA4 report deliveries (they go to the recipients listed on the schedule), the client approval link under a client-approval publish policy, public-audit subscription alerts, and replies to messages you sent through the contact or support forms.
Why did (or didn't) I get this?
The Recent notifications list on the same page shows the last 100 deliveries to you, and the organisation's Slack and PagerDuty posts, each marked sent, skipped or failed with the reason: held for your daily digest, turned off by you or by the organisation default, no webhook configured, provider error. Preference changes are also recorded in the activity log.