In this article, we describe how you can discover and segment:

• Number of users who have granted web push permission on your website
• Number of users subscribing to web push in a specified time duration
• Number of users unsubscribing from web push in a specified time duration
• Segment users based on the Web Page URL on which they subscribed to push notifications
• Segment users based on the Web Page URL they viewed
• Number of users receiving and clicking Web Push notifications 

Ensure that you have already integrated web push as mentioned here.

You will be running all these queries at MoEngage Dashboard > Segment > Create Segment. However, we also show the count of your Daily & Total Web Push Subscribers on MoEngage Dashboard > Dashboard > Key Metrics.

Total Web Push Subscribers

To identify no. of users who have subscribed to Web Push Notifications, select the User Property Web Push Subscription Status and select True from the drop-down.

 

This will also enable you to identify the no. of subscribers who unsubscribed after subscribing to push notifications once.

Note: Earlier, web push subscribers were identified via Web Push Preference is Granted. We are phasing this user attribute soon and replacing it with Web Push Subscription Status which is dynamic and updates the user's push subscription status either when users visit your website or when we get a response from GCM about the user's push token.

Web Push Subscriptions

You can also find out how many users have subscribed to Web Push over a specified time (allowed time filters - in the last X days, in between 2 dates, before a date, after a date, on a date, and today).

MoEngage identifier for this event is the user behavior termed "Subscribed to Web Push". 

 

Web Push Un-subscriptions

You can find out how many users have unsubscribed from Web Push over a specified time (allowed time filters - in the last X days, in between 2 dates, before a date, after a date, on a date, and today).

MoEngage identifier for this event is the user behavior termed "Denied Web Push Subscription". 

Note: There are two sources from where we get to know about users unsubscribing from Web Push Notifications. You can select the event attribute "Source" to distinguish between the two.

1. Website: When users directly remove permission from the website and reload the page, we update the subscription status to False and create this event Web User Unsubscribed with event attribute Source as Website.
2. Campaign: When users remove Push permission from Browser Settings, we get to know about the status from Push Services (GCM, AutoPush, etc.) when a campaign is sent to that user. Again, we update the subscription status to False and create this event Web User Unsubscribed with event attribute Source as Campaign

Web Subscription URL

This user attribute helps you to identify the pages of your website on which users are subscribing to push. This can be useful for creating custom segments of users using "Web Push Subscription Page URL" containing "sports" and sending only sports-related notifications to these users.

 

Web Page Viewed (Viewed Web Page)

This event helps you to identify the page of your website being viewed by the users. You can use this to create a segment containing users who viewed a specific landing page on your website and send relevant notifications. 

 

Note: A very good use-case of 'Viewed Web Page' event is to send viewed/cart abandonment notifications to your subscribers and take them directly to the web page they dropped off from. Read more here.

Notification Received Web

This event helps you to identify the users receiving and clicking notifications from the campaigns that you have created. If you wish to identify this event for a particular campaign, mention the Campaign ID as an event attribute in this query.

 

In case you have any queries, you can always raise a support request from the "Need Help?" drop-down.