LogoLogo
  • Home
  • Integration & SDKs
    • Web / Browser Push
      • Wordpress Integration Steps
      • Wix Integration Steps
      • Safari
        • Safari on Desktop
        • Safari on Mobile (iOS / iPadOS)
      • SDK
        • SDK Methods
        • SDK Events
        • Customizing Prompt CSS
        • AMP Support
        • E-Commerce / Abandoned Cart
    • Native App Push
      • Apple / iOS
        • P8 Key or P12 Cert Setup
        • SDK: Swift / Obj-C
          • Activity Tracking
          • Deep Linking
          • Live Activities
          • App Messages
          • Identity Synchronization
          • SDK Methods
          • SDK Delegates
        • SDK: React Native
        • SDK: Flutter
        • Advanced
          • Self-Managed Integration
        • iOS SDK Changelog
      • Android
        • Firebase App Setup
        • SDK: Kotlin / Java
          • Deep Linking
          • Activity Tracking
          • App Messages
          • Identity Synchronization
          • SDK Methods
          • SDK Callbacks
          • Live Activities
        • SDK: React Native
        • SDK: Flutter
        • Advanced
          • Self-Managed Integration
        • Android SDK Changelog
      • React Native
        • Android: Firebase App Setup
        • iOS: P8 Key or P12 Cert Setup
        • SDK: React Native
          • Deep Linking
          • Activity Tracking
          • Subscriber Matching
          • Live Activities
          • App Messages
          • SDK Methods
      • Flutter
        • Android: Firebase App Setup
        • iOS: P8 Key or P12 Cert Setup
        • SDK: Flutter
          • Deep Linking
          • Activity Tracking
          • Subscriber Matching
          • Live Activities
          • App Messages
          • SDK Methods
  • API
    • API Access Management
    • API Reference
  • Platform
    • Dashboard
    • Notifications
      • A/B Testing
      • Custom Buttons
      • Notification Previews
      • Inline Segmentation
      • Notification Templates
      • Macros
      • Native App Push Notifications
    • App Messages
    • Segments
      • Custom Geo Segmentation
    • Campaigns
    • Insights
    • User Management
    • Organizations
      • Multi-Factor Authentication
      • Single Sign On
        • Google Workspace
        • Microsoft Azure AD
        • Okta Workforce
      • Multi-Domain Notifications
      • Multi-Domain Segments
      • API Access
    • Multi-Channel Notifications
  • Info Center
    • Launch Guide & Best Practices
      • Landing Domain Whitelist
    • Web / Browser Push
      • Common Questions
      • Browser Support
      • Retrieve Push User ID
      • Not Getting Prompted
      • Not Receiving Notifications
      • How to Unsubscribe
    • Native App Push
      • Retrieve Push User ID
    • Workflow Planning
Powered by GitBook
On this page
  • What are Browser Notifications?
  • Which devices and browsers support Notifications?
  • How do visitors subscribe to get Notifications?
  1. Info Center
  2. Web / Browser Push

Common Questions

PreviousWeb / Browser PushNextBrowser Support

Last updated 2 years ago

What are Browser Notifications?

Browser Notifications are content units delivered directly to a subscriber’s device. The appearance of a Notification varies depending on which device and browser combination the subscriber is using at the time of subscription.

Which devices and browsers support Notifications?

Generally speaking, most major market browsers and devices support Notifications. The key exception is iPhones, which have not yet been opened to the browser Notification channel. For a full list of browsers please see the FAQ.

How do visitors subscribe to get Notifications?

In order to become a Notification subscriber, website visitors must give the domain they are currently visiting explicit permission to deliver Notifications. In the Chrome desktop browser, this permission appears as a gray box in the upper left corner of the window. The box gives the visitor the option to “Allow” or “Block” Notifications. If the visitor selects “Allow”, they become a subscriber and can be sent Notifications.

Firefox, Edge, and other browsers carry somewhat varied language when presenting visitors with the option to subscribe to Notifications, but all require either an affirmative response in order for a visitor to become a subscriber.

Browser Support