What is an engaged user?
Total engaged users is the total number of your current app users who have your app on their devices and accessed it at least once in the last 365 days.
What is the difference between click-through reporting and view-through reporting?
Click-through reporting shows you the user behavior after they open the push notification. It gives you the number of people who opened the push notification and completed the goal event. View-through reporting shows you the user behavior after they receive the push notification. Insider tracks users for the next 6 hours by default after they receive the push notification. If that user opens the push notification in that 6-hour period, their goal behavior is projected to view-through reporting. You can change the tracking duration in the settings. View-through reporting always includes click-through numbers. View-through reporting is also essential when you have a control group variant. Users in the control group will not receive any push notification, and it will not be possible to make any comparison in click-through reporting. So these users' behavior can be seen in View-through reporting.
Take, for example, a user who opens a push notification and performs an event after the 6-hour period. Is this user counted in the click-through reporting?
No, the event should be completed in the session created by this push notification. This event will be reported in the view-through reporting.
Are the users who have not allowed push notifications included in the push notification analytics?
No, users who have not allowed push notifications are not included in the reporting as they do not receive any push notification.
How is Primary Conversion Goal calculated? Is it calculated based on Open logs or Delivered logs?
It is calculated based on push deliveries.
Why are user count and impressions different than the In-app results?
Impressions show how many times that In-app is seen and User Count shows how many unique users have seen the In-app. If frequency capping is not set as never, an In-app campaign can be displayed multiple times to a single user. The difference is originated because of this reason.
What does 0 conversion mean?
Conversions metric displays the number of people that perform the primary goal event set within the campaign. If you do not set any event, the conversion will be 0 even if the campaign has revenue. Also, revenue is not calculated through conversions but is a standalone metric. For example, if the conversion is set to "an item booked", it would not be related to the revenue metric.
If you see 0 revenue and conversion, make sure to have integrated the Track Revenue method. You can refer to Android, iOS, React Native, Flutter, and Cordova pages for further details.
Do we see the number of purchased products in conversions?
App push and app template results display the number of transaction but not the number of purchased products. For example, if you buy 3 products, the conversion will be logged as 1 instead of 3.
Why doesn't our App Smart Recommender campaign have any click, add-to-cart, conversion, or revenue data?
If the analytics of the campaigns do not work properly, you should check the respective integration. Refer to Android, iOS, React Native, Flutter, and Cordova for the integration details.
What is the difference between an inApp view event and inapp view from push event?
An inApp view event is triggered by an inApp campaign while inApp view from push event by an app template from push campaign.
Can we track offline events in an app push campaign?
No, currently only SDK events can be tracked.
If a user sees two inApp campaigns and completes only one purchase, will it be logged for both campaigns?
Yes, the purchase is logged for both inApp campaigns in this case.
Why does our push campaign's Exact Audience differ from the Delivered count?
Exact audience is the number of devices that match your targeting conditions at the time you check. The delivered count is the number of devices that actually receive a notification during the campaign. A series of checks happens between those two moments, and each one can filter out devices. Because of this, the exact audience does not guarantee how many devices will receive your message, and some gap between the two numbers is expected.
Exact audience already accounts for:
- App push opt-in (a device is also filtered out if opt-in data is missing entirely)
- Push token presence
- GDPR consent (only devices with an explicit false value are filtered; a blank value doesn't cause a device to be excluded)
- Devices flagged for ghost push or uninstall detection
The counts diverge due to various causes:
- Expired or mismatched push certificate. Every device on that platform is silently filtered out, and Exact Audience shows no warning. If the gap is large on a single platform, check your certificate first. This is the most frequently misdiagnosed cause.
- Mobile App Access. Exact audience doesn't factor in this setting; it's only checked at send time. Devices with it disabled still show up in the audience count but don't receive the message.
- Frequency capping, quiet hours, and re-eligibility rules. Audience counting doesn't simulate these rules. Devices get counted first, then drop out during delivery.
- Delayed uninstall detection. Ghost push detection runs once a day, at midnight in the app's local time. A device that uninstalled the app this morning is still counted in exact audience and falls into the undelivered bucket at send time.
- Blocked tokens and APNs/FCM errors
- The exact audience is calculated the moment you check it and isn't stored. For scheduled campaigns, hours can pass between that check and the actual send. During that window, devices can opt out, get uninstalled, or stop meeting your targeting conditions. The longer the delay, the bigger the gap.
You can check the dropped and undelivered breakdown in your campaign report. Both sections list the reason for each device, and in most cases, that breakdown explains the reason behind the gap.