Types of Web Push Opt-in
- 04 Apr 2024
- 1 Minute to read
Types of Web Push Opt-in
- Updated on 04 Apr 2024
- 1 Minute to read
Article Summary
Share feedback
Thanks for sharing your feedback!
The first step to start sending push notifications is to get an opt-in from your users to confirm that they want to receive your updates. You can do it in two ways to get an opt-in from a user on your website;
Native (HTTPS) Opt-in
This is the browser’s own permission screen, and is required to get the user's consent to send web push notifications from a particular website and domain. Native opt-in requires the website fully supporting HTTPS .
Custom (HTTP) Opt-in
It’s a pre-screen before displaying the actual native opt-in on a pop-up screen and can be used as an alternative if the website does not fully support HTTPS.
Native (HTTPS) vs. Custom (HTTP) Opt-in
| Native (HTTPS) Opt-in | Custom (HTTP) Opt-in | |
|---|---|---|
| Customizable | No | Yes |
| Website must support HTTPS? | Yes | No |
| Source of the domain for web push | Your domain | Insider's domain |
| Opt-in rates | High | Low (compared to Native) |
| Can it be displayed again if user blocks it? | No | Yes |
| Service Worker | Must be uploaded to the website | N/A |
Was this article helpful?