Web Push Analytics FAQ explains metrics, tracking, reporting, and analysis for Insider Web Push campaigns.
How do you calculate the Web Push Click-through Rate (CTR)?
Insider determines the Click-Through Rate (CTR) by dividing the number of Clicks by the total number of Delivered Web Push notifications. This calculation takes into account the entire user base that has the opportunity to click on your Web Push notifications. Consequently, the CTR provides a direct indication of your campaign's effectiveness. Since the user base used in the calculation consists of individuals who have viewed your messages, the click count from these users is closely connected to the content of your Web Push notifications. This correlation allows you to easily establish a relationship between your marketing strategy or content and the CTR metric of your campaigns.
Why do I see the old metrics when the start date in the date picker is earlier than June 01, 2023?
Insider has started calculating metrics such as frequency capped, silent hours, and unsubscribers after sending a campaign as of June 01, 2023. However, you might still want to analyze trend changes in a previously created campaign, such as a recurring push or a Trigger Push that has been active for months. That's why you still see the old metrics in the analytics dashboard if you pick a start date earlier than June 01, 2023, in the date picker. You can always set the date picker start date to a later date than June 1, 2023, to check the new metrics.
Is the same date rule applicable to exports?
Yes, it is. For exports starting before June 1, 2023, you will receive an export with the old metrics. Those starting after June 1, 2023, will receive a report with the new ones.
I pick the same date range on the Web Push Subscriber Analytics and Web Push Analytics pages. However, the unsubscription counts are different. Why?
The Web Push Analytics page displays the unsubscription metric campaign-based, while the Subscriber Analytics page displays it log-based. On the Subscribers Analytics page, regardless of campaigns, you see the total count of the unique unsubscribers received within the selected time period for any campaign. On the Web Push Analytics page, campaigns are displayed based on your selected date interval, and the sum of unsubscriber responses collected from the Push Service after sending these campaigns is shown as unsubscriptions. Since the calculation here is campaign-based, unsubscribers from Architect journeys are not counted under the Dropped tab of the Unsuccessful Messages chart. Furthermore, on the Subscribers Analytics page, you see the unique unsubscriber number for the selected time interval; on the Web Push Analytics page, there is no uniqueness (if a user opts out, opts in, and opts out again at the same time, it will be reflected as 2 Unsubscriptions). The campaign-based calculation also affects the time-zone mechanics for both pages.
Your title goes here
The opt-ins are reflected one day later in the Web Push Subscriber Analytics dashboard.
Why is the dropped count in the top metrics not equal to the total of dropped in the unsuccessful messages area?
The dropped metric area is calculated as the difference between the initially targeted users and the Web Push notification requests sent to the push service for those among these tokens. There are cases where the push request is sent much later than the token is targeted, such as sending the push notification after the silent hour duration has been completed. The targeted metric is counted right away when the user becomes eligible for the push, but the sent metric is counted only after the silent hours are completed and the push message is ready to be sent. Another example is sending pushes with a delay. For instance, if you have a Cart Reminder campaign that is triggered after 24 hours, once the user becomes eligible to receive the push, Insider collects the targeted metric. However, for the same user, you get the sent metric after 24 hours when you send the Web Push notification.
Therefore, the top metrics' dropped count (Targeted - Sent) might differ slightly from the dropped count in the unsuccessful messages (calculated as Frequency Capped + Silent Hours + Unsubscriptions + Service Provider Errors + Internal Errors).
What is the reason for including the offline recipients under the undelivered breakdown in the Trigger Web Push?
Even though Trigger Web Push is triggered while the user is visiting your website and meets the preset rules, there are some cases where users cannot receive the push. For example, even though the user is not unsubscribed, their device or browser settings might block them from receiving the push. The user’s device might be in Focus / Do Not Disturb mode, which prevents notifications from appearing. These users are also counted as Offline Recipients. Or, in specific cases, such as slow internet connections, logs might not be sent to Insider, which is another potential reason for having Offline Recipients in Trigger campaigns.