> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/other/glossary.md).

# Glossary

This glossary defines key terms used in Batch.\
Expand the letters to display definitions and key information:

<details>

<summary>A</summary>

**A/B Testing**

A/B testing is a method of experimentation used to **compare two versions** (or more) of an element, such as an app screen, a notification, an email, to determine which one performs better according to a defined goal (e.g., click-through rate, conversion rate, engagement, etc.).

It involves randomly showing **two variants or more** (for example version **A** and version **B**) of the same element to different groups of users, then measuring performance using key metrics (KPIs).

A/B testing is key to optimize performance and improve open and re-engagement rates using **data-driven decisions** rather than assumptions or intuition.

{% hint style="info" %}
In Batch:

* In **Campaigns** and **Recurring Automations**, A/B testing is set at the message level. You can enable **Automatic Winner Selection** to test the variants on part of your audience and automatically send the best-performing one to the rest.
* In **Trigger Automations**, A/B testing is done with a **Random Split** step (2 to 4 branches).
  {% endhint %}

***

**AI Assist**

Set of AI agents embedded in the Batch platform that help CRM teams create, analyze, and optimize campaigns (content, targeting, journeys), improving productivity and execution quality.

***

**AI Decide**

Set of autonomous decisioning capabilities that use AI to orchestrate campaigns and journeys based on business objectives (e.g. revenue, conversion, retention), by selecting the best actions, timing, and channels without manual intervention.

***

**AI Predict**

Set of predictive scores that analyze customer data to anticipate behaviors (e.g. purchase, churn, engagement) and enable better targeting, personalization, and decision-making across campaigns.

***

**APIs**

