Per-Component Subscriber Notifications

Per-component subscriber notifications let visitors stay subscribed to your status page without receiving every single update for every service.

Instead of following the whole page, a subscriber can keep the default All components scope or narrow delivery to only the component or service entries they care about.

How subscribers choose their scope

When public subscriptions are enabled on a status page:

1. The visitor clicks Subscribe on the public status page
2. They enter their email address
3. They open the Notify about picker
4. They keep All components selected or choose a smaller set
5. They confirm the subscription from their email

If they leave the picker on All components, nothing changes from the classic behavior: they receive page-wide subscriber updates.

What appears in the picker

The picker follows the public status page structure as closely as possible:

• Grouped services are shown under the same component groups visitors already see on the page
• Manual/simple components appear as component rows
• Monitor-backed pages may show individual service entries by monitor name, which gives subscribers narrower delivery control on pages where one component contains multiple monitored services

This means the subscriber experience stays aligned with what users already see in the Components section of the page.

Delivery rules

If no filter is saved

The subscription is treated as page-wide.

These subscribers receive the same updates as before:

• Component-linked incidents
• Status-page-wide incidents
• Incident updates and resolutions
• Scheduled and completed maintenance emails

If a subscriber picks specific components or service entries

Delivery becomes selective for incident-driven updates:

• A component-linked incident goes only to subscribers who selected that affected service entry, plus subscribers who stayed on All components
• Incident updates and resolution emails follow the same scope as the original affected component
• Page-wide incidents with no affected component still go to all subscribers on the page

Maintenance emails remain page-wide

Scheduled maintenance and maintenance completion emails are still broadcast to all confirmed subscribers of the status page.

Component selection on the maintenance record affects what visitors see on the page, but it does not currently narrow maintenance email delivery.

Feeds are not filtered

RSS and Atom feed subscriptions remain page-wide and are not affected by email component selections.

What page owners should know

• This is a delivery filter, not a separate subscriber list per component
• Your Subscribers tab still manages subscribers at the status-page level
• To make targeted delivery useful, link incidents to the right affected components when you publish them
• If you intentionally want everyone notified, publish a page-wide incident or use maintenance announcements

When to use it

Per-component subscriber notifications are especially useful when:

• One status page covers several products or customer-facing services
• Different teams care about different systems on the same page
• You want to reduce notification fatigue without creating multiple separate status pages

Related guides

• Managing Status Page Subscribers
• Status Page Settings Guide
• Managing Components and Component Groups
• Creating and Managing Incidents
• Scheduling Planned Maintenance