Enabling Web-Push Notification

Web push notifications are clickable rich content messages sent to your device by a website or a web app. Push notifications are delivered to your mobile device or desktop, even when your browser is closed. These notifications can only be sent to users who have subscribed to these notifications from a specific website on Chrome, Firefox and Safari.

Sending web push notification is easy with iZooto. Create an account and after that, you need to follow the below steps to push notifications to your subscribers.

For Websites on HTTPS

Insertion of the iZooto JS Code

The below code (sample) needs to be placed before the </head> tag on all the website pages.

<script> window._izq = window._izq || []; window._izq.push(["init"]); </script><script src="https://cdn.izooto.com/scripts/abc123def456.js"></script>
You can avail this by logging into your iZooto dashboard and clicking on Settings >> Integration Instructions. This code using Google Tag Manager too. Click here to know how.
You can also add this code asynchronously.
<script> window._izq = window._izq || []; window._izq.push(["init"]); </script><script async="true" src="https://cdn.izooto.com/scripts/abc123def456.js"></script>
Adding of files
Two files - manifest.json and service-worker.js need to be placed on the same domain as your website. For instance, if your website is https://abc.com, here is how they need to be placed on the basis of your root folder accessibility.

For websites which doesn’t have access to root directory, in addition to the above step, you need to contact at [email protected] with the mail subject, <Website name>:Root Folder Inaccessible.

Once you are done, with the above 2 steps, the subscription prompt would start to populate on your website and here is a sample of how it would look.

For Websites on HTTP

Web Push Notifications work only on SSL websites (HTTPS). However, HTTP websites can use web push notifications by creating a sub-domain on HTTPS. Unlike HTTPS websites, the subscription process is a 2 step process and involves the visitor clicking on 2 CTAs(Click to Action) before getting subscribed to a particular website.
In the first step, websites can set up the context with an interactive message on a custom dialog box while the actual subscription prompt appears in the second step on the HTTPS sub-domain.
Despite the above possibility, we recommend our customers whose website is on HTTP to migrate to HTTPS at the earliest. Click here to know why.
Insertion of the iZooto JS Code
The below code (sample) needs to be placed before the </head> tag on all the website pages.
<script> window._izq = window._izq || []; window._izq.push(["init"]); </script><script src="https://cdn.izooto.com/scripts/abc123def456.js"></script>
You can avail this by logging into your iZooto dashboard and clicking on Settings >> Integration Instructions. This code using Google Tag Manager too. Click here to know how.
You can also add this code asynchronously.

Best Practises for HTTP websites

The 2-step process may be a little confusing for website visitors as they would get redirected to another HTTPS site saying, abc.izooto.com wants to send you notification. This is the reason we recommend that subscriptions be taken on your own domain. Doing so will ensure a complete ownership of your subscribers and also will help you in seamless migration, if required.
Taking subscriptions for your HTTP website on the same domain can be achieved in 3 different ways:
a. Subscriptions on your subdomain by doing a CNAME entry
A Canonical Name Record aka CNAME entry is a type of record in DNS which is used to indicate that the domain name is an alias for another domain. With CNAME approach, we take subscriptions on customer’s sub-domain. There are two parts to the implementation:
  • Add a CNAME entry so that notify.abc.com points to notify.izooto.com
The above entry for http://abc.com would make https://notify.abc.com point to https://notify.izooto.com.
  • Install a single-domain SSL certificate on your domain
You need to provide us with a single-domain SSL certificate to configure it on https://notify.abc.com. Alternatively, we can buy it too on customer’s behalf and get it installed on the sub-domain. Once both steps are completed, we will modify SDK at our end to take subscriptions on https://notify.abc.com
b. Take subscriptions on the main domain by creating a single HTTPS page
You can create a single HTTPS page – https://abc.com/notifications, while the rest of the website still resides on HTTP. Once done, we will provide you with an updated SDK, and the integration would be the same as that of a HTTPS website.
c. Take subscriptions on the main domain by migrating your website to HTTPS
Migrate your complete website to HTTPS and enable web push notification there.

Website migrated from HTTP to HTTPS

After you have moved your website from HTTP to HTTPS, there are certain steps that need to be implemented for a smoother migration and experience of your subscribers. We recommend you send a mail to [email protected] right after you migrate to HTTPS.
Placing of files - manifest.json and service-worker.js
Two files would be provided to you which need to be placed in the root directory of your website and should be accessible as given below.

For websites which don’t have access to root directory, in addition to the above step, you need to contact at [email protected] with the mail subject, <Website name>:Root Folder Inaccessible.

Subscriber migration has a one time fee of $200 attached to it.


    Did this help answer your question?

    👍
    👍

    Thanks for the feedback! 🙏🏽


    Help by drift