This article will guide you through the setup of push notifications delivery from your own domain.
- HTTPS website (if you don’t have all your domain using ssl this will not work)
- your URL’s should start with https:// . All other http:// only should redirect to the https:// version
- Access to upload files to your server (FTP, SSH or anything)
- Able to edit html files on your website
Download and edit files
Download our archive of push files. The archive contains:
*** represents the name of the running instance, and can be missing resulting in: push_worker.js
Important: These files needs to be accessible publicly.
Try opening those files directly in your browser and you should be able to see something similar to the following.
Upload all files to your root domain. After upload both should be accessible at:
Add code to your website:
This is very important: you need to reference manifest.json in your <head> tag.
It MUST appear before any other <link rel=”manifest”> tag.
<link rel="manifest" href="/manifest.json">
What if there is already a manifest on my site?
Web browsers only support sites with one manifest in the head tag. If your site already has a link tag with a manifest, you can do one of two things:
1. Copy the following parameters at the end of your existing manifest (recommended)
"gcm_sender_id_comment": "VTpush manifest", "gcm_sender_id": "103953800507"
Make sure you keep the right format, with , (comma) between values and you do not overwrite other values.
2. Rename the manifest file and make sure you link it before the other manifest in your page.
Note that this will disable any functionality associated with the other manifest.
Enable https PUSH from dashboard
Now you won’t need another window to open when users accept to receive push notifications. From Campaigns -> Push choose Permission Tab and then under Ask users for permission? click Yes, edit the texts and add your logo and Save settings.
You can Preview the permission widget by clicking Preview Widget on the right.