Email subscriptions
Let visitors subscribe to your status page and control which updates actually send email.
Turn on Let visitors subscribe to email updates in the status page editor's Settings tab. A Subscribe to updates button appears in the page header immediately.
Customers then hear about an incident when you declare it, rather than when their integration breaks.
Available on every advanced status page.
What sends an email#
| Event | What the email carries |
|---|---|
| An incident is created | Title, impact, affected components, first update |
| An incident gets an update | The new message and status |
| An incident is resolved | Duration and the final message |
| Maintenance is scheduled | Title, window, affected components |
| Maintenance starts | Notice that the window opened |
| Maintenance completes | Notice that the window closed |
Editing an already-scheduled maintenance window sends nothing. Emails fire on schedule, start, and complete, not on edits.
Control it per update#
Every incident declaration, update, and maintenance window has a Notify subscribers checkbox above the submit button, checked by default.
Leave it checked for real incidents. Uncheck it for a typo fix, a test, or a cosmetic edit where an email is pure noise. Subscribers who get paged for a spelling correction unsubscribe, and then they are not there for the outage that matters.
The checkbox is hidden when subscriptions are off, and on maintenance it appears only when you create the window.
How people subscribe#
A visitor clicks Subscribe to updates, enters an email, and receives a confirmation link. The link expires after 48 hours. They have to click it.
There is no admin override and no way to add an address on someone's behalf. That keeps your sender reputation intact and the list compliant with CAN-SPAM, CASL, and GDPR consent rules.
The same response comes back whether the address is new, already subscribed, or inside the cooldown window, so a visitor cannot use the form to discover who else is subscribed.
Manage the list#
The Subscribers tab shows counts for Active, Pending, and Unsubscribed, and the full list with active subscribers first.
Remove deletes a subscriber, who then has to resubscribe through the public page. Export CSV downloads your-slug-subscribers.csv with email,status,created_at,verified_at for active and pending subscribers, which is what you want for a backup or a migration.
The list paginates. Use Load more for older entries.
What happens when it breaks#
| Situation | What the visitor sees | What to do |
|---|---|---|
| The confirmation link expired | Nothing arrives after they click | They resubscribe from the public page |
| They subscribed twice quickly | The second request is accepted silently, no second email | The first link is the one that works |
| They refreshed the form repeatedly | "Too many attempts, try again in a minute" | Rate limit is 5 requests per minute per IP |
| Subscriptions were turned off | The Subscribe button disappears | Existing subscribers stay on the list but receive nothing until it is back on |
| Limit | Value |
|---|---|
| Confirmation link expiry | 48 hours |
| Subscribe rate limit | 5 requests per minute per IP |
| Resend cooldown | 5 minutes |
Make unsubscribing easy#
Every email carries a one-click unsubscribe link and the standard List-Unsubscribe headers, so Gmail, Apple Mail, and Outlook show their own unsubscribe button next to the sender. One click is enough and there is no confirmation page.
The subscriber lands on a confirmation page on status.drumbeats.io even if they reached your page through a custom domain. Confirmation and unsubscribe links always use the canonical host.
Next#
Status pages for the page these subscriptions belong to. Custom domains for serving it from your own hostname. Incidents for the model behind the updates.