This article provides answers to the most common questions regarding Web Push.
Contents
- Will push notifications be seen when the contact is not on the site?
- What happens if the browser is closed when the push campaign is launched?
- Can I import tokens from a previous provider?
- If the contact previously accepted push permission, will they need to accept again when we transfer to Emarsys?
- If the contact previously rejected push permission, can we prompt them again?
- Can I use personalisation with web push campaigns?
- Can I add web push to my automation programs, like abandon basket?
- How can I check how many contacts have accepted Web push messaging?
- How do users disable/opt-out of web push campaigns if previously accepted?
- I sent a campaign with a banner image. The message displayed but not the banner image. Why?
- I sent a campaign with action buttons. The message displayed but not the action buttons. Why?
- How long does the implementation of Web Push take?
- Will be any performance or page load issues after the Web Push implementation?
- I use an old provider for Web Push. While changing to Emarsys, I want to use it parallel in order to maintain my client database. Can I have the old provider and Emarsys live at the same time?
Will push notifications be seen when the contact is not on the site?
Yes. Web Push messages are displayed to the user even if the user is not on the website where they subscribed to push notifications. Web push campaigns are sent to the browser, not to the site, which is why they still display. However, the browser needs to be active/open. It can be minimised and the push notification will still be received.
What happens if the browser is closed when the push campaign is launched?
The push campaign will be queued. Once the browser becomes active again, the push message will be displayed. The length of time the message is queued is dependant on the browser and operating system, as the message is queue by the browser and not Emarsys.
Can I import tokens from a previous provider?
It is strongly recommended not to attempt/request to import push tokens from previous providers. The detailed reasons why can be found in the article "migrating from a previous provider". In summary, trying to use imported tokens will not speed up migrating from a previous provider. Either the push messages will not be displayed correctly if trying to use an imported token or for Safari users, the event reporting would go to the old provider and not Emarsys.
If the contact previously accepted push permission, will they need to accept again when we transfer to Emarsys?
No. When the user accepts push notifications, the setting is saved for the domain on the browser. When the user revisits the site after the implementation of the Emarsys SDK, the push token will be sent to Emarsys (there will not be pop up message requesting push permission).
If the contact previously rejected push permission, can we prompt them again?
The browser will block the push permission request, as the notification setting is saved on the browser. It is not possible to override this.
Can I use personalisation with web push campaigns?
In short, yes. Web push is integrated with the personalisation service.
Can I add web push to my automation programs, like abandon basket?
Yes, web push is integrated with the Emarsys Automation Centre and Interaction programs, so you can add web push to your automation programs as an additional channel. However, currently it is not possible to include product details from the product catalog in the content of the push campaign, so for abandon basket campaigns, the content would be more general (e.g. "you left something in your basket").
How can I check how many contacts have accepted Web push messaging?
The simplest way would be to create a segment where the criteria is set to Web push notifications enabled.
How do users disable/opt-out of web push campaigns if previously accepted?
To opt-out of web push campaigns, after previously accepting, the user would have to go to the browser settings and manually disable push notifications.
I sent a campaign with a banner image. The message displayed but not the banner image. Why?
Banner images (the larger image of the campaign) are not supported on certain browsers and operating systems. As an example, Chrome supports banner images on Windows but not Mac OS. The rest of the campaign will still be received and displayed, except the banner image.
I sent a campaign with action buttons. The message displayed but not the action buttons. Why?
Like banner images, action buttons are not supported on all browsers and operating systems. It is important to set a default action for the web push campaign so users that do not see the action buttons are still able to be redirected to the website when clicking anywhere on the campaign.
How long does the implementation of Web Push take?
It depends on the complexity of the website, but it is not a large undertaking. We have seen it implemented on a small test website within an hour. Clients with large complex sites have taken a couple of days to get to the testing stage.
Will be any performance or page load issues after the Web Push implementation?
The Web Push SDK does not have any negative effect on the performance and page load of your website.
I use an old provider for Web Push. While changing to Emarsys, I want to use it parallel in order to maintain my client database. Can I have the old provider and Emarsys live at the same time?
Yes, you can use the same (old) VAPID key and add it to the Emarsys settings.
You can still send push notifications to those browsers where the user did not open the page yet and our SDK is integrated already. However, as soon as a user opens the page, where our SDK is integrated, the browser will be registered on our side and it will be no longer possible to reach the browser via the old provider. The reason for that is that a new push token will be assigned and the old one will be no longer valid.