Behind Web Push [Part 6]: Web Push—Get Up and Running

Before your website can begin sending web push notifications to the people who visit it, there’s some prep work required. The biggest part? Implementing your chosen customer engagement platform’s web SDK within your website, in order to support the kinds of data collection and message delivery functions needed to make your use of web push a success.

Let’s take the Braze web SDK as an example. When a Braze customer decides that the time has come to start sending web push notifications, they start off by adding the relevant snippet to the head section of the webpage in question and inserting their unique API key into it, making it possible for their website to begin logging customer actions and activity, and communicating (and sending data) to the Braze API.

One key thing to keep in mind? Any page that you’re looking to use to send web push should be secure, in order to prevent significant security vulnerabilities that can open you up to cyberattacks. Usually that’s going to mean that your website needs to have implemented the HyperText Transport Protocol Secure (HTTPS) protocol, but it’s also possible to address this issue by using Braze to create a secure modal in-browser message instead if that’s not feasible.

To get the full scoop on setting up your webpage to support web push, check out Braze documentation's detailed overview.

Anything else?

Looking to learn more about web push? Check out:

• Behind Web Push: All You Need to Know About Web Messaging’s Secret Weapon
• Behind Web Push [Part 2]: The History of Web Push
• Behind Web Push [Part 3]: Web Push Browser Differences
• Behind Web Push [Part 4]: Making the Most of Web Push
• Behind Web Push [Part 5]: The Downsides of Web Push