The Web Push allows you to add a messaging node in Journeys. With a messaging node you can trigger a web push notification in the browser, if a profile has given consent for Web Push.
Set up the Web Push
Implement script
Before Push Notifications can be used, a script must be implemented on the website. You can read more about this in our API documentation.
Gathering consent
To trigger the web push notification, web push consent is required. You can collect this consent by overlaying the following in the CTA url input field:
{{ requestPushNotification }}
This variable replaces the CTA url with a JavaScript function that gives the browser consent for web push notifications. Please note: the consent is given to the cookie and not to the profile. If the consent has already been given in the browser, the personalization will no longer be displayed.
Example
In an overlay this would look as follows:
Web push in Journeys
The Web Push allows you to add a messaging node in Journeys. With a messaging node you can trigger a web push notification in the browser, if a profile has given consent for Web Push. The node looks like this:
How does the journey builder work?
Web push consent in Audiences
An audience can be created based on the web push consent:
This audience can be used as an entry for the journey with the messaging node, to show the notification.