Glossary
This glossary defines key terms used in Batch. Expand the letters to display definitions and key information:
A
APIs
Batch has several APIs, each with a specific mission:
App Data API Allows you to send custom data you associated to your application. This is particularly useful if you need app-level data in your campaigns, such as dates or attributes (e.g. Quick! Premium subscription discount will end in 3 days).
Custom Audience API Allows you to upload static segments exported from your userbase (e.g. top 500 buyers, etc) or created by third-party tools like Tinyclues, for example. You can easily retarget these custom audiences with a push or an In-App automation from the dashboard.
Custom Data API Allows you to send custom data for specific custom user IDs to improve your campaign targeting and personalization with your own custom data.
GDPR API Lets you make requests to fetch and/or delete user data from our database.
Push / In-App automation API The Push / In-App automations APIs allow you to create Push or In-App automations remotely, from your own CMS, for example.
Transactional API The Transactional API is made for 1-to-1 or 1-to-few interactions. It allows you to send push notifications to a specific list of user IDs (push token or Custom User IDs) based on events in your back-end (e.g. "You have a new friend request")
B
Bounce
Bounces refer to an unsuccessful delivery attempt. In fact, bounces mean that the email couldn't reach the intended recipient for various reasons.
Different types of bounces
Hard bounce — These emails were undeliverable because the email address is invalid. The email cannot be delivered to the recipient due to a permanent issue. Recipients experiencing a hard bounce are automatically added to the suppression list and will not receive further communication. The sending will not be retried.
Soft bounce — The email can’t be delivered to the recipient due to a temporary reason. The sending will be retried multiple times and the number of retry attempts can vary from receiver to receiver. Here are the potential soft bounce reasons:
The recipient's mailbox is full.
Temporary breakdowns in server functionality.
Temporary delay due to rate limits from mailbox providers
Block bounce — The email was rejected at first sending attempt and won't be subject to retry until next email to send. As a sender, if the domain/IP is blocklisted, emails sent will fall under block bounces.
Built-in data
Built-in data attributes allow you to target users based on data the SDK collects automatically. Several conditions can be set in the same campaign and with different operators (equals to, lower than, greater than, etc).
C
Campaign A push campaign or an In-App automation allows you to reach the audience of your app or website with a message.
It's a combination of:
Targeting conditions (e.g. all of your userbase or only users who match the conditions set in your campaign)
A send date or a trigger
A message (e.g. a push notification, a push notification with a landing page or an in-app message).
These are sorted by status in the "Campaigns" or "Automations" tab of the dashboard:
Draft: These campaigns have not been activated yet. You can edit and send them later.
Completed: These campaigns have been sent.
Paused: These recurring push campaigns or In-App automations have been paused.
Running: Batch is currently delivering push notifications or showing in-app messages to your audience for these campaigns.
Capping This feature allows you to limit the number of in-app messages or push campaigns sent to your users and therefore manage your communication pressure. This is useful to avoid overwhelming your users with the same message. Here's how to set it.
There are several layers of capping:
Global capping: the limitation rules will affect all your push notifications.
Campaigns capping: the limitation rules will only affect notifications coming from campaigns created on the dashboard or with the Push Campaigns API.
Transactional capping: the limitation rules will only affect real-time notifications sent with the Transactional API.
Label-based capping: you can create a frequency capping for all the notifications attached to a specific label.
Clicks
Click distribution: Refers to the distribution of clicks among all clicks.
Click rate: Unique click divided by delivered. Total clicked: Number of recipients who clicked on a link or button (redirecting to a specific page) in the e-mail. For example, If the same user clicks 4 times on the email, it will count as 4 clicks. Please note that this does not include unsubscribed link clicks.
Unique clicked: Number of recipients who clicked on a link or button (redirecting to a specific page) in the e-mail. Regardless of how many times they click, it will be counted as 1 unique click. Please note that this does not include unsubscribed link clicks.
CTA or In-App Button You can add up to 2 buttons to your in-app messages and attach a specific action to them:
Dismiss: Lets users close the in-app message and continue to navigate the app.
Deeplink: Directs users to another specific page in or outside your app.
Custom action: Executes a custom action developed on your end.
Custom Audience
Custom audiences allow you to upload static segments exported from your userbase (e.g. top 500 buyers, etc) or created by third-party tools like Tinyclues for example. You can easily retarget these custom audiences with a push or an In-App automation from the dashboard.
Custom data Batch can collect additional data to improve your targeting and send better messages to your users. There are two types of custom data you can gather:
User properties: attributes (e.g. first name, subscription date, etc), tags (e.g. list of favourite topics, list of purchased brands, etc). You can use them to segment your userbase or personalize the content of your notifications.
User actions (events): Events are useful to segment your userbase. You can also use them as a trigger for push or in-app messages.
Custom user ID Batch allows you to set a Custom User ID for every install.
This custom user identifier can be:
The unique ID you are using in your login system.
A stable ID used in your data store (e.g. Firebase, etc).
Any stable information that can help you to identify a user (e.g. hashed email address, etc).
You can use that user ID to target a specific user with the transactional API, and more.
D
DAUs
Stands for Daily Active Users. It represents the number of unique installs that opened the app at least once a day.
Debug Batch provides a simple debug tool that allows you to test your custom data integration (Settings > Debug). It shows all the data available for a specific user ID (push token, Custom User ID, native and custom data, etc).
Deeplink Also called a redirection link. It allows you to direct users to a specific page within your app.
Delivered
Number of emails delivered successfully to the mailbox provider (for example : Gmail, Outlook, iCloud mail, etc).
Delivery rate = delivered divided by sent
E
Estimated Reach
The Estimated Reach indicator shows you the approximate number of opt-in users or installs who are going to receive your message, based on your current targeting options. You can check out how it works.
G
Global time
When setting the date of your campaign, this option allows you to send a push notification to your users at a specific UTC time regardless of their location. Every user will receive the message at the same time regardless of their time zone.
Grace period The grace period allows you to set a delay between each display of the same in-app message. This feature is quite handy to avoid your user seeing the same message multiple times in a single session.
I
In-App automation In-app messages allow you to trigger messages inside your app when users open it, perform a specific action or as landing pages after opening a push notification.
This is great to communicate with users who have turned off push notifications or to show contextual messages while your users are browsing your app (e.g. special offers, update reminders, etc). We have been working on formats that neatly fit your app design, bring the same experience to all your users and allow you to interact better with them.
You will find more information here on In-App: How Do In-App automation Work?
Install 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.
Installation ID Anonymous ID generated by the SDK when users open the app for the first time.
L
Label
You can attach one or several labels to your push and In-App automations. This is useful to filter your campaigns (e.g. "onboarding campaigns") or apply a specific marketing pressure rule on them.
Local time
When setting the date of your campaign, this option lets you send a push notification that will be received based on the user's times zone; i.e at the same hour in every country. This ensures that marketing efforts target your users at a uniform time.
M
Machine Opens
Automatic opens carried out as part of the Apple Mail Privacy Protection. In that case, all emails delivered to subscribers who use the Apple Mail application with the MPP function activated are automatically counted as opened. This concerns all emails opened via the Apple Mail application on any device running the latest version of iOS and with the MPP function activated, whether they come from Gmail or a professional account.
MAPs
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.
MAUs Stands for Monthly Active Users. It designates the number of unique installs that opened the app at least once a month.
Mobile Landing Mobile Landings allow you to display an in-app message when users open your push notification. This is great to manage scenarios that require a specific action from your users (update reminders, etc) or to have all their attention (new feature announcements, exclusive offers, etc).
O
Open 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.
For emails:
Open rate: Unique open divided by delivered
Machine Opens: Automatic opens carried out as part of the Apple Mail Privacy Protection. In that case, all emails delivered to subscribers who use the Apple Mail application with the MPP function activated are automatically counted as opened. This concerns all emails opened via the Apple Mail application on any device running the latest version of iOS and with the MPP function activated, whether they come from Gmail or a professional account.
Total open: Total number of times your email was opened.
Unique open: Number of recipients who opened your email at least once. Note that machine open from Mail Privacy Protection also counts as open.
Opt-in Users who accepted to receive your notifications.
Opt-out Users who didn't turn on, refused or disabled push notifications for your app.
OS Stands for Operating System. It designated the main systems developed by Apple (iOS), Google (Android) and Microsoft (Windows Phone).
P
Push campaign This is the very first reason our users chose Batch. You can use Batch to send rich notifications using images, videos, GIFs or sounds on iOS, Android or Windows. You can also send a notification to your users' browsers. Here are some tips to create your first push campaign.
These notifications will be displayed outside of the app, on the lock screen of the device or in the notification centre.
Push certificate This is the file Batch needs in order to send a push notification to the tokens collected for your iOS app. You can use a P12 certificate or a P8 file.
Push Token Tokens are volatile IDs generated by Apple, Google or your browser's push service.
Batch collects these tokens in order to send a push notification to your users' devices:
iOS : We collect a token when a user clicks on "accept" or "refuse" on the push authorization request. It's displayed the first time the app is opened, so 100% of users see it.
Android: Same behaviour as iOS for Android 13 and above. For version 12 and below, users are opt-in by default.
R
Reengaged users Dormant users who received a notification, opened it and then came back to the app/website in the 3 days following the reception of the notification.
REST API key It identifies your account and gives you access to our APIs. You can find it in Settings > General.
S
SDK Stands for Software Development Kit. This is the library you need to integrate into your app to get Batch up and running. Batch SDK takes care of collecting data on the installs (e.g. push token collection, custom data, etc), sending analytics (e.g. push open, etc) and displaying In-App messages.
SDK API key The SDK API key identifies your app on Batch dashboard. It's included in the code of your app and used when the SDK starts. You can find it in Settings > General.
Seat
The number of accesses to the dashboard. They depend on the plan you picked.
Sent
Number of push, email or SMS sent to the recipients.
Regarding email, this can include delivered, deleted and bounced emails. It means that a request to send an email has been forwarded to the delivery provider, indicating the initiation of the delivery process. Yet, it doesn't ensure successful delivery due to external factors that can influence final receipt such as invalid address. Sending — Period during which emails are in sending. This metric evolves as the campaign is sending and decreases at the end of the campaign.
Skipped due to suppression
Number of email address we tried to send an email to but the email address is suppressed due to previous hard bounce or if a user previously marked any email as spam.
Smart Segments Smart Segments are automatically generated by Batch from the moment the SDK is implemented in your app.
They allow you to take action on your userbase in a meaningful manner, based on their engagement level:
New users: Users who just downloaded your app or visited your website for the first time. They can stay in that segment for up to 15 days after the installation.
Engaged users: Users of the Engaged segment are your regular users. They open your app frequently, enjoy it the way it is and know exactly why they're using it. For all these reasons, they are the most receptive users you have and you want to keep them engaged.
Dormant users: Dormant users were 'engaged' at one point, but have not launched your app for a long time. They're basically not using it any more, but they still remember it and probably why they installed it.
One-time users: Users who downloaded the app and opened it once but never came back since.
SMS
Stands for Short Message Service. Technology for sending short text messages between cell phones or compatible devices. One SMS includes parts depending on character encoding. The billing unit for SMS is the number of parts included. Please follow this documentation to understand how to calculate the size of an SMS.
Start 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.
T
Tagging plan The tagging plan is a document you usually elaborate on during the integration of the SDK. It's the list of all the custom data you want to collect with Batch, in order to segment your userbase properly.
Targeting The targeting is the set of conditions added to your push or In-App automation that will allow Batch to select the users who should see the message you are editing. You can base your targeting on built-in data (e.g. installation date, country, language, etc) and on custom data (e.g. any other data existing in your app to reach the correct audience).
Segmentation is slightly different on web push, read this article to learn more.
Themes Batch in-app messages are highly customizable. You can tailor the overall layout of the in-app message, colors, image and button by creating a theme in Settings > Themes.
There are four formats you can choose from:
Fullscreen
Banner
Modal
Image
Trigger Action required to display an in-app message to your users. You can choose to trigger your in-app message as soon as users will open your app (As Soon As Possible), in a new session (New Session) or based on a custom event tagged in your app.
Trigger analytics
Targeting mismatch: all the users who had initially entered the journey and who no longer match the targeting at the time of the trigger (for example, the user is no longer premium at the time of the push, but 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 of the users that Batch could not address because they do not have valid tokens (if they uninstalled the app, for example).
TTL Stands for Time To Live and designates an expiration delay for your campaign, meaning that it won't be displayed if the device didn't receive the notification within this time. By default, Batch sets a TTL of 14 days for all of the notifications you send, but you're free to change it: here's how.
U
Uninstall Deletion of the app on a user's device.
Unsubscribed
Number of recipients who opted-out by clicking on the Unsubscribe link which allows Batch to get instant opt-out feedback and to not retarget recipients who have chosen to unsubscribe.
Unsubscribe links — the line that mentions unsubscribe links is not included in the calculation of total clicks.
Last updated
Was this helpful?