Skip to main content
Analytics glossary

You will find here the definition of all the words used in Batch analytics: push campaigns, In-App automations and general analytics.

Antoine avatar
Written by Antoine
Updated over a week ago

The number of times the SDK "starts" in your app over a period of time. The SDK starts every time users open your app. The starts/DAUs ratio can help you to measure the average number of sessions initiated by your users.

Stands for Daily Active Users. It represents the number of unique installs that opened the app at least once a day.

Stands for Monthly Active Users. It designates the number of unique installs that opened the app at least once a month.


Stands for Monthly Active Profiles. It designates unique deduplicated profiles on which Batch has recorded activity in the last month. An activity is an attribute change or an event observed on one of the connected data sources: SDKs, APIs, email opens (whether users connect to the app/website, or send updated data for a given profile).
Relevant APIs : Profile API, Custom Data API, Trigger Events API.

Designates an installation of a version of your app including Batch SDK. The number of installs never decreases. A reinstall of your app is considered a new install.

💡 In web push, designates people who have visited your website at least once since the installation of the SDK.

Deletion of the app on a user's device.

Short for the opening of a push campaign. Batch measures 2 types of opens:

  • Direct opens are the number of opt-in installs who opened your app by tapping the notification.

  • Influenced opens are the number of users who received a notification and opened your app within the next 3 hours.

Users who accepted to receive your notifications.

Users who didn't turn on yet refused or disabled push notifications for your app.

Reengaged users:
Dormant users who received a notification opened it and then came back to the app/ website in the 3 days following the notification reception.

Trigger analytics:

  • Targeting mismatch: all the users who had initially entered the journey and who no longer correspond to the targeting at the time of the trigger (for example, the user is no longer premium at the time of the push when he was at the beginning).

  • Campaign ended: all users who received the campaign once, and will no longer receive it because there is a capping of 1.

  • No push token: all the users that Batch could not address because they do not have valid tokens (if they uninstalled the app for example).

Need more help?
Feel free to check our detailed documentation here:

This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on and our blog.

Did this answer your question?