A user must first opt in to notifications:

• Web: accepts the browser “Allow notifications” prompt (varies by browser/device).
• Mobile apps: accepts the OS permission prompt (and can later change it in device settings).

After opt-in, automated pushes are sent only to users who meet configured eligibility rules (based on engagement). These rules are periodically tuned to improve relevance and reduce fatigue.

Common reasons a user did receive an automated push:

• They are opted in and recently engaged with similar content/sections.
• The story was newly published/syndicated and eligible for automation.

Common reasons a user did not receive an automated push:

• They are not opted in (or disabled notifications at the OS/browser level).
• They are outside the eligible audience due to engagement-based rules.
• The story was not eligible (e.g., not treated as a “new” publish/syndication event).
• It occurred during quiet hours (see below).
• They hit a frequency cap (see below).

Automated pushes are intended for newly published or syndicated stories. Stories that are updated (but not treated as a new publish/syndication event) are not eligible for automated sends.

If a newsroom expects an updated story to be pushed, use a manual push when editorially appropriate.

Automated notifications follow quiet hours to avoid overnight disruption.

Current quiet hours policy (automated only):

• Automated pushes are allowed 7:00 AM → 9:00 PM local time, by station.

Manual pushes for urgent situations may still be used when necessary.

Automated pushes are governed by hourly and daily frequency caps to reduce notification fatigue.

If you receive reports of “too many pushes,” share examples with Product Support (station + date range + approximate volumes).

Manual and automated pushes are managed differently:

• Automated pushes are system-capped to protect against fatigue at scale.
• Manual pushes are treated as editorial overrides for high-priority moments.

If manual volume is high and users report fatigue, Product Support can help investigate trends and potential mitigations.

Not at this time. Automated notifications are primarily based on observed engagement signals and configured rules rather than user-selected topic subscriptions.

Yes. Manual pushes remain essential for:

• breaking news
• severe weather
• urgent public safety updates
• major live moments

Automated pushes are meant to handle “always-on” relevance; manual pushes cover editorial urgency.

The system is designed to avoid duplicate notifications for the same story. Users that receive an automated notification will be excluded from receiving the first manual notification for the same story.

If you see suspected duplicate behavior, send Product Support:

• story URL
• timestamps of the notifications
• station
• platform (web/app)

Visibility and reporting continue to improve over time. If you need:

• confirmation that a specific story was sent,
• approximate audience size,
• or investigation into volume/duplicates,

contact Product Support with the story URL/headline and send window. They can help route requests to the right owners and pull what’s available.