This article will outline how consent management, also known as subscription management, is handled for each of our native web marketing channels.

Web Push Notifications Consent

When it comes to handling marketing consent for web push notifications, the consent is built into the browser, but you are able to prompt and collect the consent data via your SDK.

In terms of giving their consent, you can use push prompts with consent forms built in to demonstrate the value of opting in and register their intent, however, when they agree to notifications on this form, an additional browser message (known as a hard push prompt) will then be displayed on their device.

Notifications are sent via the browser, therefore the user must also consent in the browser window they are currently using. Only the built-in browser pop-up will actually opt customers into your marketing.

While the browser will handle the consent collection, you can gather the consent and token via the Web SDK. To learn more about gathering consent via the SDK, please review our Github where we have a dedicated repository for our Web SDK.

Please Note: If your website's domain changes, users will need to re-consent to web push notifications. This is due to how browser-based notifications work—each domain is treated separately, meaning consent cannot be transferred from one domain to another. It's important to plan for this if you anticipate a domain change, as users will need to go through the consent process again to continue receiving notifications. This ensures compliance with browser security standards. 

How to increase opt-ins

Getting your customers to opt-in to web push will be key for keeping them engaged with your website in the long run. There are a few best practices you can follow to encourage opt-ins for this channel.

• Provide Clear Value: Ensure that before you prompt the customer to opt-in to web push notifications, you have provided clear context and the value they would get out of receiving web push. For example, exclusive offers or time-sensitive sales. This can be helped by using a soft prompt, to demonstrate this value.
• Choose the Right Moment: Timing is everything. Review your onboarding process to determine when is the right moment to prompt customers to opt in. Consider the value you’ve already demonstrated, and how far through onboarding they are.
• Promote via In-App: If a customer hits “Don’t Allow” the first time, you may be able to bring them back using web page pop-ups later on. Again, ensure you are clear on why they would benefit from receiving your web push, to encourage them to update their browser settings.

Collecting consent for a Progressive Web App (PWA) must also be done using a browser’s built-in notification permission prompt, and gathering that data via the Web SDK. If you have any questions about configuring consent management for your PWA, please reach out to the team.

Web Page Pop-ups Consent

When it comes to Web Page Pop-ups, these are considered part of the website experience and therefore do not require an opt-in from the user. If you have any questions or concerns about marketing consent for Web Page Pop-ups, please reach out to the team.