In this article, we've described how you can discover and segment Web Push subscribers for the following scenarios:
-
-
- Number of users who have granted Web Push permission on your website
- Number of users who have subscribed/unsubscribed 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
-
library_add_check |
Prerequisites Web Push is already integrated. For more information, refer to Web Push Integration. |
Navigation
-
-
- All these queries will be run on the following navigation: MoEngage Dashboard > Segment > Create Segment.
- You can view the Daily and Total Web Push Subscribers count on the following navigation as well: MoEngage Dashboard > Dashboard > Key Metrics.
-
Identifying the Total Web Push Subscribers
To identify the number of users who have subscribed to Web Push Notifications:
-
-
- Select the Filter users by option.
- In the User Property tab, select the Web Push Subscription Status attribute and select True from the drop-down.
-
This will also enable you to identify the number of subscribers who unsubscribed after subscribing to Push notifications once.
Note: Earlier, Web Push subscribers were identified using the criteria 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).
The MoEngage identifier for this event is the user behavior termed Subscribed to Web Push. To identify the number of subscriptions:
-
-
- Select the Filter users by option.
- in the User behavior tab, select the condition Has Executed Subscribed to Web Push event at least 1 time and add the timeframe of your choice, as shown below.
-
Web Push Unsubscriptions
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. To identify the number of unsubscriptions:
-
-
- Select the Filter users by option.
- in the User behavior tab, select the condition Has Executed Denied Web Push Subscription event at least 1 time and add the timeframe of your choice, as shown below.
-
info |
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.
|
Web Subscription URL
The Web Push Subscription Page URL is a user attribute that helps you identify the pages of your website on which users are subscribing to Push. This can be useful for creating custom segments of users using the attribute, as described below.
To send only sports-related notifications to a certain set of users, you can add the criteria as Web Push Subscription Page URL contains sports.
Web Page Viewed (Viewed Web Page)
The Viewed Web Page event helps you 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, as shown below.
A popular use-case of the 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. For more information, refer to Web Push Campaigns in 60 Minutes.
Notification Received Web
The Notification Received Web 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.