User Model only supports HTTPS sites
HTTP is not supported with v16 of the OneSignal Website SDK, your site must start with
OneSignal stopped supporting new apps from using Blogger, Bubble, Squarespace, Webflow, Weebly, Wix, HTTP sites, and website builders that don't support uploading Service Workers to a server (which are required for web push).
We used to provide a workaround subdomain like
https://LABEL_HERE.os.tcso we would host the Service Worker files for you, but this isn't going to be supported anymore for several reasons, the most important being:
- This doesn't work for iOS Web Push
- It provides a bad User Experience for your users
- Chrome is making a change detailed in their storage partitioning plans / CHIPS which when enabled prevents our SDK from checking unsubscribe stats when using the
If you currently use the the os.tc subdomain, you can continue to use it but will no longer be able to prompt for push notifications. Your existing subscriptions will continue to receive notifications. Starting September 8th, Chrome's change will prevent users from being able to unsubscribe when they visit the
https://LABEL_HERE.os.tc/unsubscribepage. They will need to unsubscribe from the browser notification settings.
Sorry for the inconvenience. We know a lot of people want this. Especially for blogger, hopefully the Google Team will support this someday: Is it possible that I can build progressive web app for my Blogger blog
If you use one of these types of site builders, you may be able to work around this by following our Typical Website setup and put a CDN in front of your domain to host the
OneSignalSDKWorker.jsService Worker file. But this is quite technical and we don't have any guidance on how to setup the CDN.
OneSignal supports two different underlying technologies for customers looking to integrate push notifications on their websites. These technologies are called the HTTPS SDK and the HTTP SDK.
Customers that have more control over the technology used to build their sites will typically support our HTTPS SDK, whereas customers that use website builder software such as Shopify and Blogger often must use our HTTP SDK.
Recommendation: We recommend new customers always use the HTTPS SDK if their website supports it.
Using push notifications with our HTTPS SDK has the following benefits that are not available when using our HTTP SDK:
- Clarity - Push notifications are seen as officially coming from your domain name, rather than
yoursite.os.tc. This may help reduce confusion with some users.
- More subscribers - Users need to go through one less step to subscribe to notifications, meaning less friction to subscribe.
- More options - You may directly trigger the Browser Permission Request on the page users are on.
- More flexibility - Users may be migrated from one push provider to another.
Recommendation: Before using the HTTP SDK, we recommend customers first determine if they can upgrade their site to meet the requirements for using the HTTPS SDK. We recommend using the HTTP SDK only if you cannot use the HTTPS SDK.
The following are some reasons why you may not be able to use our HTTPS SDK:
- Some HTTPS website providers do not allow uploading files to the root directory, which is required to use the HTTPS SDK. These providers include (but are not limited to): Shopify, Blogger, Drupal, Squarespace, Weebly, OpenCart, and others.
- Not all sites use HTTPS exclusively. Some sites use a combination of HTTP and HTTPS (e.g. some shopping sites), and the OneSignal HTTPS SDK requires exclusive use of HTTPS.
- Not all sites use HTTPS at all. Some sites only use HTTP.
The OneSignal HTTP SDK allows website operators to work around the limitations of their website technologies to offer push notifications when they otherwise could not. The capabilities of the OneSignal HTTP SDK are somewhat limited relative to our native HTTPS SDK, which is why we encourage people to use our HTTPS SDK when possible. The effects of these limitations are as follows:
- Less clarity - Push notifications do not come from your own domain, and instead must come from the label you chose using the
- Fewer subscribers - Users must always go through an extra step to subscribe, clicking on a button in a pop-up window that is displayed after they opt-in to notifications in order to become subscribed.
- Less flexibility - Users cannot be migrated away from OneSignal.
Some customers may wish to switch from the HTTP SDK to the HTTPS SDK to gain the user experience benefits of the HTTPS SDK. The only requirement to upgrade is that your site must only support HTTPS and must be able to upload files to the root directory of your website.
ALL CURRENT SUBSCRIBERS WILL BE LOST when switching from our HTTP SDK to our HTTPS SDK. Learn more.
DO NOT UPGRADE if the HTTP version of your site is still accessible. If users visit your HTTP site after you upgrade to the HTTPS SDK, they will not be able to subscribe. Learn how to redirect users to HTTPS.
Just create a new app for your site following our Typical Setup process, enter in your new HTTPS site URL, and be sure to leave the
My site is not fully HTTPS option disabled.
Create a new app for your HTTPS site following our Custom Code Setup guide.
Update your site with the new initialization code. There should not be a
subdomainNameparameter in your init code.
Create a new app for your HTTPS site following our Wordpress Setup process, enter in your new HTTPS site URL, and be sure to leave the
My site is not fully HTTPSoption disabled.
Visit your WordPress admin panel, visit our plugin admin page, select the Configuration tab, and at the top under Account Settings enable "My site uses an HTTPS connection (SSL)".
Make sure the "App ID" textbox points to your new app's ID.
Make sure your "REST API Key" textbox points to your new app's REST API key.
Important: If your Configuration page shows a Google Project Number textbox, be sure to clear this value and then click Save.
Just create a new app for your site following the appropriate setup guide (Magento, Joomla, Drupal), enter in your new HTTPS site URL, and be sure to leave the
My site is not fully HTTPS option disabled.
Once you've upgraded to the HTTPS SDK, you should have two apps in OneSignal: one for your users that signed up on the legacy HTTP SDK, and one for any new users that have signed up on the HTTPS SDK. We recommend only sending notifications to users in your app that uses the HTTPS SDK. Learn more.
If your old app had Automated Messages, Segments, or Templates, you will have to recreate those in your new HTTPS SDK app.
Web push permissions and subscriptions are separated by domain/protocol, and the browser considers http://site.com and https://site.com to be two entirely different sites, and so there isn't a way to transfer the subscription.
While your old users are still subscribed and can be reached, we do not recommend sending notifications via your old app. This is because once you switch to your HTTPS site, any users previously subscribed will see a prompt requesting them to subscribe again, meaning users are likely to become double subscribed. If you then send notifications from both your old HTTP app and your new HTTPS app, those users will receive two notifications. After setting up your HTTPS app, you can send one last message to your old subscribers letting them know you've switched over.
Web push notifications actually do not support HTTP sites at all. We work around the issue by sending notifications from a subdomain of our site,
.os.tc, which is an HTTPS site. You choose a subdomain to represent your site, and push notifications are officially sent from
*subdomain*.os.tc. Due to browser restrictions, our workaround requires a popup to be shown, since users are actually subscribing to
*subdomain*.os.tc. As long as you are using our HTTP integration, this is always true and a popup will always be required.
If you're using CloudFlare, you can forcefully redirect all HTTP visitors --> HTTPS.
Updated 22 days ago