Architect Channel: Web Push

Prev Next

Web push notifications are actionable messages sent to a visitor’s device from a website via a browser. They are contextual, timely, and personalized, and best used to engage, re-engage, and retain website visitors. These messages are sent directly to a user’s device, pop up as soon as they’re received, and reside on the notification panel. 

This guide explains the following concepts:

How does the Web Push channel work?

Before sending a web push notification to a user, the journey checks if they are reachable on the web push channel.

If the user is reachable, they receive a notification when they are online. If the user is not reachable, they drop from the journey.

The reachability function checks the user’s web push opt-in, web push token, and GDPR opt-in. Web push opt-in and a token are generated when the user allows the browser web push notifications. 

The journey does not attempt to send a web push to a user;

  • If they do not have a web push token.
  • If their token has expired.
  • If they have not allowed to receive notifications.
  • If their Gdpr Optin is false.

If your company obtains your users' consent in compliance with the local regulations, make sure to pass the GDPR opt-in field to Insider One. If you want to stop collecting and processing the data of an identified user, GDPR opt-in field should have the false value. Insider One cannot be held liable if these obligations are not fulfilled and reserves the right to seek compensation from your company.

If the user's browser is offline, the push service queues the notification until the browser becomes online to deliver it. With this request, we specify the content of the notification, to whom to send it, and the settings about how the push service should send the notification, like the Time to Live (TTL) value. TTL defines how long the push service should keep a notification in the queue before removing it. When the TTL expires, the notification will be removed from the push service queue, and it won’t be delivered.

Use Cases

With the Web Push channel in your journeys, you can send:

  • Cart abandonment notifications,
  • Browse abandonment notifications,
  • Post-purchase notifications,
  • Welcome messages to new users,
  • New offers to silent users,
  • Messages about the new season to active users.

Tips & Tricks

  • You can use the Check Reachability element before adding a web push channel. Accordingly, you can take another action on users or send messages through other channels.
  • You can use the rich web push option by adding a dynamic image to engage your users with the last browsed or last abandoned item. 

Integration

You need to ensure that you have completed Web Push Integration, also known as Native Opt-in Integration with VAPID before setting up your Web Push in Architect. Read more on web push integration here.