Batch APIs let you send data to Batch, manage your audiences and catalogs, send messages and retrieve your data and analytics from your own systems. They are project-level APIs: each call requires your **REST API key** and your **Project key**. Learn more in the [API documentation](https://doc.batch.com/developer/api/cep).

{% hint style="info" %}
**Profile API**\
Allows you to create and update profiles: identifiers, native attributes (email address, phone number, subscriptions, language, region, etc.), custom attributes and events. Events sent with the Profile API can be used to trigger automations (e.g. a transactional message sent when an order is confirmed in your back-end). The Profile API also lets you request exports of profile data (attributes, events, reachability).

**Campaigns API**\
Allows you to create and update Campaigns remotely, from your own CMS or back-office for example.

**Orchestrations API**\
Allows you to list your orchestrations (Campaigns, Recurring, Trigger and In-App Automations) and retrieve their analytics.

**Audiences API**\
Allows you to create, update, replace and delete Audiences: lists of Custom IDs, email addresses or Installation IDs, with optional attributes for personalization.

**Catalogs API**\
Allows you to create and maintain Catalogs (e.g. products, articles, offers) to use non-user-centric data in your messages.

**Segments API**\
Allows you to list the Segments of your project.

**Exports API**\
Allows you to list, check the status of, and download the exports you requested.

**GDPR API**\
Lets you make requests to fetch and/or delete user data from our database.
{% endhint %}

***

**Attributes**

Data stored on a profile. There are two types of attributes:

* **Native attributes** are managed by Batch and prefixed with `$` (e.g. email address, phone number, language, region, timezone, last visit, email/SMS marketing subscription).
* **Custom attributes** are the data you send to Batch via the SDKs, the Profile API or Cloud Sync (e.g. first name, loyalty tier, subscription end date). They can be strings, numbers, booleans, dates, URLs or arrays.

Attributes can be used for targeting and personalization. New custom attributes must be confirmed in **Data > Profile data** before they can be used in orchestrations.

***

**Audience**

An Audience is a static list of **Custom IDs, email addresses** or **Installation IDs** you import into Batch to target or exclude specific users *(e.g. top 500 buyers, a list exported from your CRM or a third-party tool)*.

Audiences can be uploaded from **Data > Audiences** (CSV or TXT file, with up to 10 optional attributes for personalization), sent with the Audiences API, or imported automatically with the Audience Importer (on request). Learn more in [Audiences](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/audiences).

{% hint style="warning" %}
Uploading a file of email addresses creates an Audience only: it does not create or update profiles. Only email addresses already linked to a profile can be targeted.
{% endhint %}

***

**Automation**

Automations are multi-step, rule-based orchestrations that automatically send **personalized, event-based** or **recurring messages** to users, guiding them through key moments of their lifecycle with your app and/or website.

They allow you to orchestrate user engagement without human intervention, by triggering communication when a user performs a specific action or reaches a defined stage.

{% hint style="info" %}
**Different types of automations**

* **Trigger Automations**
  * Launch automatically when a specific event occurs or an attribute changes: for example, when a user opens the app, adds a product to their cart, or becomes a premium customer.
  * They enable **contextual messaging** based on user behavior.
* **Recurring Automations**
  * Run on a **scheduled basis** (daily, weekly, annually etc.) according to the profile's local time or UTC.
  * Useful for ongoing campaigns like daily tips, weekly summaries, birthdays or loyalty updates.
* **In-App Automations**
  * **Displayed inside your app** when a user opens your app or performs a specific action in your app (for example tapping a button or browsing a page).
  * Let you reach users exactly when they're active inside your app: no need for push permissions.
    {% endhint %}

***

**Automation Builder**

The Automation Builder is the canvas to **design multi-step, multi-channel Trigger Automations.**

It lets you build customer journeys that start on events or attribute changes, add message steps (Push, Email, SMS, Universal Channel), branch audiences (Yes/No, Random), and schedule delays ("Wait for," "Wait until," or "Wait until date attribute"). You can also set targeting, capping, grace period, quiet times, and start/end dates.

The Builder view includes contextual analytics like step metrics and user path stats. Learn more in [Trigger Automations](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/trigger-automations).

</details>

<details>

<summary>B</summary>

**Bounce**

Bounces refer to an unsuccessful delivery attempt. In fact, bounces mean that the email couldn't reach the intended recipient for various reasons.

{% hint style="success" %}
**Different types of bounces**

* **Hard bounce:** These emails were undeliverable because the email address is invalid or is now disabled by the mailbox provider. The email cannot be delivered to the recipient due to a permanent issue. Recipients experiencing a hard bounce are automatically added to the transactional and marketing suppression list and will not receive further communication.
* **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 recipient's mail server rejects the email because your domain or IP is blocklisted due to reputation issues.
  {% endhint %}

Bounces also exist on Push and SMS (e.g. invalid token or phone number). Bounced messages can be used in retargeting.

***

**Built-in data**

Data automatically collected or computed by Batch on your profiles (e.g. language, region, last visit, app installation, push opt-in, has custom ID), as well as the engagement events Batch tracks on your messages (sent, delivered, opened, clicked, bounced, dismissed). Built-in data can be combined with your custom data in your targeting conditions, with different operators *(equals to, lower than, greater than, etc)*.

</details>

<details>

<summary>C</summary>

**Campaign**\
A Campaign is a one-shot orchestration that sends a message (Push, Email or SMS) to a targeted audience at a given time.

{% hint style="info" %}
It's a combination of:

* **Targeting conditions** (e.g. all of your profiles or only those who match the conditions or segments set in your campaign)
* A **send date** (now or scheduled)
* A **message** (e.g. a push notification, a push notification with a mobile landing, an email or an SMS).
  {% endhint %}

Campaigns and Automations are sorted by status in the **Campaigns** and **Automations** listings of the dashboard:

* **Draft**: The orchestration has not been launched yet. You can edit it and launch it later.
* **Planned**: The orchestration is scheduled and will start at its send date.
* **Running**: Batch is currently sending messages for this orchestration.
* **Stopped**: The orchestration has been stopped. It can be edited and launched again.
* **Completed**: The orchestration is over and all messages have been sent.

Learn more in [Campaigns](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/campaigns).

***

**Capping**\
Capping allows you to limit the number of messages your users receive and therefore manage your marketing pressure. This is useful to avoid overwhelming your users with the same message or too many messages.

{% hint style="info" %}
There are several layers of capping:

* **Label-based capping**: set in **Settings > Cappings**, it limits the number of messages a profile can receive from all the orchestrations attached to a specific label, across all channels (email, SMS, push), over the last X hours/days. [Here's how to set it](https://doc.batch.com/guides-and-best-practices/orchestration/how-to-cap-the-number-of-themed-communications-received-by-a-user).
* **Automation capping**: limits the number of times a profile can enter a Trigger Automation.
* **In-App capping**: limits the number of times an In-App message can be displayed to a profile.
  {% endhint %}

Learn more in [Cappings](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/cappings).

***

**Catalog**

Catalogs are collections of **non-user-centric data** (e.g. product catalogs, media articles, store lists). Each item of a catalog has an ID and attributes you can reference in your messages to power advanced personalization scenarios, such as abandoned cart, product recommendations or new arrivals.

Catalogs are fed with the Catalogs API or with Cloud Sync. Learn more in [Catalogs](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/catalogs).

***

**Clicks**

{% hint style="info" %}
**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.
{% endhint %}

***

**Cloud Sync**

Cloud Sync connects Batch to your data warehouse or database (e.g. BigQuery, Snowflake, Redshift, Databricks, SFTP) to automatically keep your **profile attributes**, **profile events** and **catalogs** up to date in Batch, without any API development. Cloud Sync is a paid offering: contact your Customer Success Manager or Account Manager for more details. Learn more in [Cloud Sync](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/cloud-sync).

***

**Control Group**

A percentage of the targeted audience of a Campaign (up to 20%) that is randomly held back from receiving the message. Comparing the conversions of this group with the conversions of the profiles who received the message lets you measure the **incremental impact** of your campaign. Learn more in [Messages](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/overview).

***

**Conversion Goal**

A Conversion Goal measures how many profiles perform a specific event (e.g. a purchase or a subscription) within a defined time window after receiving, opening or clicking a message. You can also track a business value (e.g. revenue) linked to these events. Conversion and revenue metrics are displayed in the orchestration analytics. Learn more in [Orchestration analytics](https://doc.batch.com/getting-started/features/customer-engagement-platform/analytics/orchestration-analytics).

***

**CTA or In-App Button**\
Buttons (and images) in your In-App messages and Mobile Landings can be attached to an action, for example:

* **Dismiss**: Lets users close the message and continue to navigate the app.
* **Deeplink**: Directs users to another specific page in or outside your app.
* **Other actions** such as asking for an app rating, a push re-opt-in or copying a text to the clipboard.

Clicks on buttons can be used in retargeting.

***

**Custom data**\
Batch can collect your own data to improve your targeting and send better messages to your users. There are two types of custom data:

* **Attributes**: profile properties (e.g. first name, subscription date, list of favourite topics, etc). You can use them to segment your profiles or personalize the content of your messages.
* **Events**: user actions (e.g. add to cart, purchase). You can use them in your targeting and as triggers for your automations and In-App messages. Events can carry their own attributes (e.g. product name, price).

Custom data can be sent with the SDKs, the Profile API or Cloud Sync.

***

**Custom ID (Custom User ID)**\
The Custom ID is your own unique identifier for a user, set with the SDKs or the Profile API. It's the key Batch uses to **build a single profile** from all the data received from your apps, websites and back-end.

{% hint style="info" %}
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. CRM, CDP, etc).
* Any stable information that can help you to identify a user (e.g. hashed email address, etc).
  {% endhint %}

Make sure each Custom ID belongs to one single user. Learn more about the [Custom User ID](https://doc.batch.com/developer/sdk/ios/profile-data/custom-user-id).

</details>

<details>

<summary>D</summary>

**Daily Active Profiles**

The number of distinct profiles that started the Batch SDK at least once on a given day (iOS, Android or Website). A profile starting several times on the same day is only counted once. Available in **Analytics > Profiles**, in the Activity section. Learn more in [Profile Analytics](https://doc.batch.com/getting-started/features/customer-engagement-platform/analytics/profile-analytics).

***

**Deeplink**\
Also called a redirection link. It allows you to direct users to a specific page within your app or website.

***

**Deliverability**

Email deliverability involves a variety of practices designed to ensure that emails reach recipients' inboxes without being rejected or marked as spam.

{% hint style="info" %}
In other words:

* It is not just sending an email, but making sure it lands in the **actual inbox** (not the spam/junk folder or blocked entirely).
* It depends on factors like sender reputation, authentication, list hygiene, volume/frequency, etc.
  {% endhint %}

***

**Delivered**

Number of emails delivered successfully to the mailbox provider (for example : Gmail, Outlook, iCloud mail, etc).

{% hint style="info" %}
**Delivery rate** = delivered divided by sent
{% endhint %}

</details>

<details>

<summary>E</summary>

**Estimated Reach**

The Estimated Reach indicator shows you the approximate number of profiles who are going to receive your message, based on your current targeting options. You can check out [how it works](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/targeting#estimated-reach).

***

**Event**

An action performed by a user and sent to Batch (e.g. `add_to_cart`, `purchase`), with optional attributes. Events can be tracked with the SDKs, the Profile API or Cloud Sync. They are used to trigger automations and In-App messages, in targeting conditions and as conversion goals.

</details>

<details>

<summary>G</summary>

**Grace period**\
The grace period sets a minimum delay between two sends or displays of the same message to a profile. It's available on Trigger Automations (up to 60 days) and on In-App Automations, where it avoids users seeing the same message multiple times in a single session.

</details>

<details>

<summary>I</summary>

**In-App automation**\
In-App messages are displayed inside your app when users open it or perform a specific action. They are created in **Automations**, using the In-App channel.

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)*. In-App messages are built with a block-based composer (images, text, buttons, columns, etc.) and can be saved as reusable templates.

You can choose 1 to 10 trigger events (or the native **New session** event), add a display delay, and set a capping and a grace period. Learn more in [In-App Automations](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/in-app-automations).

***

**In-App Template**\
A reusable blueprint for the structure and styling of your In-App messages (type and position of the blocks, colors, margins, sizes, etc.). Templates don't include the message content (texts, images, button actions).

You can manage your templates in **Content > In-App Templates**, or save one directly from the message composer. Pre-built Batch templates are also available as a starting point. Learn more in [In-App Templates](https://doc.batch.com/getting-started/features/customer-engagement-platform/content/in-app-templates).

***

**Install**\
Designates an installation of your app including Batch SDK, or a browser on which your website including Batch Web SDK has been visited. A reinstall of your app is considered a new install. A profile can have several installs (e.g. a smartphone, a tablet and a browser).

The daily number of **new installs** of your iOS and Android apps is available in **Analytics > Profiles**, in the Activity section. An install is counted the first time Batch detects a new app installation, whether or not the user has enabled push notifications.

***

**Installation ID**\
Anonymous ID generated by the SDK when users open the app (or visit your website) for the first time. It changes when the app is reinstalled.

</details>

<details>

<summary>L</summary>

**Label**

Labels can be attached to all your orchestrations (Campaigns and Automations), whatever the channel. They are useful to filter your orchestrations (e.g. "onboarding"), to analyze performance by theme and to apply a specific marketing pressure rule on them (label-based capping).

Labels are created in **Settings > Labels** (up to 200 per project). Learn more in [Labels](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/labels).

***

**Landing Pages & Forms**

Web pages hosted by Batch, created from the dashboard, that you can link to from your messages (e.g. a preference center, a subscription form or an event page). Learn more in [Landing Pages & Forms](https://doc.batch.com/getting-started/features/customer-engagement-platform/content/landing-pages-and-forms).

***

**Lift**

A measure of how much better predictive targeting performs versus random targeting. A lift of 3 means that customers selected via the predictive score convert 3× more than customers picked at random.

</details>

<details>

<summary>M</summary>

**Machine Opens**

Automatic opens carried out as part of the [Apple Mail Privacy Protection](https://www.apple.com/legal/privacy/data/en/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.

***

**Machine Learning (ML)**

A family of AI techniques in which an algorithm learns patterns from historical data, without being explicitly programmed.

***

**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, Cloud Sync, email opens or clicks (whether users connect to the app/website, or send updated data for a given profile).

Find more details about [activity on a profile](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/data-lifecycle#what-is-an-inactive-profile) :point\_left:

***

**Mobile Landing**\
Mobile Landings allow you to display an in-app message when users open your push notification (select **Show Mobile Landing** as the push redirection). 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)*.

***

**Model**

A model is an algorithm trained on a specific customer's data to produce predictions. A model must first be **trained** and then **applied** to generate AI Predict scores on profiles.

***

**Model training**

The process by which Batch AI Predict learns behavioral patterns from your historical customer data in order to generate predictions. Training runs automatically in the background: no action is required from your team. Once complete, the model is applied to your current customer base to produce scores, which are then pushed to your Batch profiles.<br>

</details>

<details>

<summary>O</summary>

**Open**\
Interaction of a user with a push notification or an email.

{% hint style="info" %}
For push notifications, Batch measures 2 types of opens:

* **Direct opens**: users who opened your app by tapping the notification.
* **Influenced opens**: users who received a notification and opened your app within the next 3 hours.

**Open rate** for push = opens divided by sent opt-in.
{% endhint %}

{% hint style="warning" %}
For emails:

* **Open rate:** Unique open divided by delivered
* **Machine Opens:** Automatic opens carried out as part of the [Apple Mail Privacy Protection](https://www.apple.com/legal/privacy/data/en/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.
  {% endhint %}

***

**Opt-in**\
Users who agreed to receive your messages on a channel: users who accepted push notifications on their device or browser, or profiles subscribed to your marketing emails or SMS.

***

**Opt-out**\
Users who didn't turn on, refused or disabled push notifications, or who unsubscribed from your marketing emails or SMS.

***

**Orchestrations**\
Orchestrations are workflows that let you choose when and how you send messages with full control over targeting, timing, marketing-pressure rules and personalization.

{% hint style="info" %}
**Different types of Orchestrations**

* Campaigns
* Recurring Automations
* Trigger Automations
* In-App Automations
  {% endhint %}

***

**OS**\
Stands for Operating System. It designates the main systems developed by Apple (iOS) and Google (Android).

</details>

<details>

<summary>P</summary>

**Payload**\
Payload refers to the data structure that carries the content and parameters of a message or request sent through Batch, such as a Push Notification or an API call.\
It defines **what** is sent, **to whom**, and **how** it should be displayed or processed.

For push notifications, you can also add a **custom payload** (key/value data in JSON) to pass additional information to your app.

***

**Personalization**

Dynamic content inserted in your messages to adapt them to each profile, using profile attributes, trigger event attributes, audience attributes or catalog items (e.g. `{{ first_name }}`). Learn more in [Personalization](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/personalization).

***

**Profile**

A profile centralizes all the data and events of a user coming from your apps, websites, APIs and Cloud Sync, based on their **Custom ID**. It also stores their email address, phone number and subscriptions (push, email, SMS). Profiles can be anonymous (not identified with a Custom ID yet) or identified.

This allows you to message a user on any channel, whatever the source of their data. Learn more in [Profiles](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/overview).

***

**Profile view**

The page of the dashboard that displays all the data of a profile: attributes, events, subscriptions and message history, whatever the source (SDK, API, Cloud Sync). You can find a profile in **Profiles > Search profiles** with a Custom ID, an Installation ID or an email address. It's the best place to check that your data is correctly received by Batch. [Here's how to find a profile](https://doc.batch.com/guides-and-best-practices/profiles/how-to-find-a-users-profile-on-the-dashboard).

***

**Profile's local time**

When scheduling a Campaign or a Recurring Automation, this option sends your message at the same hour in every timezone, based on the profile's local time. A Campaign sent in Profile's local time can take up to 25 hours to complete.

***

**Project**

A project groups your Android and iOS apps, websites and all your channels (Push, In-App, Email, SMS) in a single entity, with a unified base of profiles. You can switch between projects with the project selector, in the upper-left corner of the dashboard.

***

**Project key**\
The Project key identifies your project. It's required, along with the REST API key, to call Batch APIs. You can find it in **Settings > General**.

***

**Propensity score**

A numeric value between 0 and 1 attached to a customer profile, representing the probability that a customer will perform a specific action, such as purchasing a product, churning, or responding to a promotion. The closer the score is to 1, the higher the likelihood. Propensity scores are computed by Batch AI Predict from historical customer data and are available as profile attributes, ready to use in segmentation and personalization.

***

**Push notification**\
Push notifications are messages displayed outside of your app or website: on the lock screen of the device, in the notification centre or in the browser. You can send rich notifications using images or GIFs on iOS, Android and the Web. Learn more in [Push](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/push).

***

**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.

</details>

<details>

<summary>Q</summary>

**Quiet times**

Time slots (Quiet hours) and/or days (Quiet days) during which profiles won't receive messages from a Trigger Automation, based on the profile's local time. Messages that should be sent during a quiet time can either be sent at the next available time or skipped.

</details>

<details>

<summary>R</summary>

**Random Split**

A Trigger Automation step that randomly splits profiles into 2 to 4 branches, to A/B test different messages or journeys.

***

**REST API key**\
It identifies your account and gives you access to our APIs. You can find it in **Settings > General**. Only users with the right permissions can see it.

***

**Retargeting**

Targeting profiles based on how they reacted to your previous messages: sent, delivered, opened, clicked, bounced or dismissed. You can retarget a specific orchestration (or step), a channel or a label. Retargeting is available in targeting, Yes/No splits, wait steps and segments. Learn more in [Targeting](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/targeting).

***

**Rolling Active Profiles**

The number of distinct profiles that started the Batch SDK at least once over the preceding 30 days (rolling window, recomputed daily), across iOS, Android and Website. Available in **Analytics > Profiles**, in the Activity section.

{% hint style="info" %}
Not to be confused with MAPs: Rolling Active Profiles only count SDK starts in your apps and website, while MAPs count any activity recorded on a profile (SDK, APIs, Cloud Sync, email opens…).
{% endhint %}

</details>

<details>

<summary>S</summary>

**Score (Predictive Score)**

An attribute attached to a customer profile, produced by an ML model. Depending on the model, a score can be a probability between 0 and 1 (a propensity score), a monetary amount (e.g. predicted LTV), an estimated date, or a list of recommended product IDs (top-N recommendation).

***

**Score refresh**

The automatic recalculation of predictive scores at a regular cadence, ensuring that profile attributes stay up to date as customer behavior evolves. When a score is refreshed, the updated values are pushed directly to Batch profiles and immediately reflected in any segments, automations, or personalizations that use them.

***

**SDK**\
Stands for Software Development Kit. This is the library you need to integrate into your app or website to get Batch up and running. Batch SDK takes care of identifying users, collecting data (e.g. push token, attributes, events), sending analytics (e.g. push open, etc) and displaying In-App messages.

***

**SDK API key**\
The SDK API key identifies your app or website on Batch. 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.

***

**Segment**

A Segment is a **dynamic** group of profiles defined by targeting rules (attributes, events, retargeting, audiences, etc.), automatically updated as your data evolves *(e.g. "Users active in the last 7 days", "Premium subscribers")*. Segments are created in **Data > Segments** and can be reused in all your orchestrations. Learn more in [Segments](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/segments).

***

**Send rate**

The maximum number of messages sent per hour for a Push or Email Campaign or Recurring Automation. It lets you spread the sends over time, for example to avoid overloading your servers after a push.

***

**Sent**

Number of push, email or SMS sent to the recipients.

{% hint style="info" %}
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.

Regarding push, **Sent opt-in** is the number of notifications sent to opt-in devices. It's used to calculate the push open rate.
{% endhint %}

***

**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.

***

**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](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/sms#sms-parts-and-encoding) to understand how to calculate the size of an SMS.

***

**Start**\
A start of the Batch SDK, recorded every time a user opens your app or visits your website (silent starts excluded). Unlike Daily Active Profiles, starts are not deduplicated: a profile opening the app several times a day counts once per start. The Starts / Daily Active Profiles ratio helps you measure the average number of sessions per active profile. Available in **Analytics > Profiles**, in the Activity section.

***

**Subscription status (Email / SMS)**

The marketing consent of a profile for a channel:

* **Subscribed**: the profile accepted to receive marketing messages. You can send them marketing and transactional messages.
* **Unsubscribed**: the profile opted out of marketing messages (e.g. via an unsubscribe link or a STOP reply). You can send them transactional messages only.
* **Never subscribed**: the profile shared an email address or phone number but never subscribed to marketing messages. You can send them transactional messages only.

***

**Suppression list**

List of email addresses Batch won't send emails to, because of a previous hard bounce or a spam complaint.

</details>

<details>

<summary>T</summary>

**Tagging plan**\
The tagging plan is a document that you usually elaborate during the integration of the SDK. It's the list of all the custom data (attributes and events) you want to send to Batch, in order to target and personalize your messages properly. [Here's how to create one](https://doc.batch.com/developer/technical-guides/how-to-guides/how-to-create-a-tagging-plan).

***

**Targeting**\
The targeting is the set of conditions added to your orchestration that will allow Batch to select the profiles who should receive the message you are editing. You can base your targeting on built-in data (e.g. language, region, last visit, etc), custom data (attributes and events), retargeting, segments and audiences. Learn more in [Targeting](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/targeting).

***

**Token (push token)**\
Tokens are volatile IDs generated by Apple, Google or your browser's push service.

{% hint style="info" %}
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.
  {% endhint %}

***

**Topic preferences**

Thematic subscription preferences stored on a profile (e.g. "newsletter", "promotions"), using the `$topic_preferences` native attribute. They can be sent with the SDKs or the Profile API and used in your targeting.

***

**Transactional message**

A message triggered by an individual action or a service need (e.g. order confirmation, password reset), as opposed to marketing messages. Transactional emails and SMS can be sent to profiles who are not subscribed to marketing messages. Transactional messages are usually sent with Trigger Automations, triggered by events sent with the Profile API.

***

**Trigger**\
The event (or attribute change) that starts a Trigger Automation or displays an In-App message. For In-App messages, you can use the native **New session** event or 1 to 10 custom events tracked in your app via the SDK.

***

**TTL**\
Stands for Time To Live and designates an expiration delay for your push notification, 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 : you can check our [Push documentation](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/push#expiration-ttl) for more details.

</details>

<details>

<summary>U</summary>

**Uninstall**\
Deletion of the app on a user's device. Batch detects an uninstall when Apple (APNs) or Google (FCM) reports it after a push delivery attempt. The daily number of uninstalls of your iOS and Android apps is available in **Analytics > Profiles**, in the Activity section.

***

**Universal Channel**

An automation channel that lets you call any third-party API (webhook) from a Trigger Automation step, for example to send a message through an external provider or update data in another tool. Universal Channel is a paid offering: contact your Customer Success Manager or Account Manager for more details. Learn more in [Universal Channel](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/universal-channel).

***

**Universal time (UTC)**

When scheduling a Campaign or a Recurring Automation, this option sends your message at a specific UTC time regardless of the profiles' location. Every user receives the message at the same time, whatever their timezone.

***

**Unsubscribed**

Number of recipients who opted-out by clicking on the [Unsubscribe link](https://doc.batch.com/guides-and-best-practices/message/email/link-and-tracking-settings/how-to-add-an-unsubscribe-link-to-your-email-template-1) which allows Batch to get instant opt-out feedback and to not retarget recipients who have chosen to unsubscribe.

{% hint style="info" %}
**Unsubscribe links** — the line that mentions unsubscribe links is not included in the calculation of total clicks.
{% endhint %}

</details>

<details>

<summary>Y</summary>

**Yes/No Split**

A Trigger Automation step that splits profiles into two branches depending on whether they match a condition (e.g. an attribute, an event or a reaction to a previous message).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/getting-started/other/glossary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
