First, open your account's menu located on the top right corner of the dashboard (in Batch Customer Engagement Platform) or the bottom left corner (in Batch Mobile Engagement Platform).

Click 'Manage team', then click 'Invite user':

Then, pick the right permissions for the new team member and select the apps they will be able to see the dashboard:

There are several permissions you can grant or revoke:

• Administrate: Grants full access to company account (team members, users permissions, etc). Note: an account can have more than one Administrator.

• Review: Grants read-only access to the dashboard. Review users will not be able to create or edit campaigns.

• App: Grants users' rights to create, edit, and archive apps.

• Campaign: Grants users rights to create, edit and delete campaigns.

• Privacy: Grants users' rights to manage GDPR settings.

Managing Existing Users

Adding/removing existing users

You can resend invites, delete and manage existing users from the Account Manager too:

Setting app-level permissions

To facilitate collaborative work, a user with 'Administrate' rights can also grant another user access to a group of selected apps. This is handy to ensure specific users cannot access certain apps on the dashboard or if you have multiple projects with separate teams working on each one.

Setting a country/language restriction

In addition to app-level permissions, you can restrict the rights of existing users to make sure they can only create push campaigns or In-App automations for users living in specific countries.

This is useful to avoid targeting mistakes if an international team is working on the same app on Batch dashboard (e.g. editors sending a notification to all your users by forgetting to target a specific country). Here is what the campaign editor looks like for a user who can only send notifications to Canada, in French or English:

On Batch dashboard, users with a country/language restriction (e.g. Canada + English/French) will exclusively see in their campaign list:

• Campaigns matching their country/language restriction (e.g. Canada + English/French)

• Campaigns that don't include any country/language targeting (e.g. templates).

You can simply attach up to 3 labels to a campaign via the Associate labels button.

Labels have two main purposes:

• Marketing pressure limit: You can set a specific marketing pressure limit on all the campaigns attached to the same label (e.g. no more than 1 push a week for all campaigns using the "onboarding campaigns" label).

• Filtering: You can filter your campaigns list based on the labels attached to your campaigns (e.g. "onboarding campaigns"):

In case you are using Batch's APIs, you can also attach one or several labels to a campaign created from the Campaigns API or to notifications sent from the Transactional API.

The profile view page will present all data associated with a profile, including:

• Attributes: Display various profile characteristics and preferences.

• History: Show a history of profile actions, sent messages and interactions.

• Subscriptions: List any subscriptions or opt-ins associated with the profile.

This centralized view provides a complete picture of the user's data, enabling efficient profile management and analysis.

History

Profile actions

All events tracked by a profile apps or websites via Batch SDKs methods are displayed on the Profile view, as well as events sent via API.

Message events

Message events are events related to messages sent by Batch.

The following events are tracked:

• Sent: for Email, Push v2, SMS

• Sent opt-in: for Push v2

• Delivered: for Email , SMS, Mobile Landing and In-App

• Open: for Email, Push v2.

• Machine open: for Email

• Click: for Email

• Bounces: for Email

• Suppressed: for Email, when an email adress is in the suppression list

• Dismissed: for Mobile Landing and In-App

Account administrators can require new and existing teammates to use two-factor authentication (2FA) when they sign into Batch.

Reset API Key

Account administrators can reset the API key if needed, for example if it leaked in a chat conversation, by mistake. All services leveraging Batch APIs will have to get the new key after the reset.

Project-level Permissions

To facilitate collaborative work, a user with "Administrate" rights can grant another user access to specific projects. This is useful if you want to make sure specific users cannot access all the project on the dashboard.

The user will have the same permissions on all the assigned projects.

Troubleshooting

I didn't receive my invite

Here are some suggestions to find the issue:

1. Check your spam folder and look for an email sent by hello@batch.com.

2. Resend the invite: Ask the administrator of Batch account to double-check the email address they used or resend the invite.

3. Validation link: If none of the above work, your manager can send you the confirmation link he will see after inviting you.

I Get "[Email Address] Is Already Registered On Batch.Com"

If one of your teammates already has a Batch account registered with his email address, he needs to contact our support team (support@batch.com) with the following information:

• Email address of his first account.

• Email address of the team he wants to join.

We will add him to your team with all the apps he created with his previous account.

Can I Manage Several Accounts With The Same Email Address?

You cannot manage more than one account with the same email address.

If you have a Gmail account or use Google Apps, you can add a "+" at the end of your username to benefit from dynamic alias (e.g. andrew+secondaccount@gmail.com).

How Can I Delete My Account?

Just ask us to delete your account at support@batch.com. Our team will let you know when it's done.

You can create a frequency capping for all the orchestrations attached to a specific labels. It works for orchestrations created via the Dashboard or Batch's APIs.

Batch dynamically checks the number of messages across all channels (email, SMS, push) that have been sent in the last X hours/days to see if the message has to be sent or not.

If you send a multiplatform push message, it counts as one sending even if the person might receive the push on several devices.

Important note: Messages sent very closely or at the same time may not be taken into account by the capping feature.

Global Capping

You can either define a simple limit that will be applied to all the notifications you send or fine-tune your global frequency capping:

• All push notifications: The capping rules affects all your push notifications.

• Orchestrations: The capping rules only affects notifications coming from campaigns and automations created on the dashboard or with the Campaign API.

• Transactional: The capping rules only affects notifications sent with the Transactional API.

• In-app messages: This capping rules only affects In-app messages. It can be setup by session or interval of time.

All these rules can work together. For example, you can set a global capping of 5 push notifications per day and create two additional rules that will ensure users won't receive more than 1 transactional push every 2 hours and 1 push from a marketing campaign per week.

Capping analytics

You can see the number of messages that were not delivered because users already reached the limit defined in your dashboard settings. The corresponding metric is called "Skipped".

• It is in CSV format.

• Its name contains the extract date and the Segment name.

• It contains the list of profiles in the Segment at the time of export, with the following information on each profile: Custom ID, Profile ID, phone number and email (when information is available for user).

• Profiles that have neither install nor custom ID are not exported.

There are 4 metrics you should check to see how your app is performing:

Installs

Total number of installs of your app since you released it with Batch SDK. This number includes users who still have your app on their device or who already uninstalled it.

Opt-ins

This is the percentage of users who have opted-in to push notifications in your app or website.

Number of tokens

Appears on hover on "Opt-ins". The interpretation of this metric differs from an OS to another:

Android

On Android, Batch retrieves automatically the token of your new users. Users who have a token are users who still have your app on their device.

iOS

On iOS, the token collection can depend on the background refresh. You can go in Xcode and see if "Remote notifications" is checked as a background mode in your app's Capabilities to see if it's enabled.

• If enabled: Batch collects tokens for all your users, even for those who choose not to receive push notifications. In this case, users who have a token are also users who have your app on their device.

• If disabled: Batch only collects tokens for users who opt-in for push notifications. In this case, users who don't have a token are users who didn't accept notifications or uninstalled your app.

Please note that users can disable background refresh for your application so these stats may be imprecise.

Smart Segments

Understanding smart segmentation

Smart Segments are automatically created by Batch using a proprietary algorithm. They let you visualize precisely who is using your app, and who is not, who is buying your product, and who is churning away.

Our algorithm analyses the sessions of your users from the moment they install your app and put them in 4 different segments. Here is a short definition of every segment:

• New: Newcomers to your app that haven't yet established themselves as engaged, lasting users.

• Engaged: Congratulations! These users are actively using your app.

• Dormant: These promising users haven't used your app in a while. Reengage them!

• One-time: Users that have had your app for a while but have only opened it once.

We are also showing the predictive and intermediate Smart Segments that our algorithm calculates:

• Risky Engaged: Users with a high risk of becoming dormant in the next days if you don’t re-engage them with a targeted notification.

• Promising New / Dormant users: Users who are about to become engaged. Don’t miss the opportunity to send them a message!

Batch also shows the number of imported tokens who haven't been reintegrated to Batch Smart Segments yet. You will find more information on token import here.

As soon as the request is completed, users with the Privacy and Administrate rights will receive an email (e.g. "[BATCH] Your GDPR request [request token] has been processed") with a link to an archive containing all the data Batch has stored for the provided identifier (e.g. list of sent notifications, list of installs attached to the id along with the data collected for each install, etc).

That file can also be downloaded from the Privacy center:

Requesting a Data Removal

All the data Batch has stored for the provided identifier will be deleted.

Creating a Label

You can create as many labels as you want. Every label you create has: 

• A code: Unique id of a label. Use it as a reference in your calls to the Batch API. Avoid editing label codes. By changing a label's code, you might trigger errors on your API calls if you don't update them with the new name. This may also reset the frequency capping limits on running campaigns already using this label.

• A name: Used to identify your label on the dashboard.

Managing Labels

You can edit the code and the name of existing labels or delete them if needed. Batch shows the number of orchestrations attached to each label so you can understand the impact of deleting or modifying one.

Batch provides a simple tool you can use to see the list of installs tied to a specific ID and the data Batch collected for each one of them. You can search installs based on:

• An advertising ID: IDFA (iOS) or GAID (Android). You can find your advertising ID by using My Device ID on iOS or by going to your device settings → Google → Ads on Android.

• A Custom User ID: Your own user IDs shared with Batch.

• An Installation ID: ID generated by Batch for all the installs the first time your users open the app. You can get your installation ID in the log of your app or display it in your app for debug purposes.

You can also see the data collected for random installs in your userbase.

For every install, the debug tool displays basic information on the left side:

• Basic information: Device type, last SDK start date, country, language, installation date, push op-tin status, app/OS/SDK version.

• API Key: API key tied to the install. This can be your live or your dev API key.

• Custom user ID: Custom User ID set for the install. The field will be empty if no custom user ID is set.

• Installation ID: ID generated by Batch for the install when user opened the app for the first time.

• Push Token: Push token attached to the install. The field will be empty if Batch hasn't received any token yet for the install or if the token has been invalidated (e.g. uninstall).

On the right side, you will find the list of all the data collected for a specific install:

• Native data: app version, bundle ID, carrier code, city code, device brand/type, installation date, last location, and more.

• Custom data: You will find here the list of all the attributes, tag collections and events received from the SDK or the Custom Data API. You search a specific value in the list if needed.

The dashboard will display the most recent install first. Simply click again the "Debug" or "Reload" button to refresh the list of installs and update the attributes/events list.

Sending a Test Notification

Batch enables you to send a test notification to all the installs attached to the ID you are debugging. Click the "Send Test Push" button at the top of the installs list:

If you need to send push notifications to your device on a regular basis, then you should add your ID as a test device by clicking the "Save as a test device" button.

Debugging a Trigger Campaign

You can also see if a specific install is or has been in the user journey of a trigger automation. Click the ⚡️ lightning icon in the top right corner of the debug tool. This will show the list of trigger campaigns that targeted your install at some point.

For every campaign, you can see when your install entered the user journey and when/why it exited that user journey:

• push_done: Batch sent a push to the install when the timer finished

• cancel_event: Your user triggered the cancellation event before the timer finished.

• stop: The trigger campaign has been stopped before the timer was finished.

• no_pushtoken: Batch tried to send a notification to the install, but it didn't have a token. This may happen if users didn't see the opt-in prompt yet or didn't turn off push notifications on iOS.

• pushtokennot_registered: The token attached to the install was not valid anymore when Batch tried to push it. This usually happens when users reinstall or uninstall the app.

• query_mismatch: The install was not matching anymore the targeting of the campaign when the timer finished.

Troubleshooting

There are several points you should check if you don't find any installs matching your advertising ID (IDFA/GAID):

• App restriction: Your app may not be able to collect advertising IDs. This happens frequently on iOS, especially if it doesn't displays ads.

• Device settings: Check your device settings to be sure you didn't turn on limited ad tracking in Settings → Privacy → Advertising.

• Batch integration: Make sure that the advertising id collection hasn't been disabled.

Transactional API Debug Tool

Batch provides a simple debug tool that lets the list of all the targeted push tokens for any given API call to the Transactional API. Go to ⚙️ Settings → Debug, select "Transactional" and input the token generated by the API on each successful call:

The advanced analytics view gives you detailed information for a specific transactional push:

• Sent: The total amount of sent push notifications.

• Not Found: Number of Custom User ID or installation ID are not linked to any push token.

• Undeliverable: Number of push tokens that were flagged as invalid by Apple/Google. Your app may have been uninstalled.

• Errors: Number of APNS/FCM/WNS errors.

Additionally, you can see how your userbase is distributed around the world in order to optimize your marketing strategies or decide in which language you should localize your next push notification.

The counters per region displayed on the map are calculated based on the data collected at the first application start. If the user's region changes overtime or is overwritten, the counters will remain unchanged.

Interpreting your statistics

There are 5 metrics you should check daily to see how your app is performing over time and measure the impact of your push campaigns:

DAUS

"AVG DAUs" stands for average number of Daily Active Users. It's a basic metric that shows the average number of users who open your app on a daily basis.

Pay attention to the evolution of your app's DAUs. They're a good indicator for seeing if the involvement of your users is increasing or if you need to send a push notification to re-engage them.

The DAUs/Installs ratio is also a basic indicator to measure the ‘stickiness’ of your app. Depending on the category of your app, this ratio can vary between 15% or 30%.

Installs

Number of new installs over a period of time. Updates and reinstalls are considered as new installs.

Bear in mind that users coming from an older version of your app and upgrading to a version with Batch's SDK (after a first release or a token import) are considered as new installs.

Starts

Number of times the SDK "starts" in your app over a period of time. The SDK starts every time a user opens your app.

The starts/DAUs ratio can help you to measure the average number of sessions initiated by your users.

Push

Total number of marketing and transactional push notifications sent over a period of time. Click on the Notifications tab if you want to see a full report on your push strategy (global open-rate, global re-engage rate, etc).

Revenue

Income generated in your app. Make sure you are sending custom data on transactions to see this indicator.

Uninstalls

Number of invalid tokens deleted daily, based on the feedback received from the platform push services (e.g. APNS on iOS, FCM on Android, etc). Tokens are considered invalid when users uninstall the app or clear your website data (web push notifications only). Batch receives these feedback every time a token is targeted by a push campaign. You may notice an increased number of uninstalls on days when you send many campaigns, as Batch will receive more feedback from the push services.

Rolling MAU

"MAU" stands for Monthly Active Users. It shows the number of users who opened your app at least once in the last 30 days.

The profile ID is a unique ID automatically generated by Batch.

Installation ID

The installation ID is an anonymous ID generated by Batch the first time users open your app or your website. That ID changes each time users reinstall your app or web session data is wiped. If a users visit your website from the same computer, using different web browsers (e.g. Chrome, then Firefox, then Microsoft Edge), Batch will attach visits to different installation IDs. A profile can store up to 50 installation IDs.

Custom ID

The custom user ID is a native field you can use to attach a unique user ID to a profile. That ID will act as a reconciliation identifier between Batch Profile base and your own backend.

Attributes

Native attributes

They have preset names and formats and are designed to capture common and essential information about profiles. They can be automatically collected by Batch (e.g. app version after SDK implementation)

Custom attributes

Any attribute specific to your needs and industry that is relevant to better target profiles and personalize messages (e.g. a loyalty status)

Events

They are used to trigger automations and refine targeting (eg. add_to_cart event)

How to create a profile?

Batch automatically generates new profiles in 3 scenarios:

• When a user starts your app or visits your website for the first time

• When the Profile API is called with a Custom ID that isn't yet known to Batch

• When a Custom ID is set via SDK, and this Custom ID isn't yet known to Batch

Developers do not need to explicitly declare the creation of a new Profile. Batch handles this process automatically, either updating an existing profile or creating a new one based on the data set via API or SDK.

Each profile has a unique profile_id generated by Batch. Other identifiers can be linked to it depending on its position in the lifecycle:

• Custom ID: The custom ID is a native field you can use to attach a unique user ID to a profile. That ID will act as a reconciliation identifier between Batch Profile base and your own backend. It can only be attached to 1 profile at a time.

• Installation ID: The installation ID is an anonymous ID generated by Batch the first time users open your app or your website. That ID changes each time users reinstall your app or web session data is wiped. Think about it as a device identifier that can travel from one profile to another depending on login/logout actions on your app or website. It can only be attached to 1 profile at a time.

Anonymous Profiles

Before you identify a profile with a Custom ID, Batch generates an anonymous profile.

The installation ID that triggered the creation of the profile is attached to the Profile.

Anonymous profiles are reachable via push notifications once they opt-in.

Logged-in Profiles

Logged-in Profiles are Profiles with a Custom ID that has been shared:

• via Profile API with any attribute update or event tracking

• via SDK with the identify method

Logged-in Profiles are reachable via email, push notifications and SMS.

What happens when setting a Custom ID on an anonymous profile?

The profile lifecycle in Batch is closely aligned with real-life user interactions. Understanding how data is stored against profiles can be clarified by examining common user actions: sign-in, login, and logout.

Sign-in

Definition: This occurs when you set a Custom ID that is not yet known to Batch.

Process: The Custom ID will be assigned to the initial profile, and all previously collected data will be retained within this profile.

Login

Definition: This happens when you set a Custom ID that Batch already associates with another profile. This situation can arise if the user has previously logged in on another device or if data was sent via the Profile API using this Custom ID.

Process: The anonymous profile will become orphaned, and all installations will be linked to the already existing profile. To transfer attributes from the anonymous profile to the logged-in profile, resend data via SDK after the identify call. Events that have been collected during the anonymous session will be reattributed to the identified Profile (last 3 months of events for apps and last month of event for web, with a limit of 10,000 events).

Orphaned Profiles

Definition: Orphaned Profiles are profiles that lack both Custom IDs and Installation IDs. This happens after a login from a previously anonymous profile.

Process: These profiles become unreachable and are excluded from all dashboard analytics and exports.

How are attributes reconciled on Profiles?

The majority of attributes on Profiles are reconciled using the "last update rule". This means that the most recently written value for an attribute will be displayed in the Profile view and used for targeting and personalization purposes, regardless of the attribute's source (SDK or API). This rule applies to:

• All custom attributes

• Email address

• Phone number

• Marketing email subscription status

• Marketing SMS subscription status

Exceptions

Certain native attributes follow different priority rules when being reconciled. These exceptions are as follows.

Region and Language

Priority order:

1. Set via API

2. Set via SDK

3. Automatically collected by the SDK

Timezone

Priority order:

1. Automatically collected by the SDK

2. API set

GDPR & Privacy

Profiles are compatible with the GDPR API, as well as all privacy requests made from the dashboard. To respond to privacy requests (data export and data deletion), Batch finds the Profile that matches the identifier in the privacy request and follows standard identity resolution process.

It means that when a data request is made with an Installation ID, Batch will not be able to find a Profile that holds this Installation as well as a custom user ID. To read or delete a logged in Profile (with a custom user ID), it is necessary to provide its custom user ID in the privacy request.

Event retention

Events tracked by SDKs or the Profile API are stored and can be used for targeting for 1095days (3 years) by default. Contact the support to customize this policy.

Inactive profiles

Profiles that have not been active for a certain period of time are classified as inactive and deleted.

What is an inactive profile?

A profile will be considered inactive if no activity is detected for it for a certain period. By default, the period of inactivity is set to 390 days. You can reach out to your Customer Success Manager to shorten this period.

Activity on a profile may be:

• Data sent from a mobile application or website via Batch SDKs. Example: an open or a visit, change of opt-in status for push notifications, custom attribute or event tracking, etc.

• Custom data tracking via Custom Data API or Profile API

• User event tracking via Trigger Events API or Profile API

• Upload or update of email subscription information via Profile API, Email Subscription API or mobile and web SDKs. Example: modification of email address, update of opt-in status for email marketing, etc.

• Engagement events with emails received: open or click.

What is the impact of these deletions?

Once a profile's data has been deleted, it can no longer be targeted by all messages based on the Profile based data model. This implies email, SMS, and push V2 messages.

If an activity takes place for a user after their profile has been deleted (e.g., a user returns to the application 14 months after their last activity), a new profile will be created for them.

This behavior is consistent with the profile lifecycle management in Batch. When a profile is deleted due to inactivity, the system essentially "forgets" about that user. Upon the user's return and subsequent activity, Batch treats them as a new user, creating a fresh profile to store their data.

First, you need to give a Name to your Campaign.

• A draft Campaign cannot be saved if it has no name.

• The name is how you are going to be able to distinguish the Campaign from the many others you are going to create, so try to be as specific as possible.

Managing a Campaign

Stopping a Campaign

• A Universal time (UTC) Campaign cannot be stopped after sending.

• A Profile's local time Campaign can be stopped, however, stopping this Campaign only cancels it for users located in timezones that have not yet reached the scheduled sending time.

  • For example, if the Campaign is scheduled for 2PM (local time) and is canceled at 3PM UTC, a targeted user located in the US (UTC-4) will not receive that Campaign.

Modifying a Campaign

• A Campaign can be modified until it is completed.

• You can modify its targeting, timing and/or content.

• If your Campaign is scheduled to be sent at a later date, or in other words if the sendings have not started, all your changes can be taken into account.

• However, if sendings are already in progress, all the people concerned by these sendings, will not be affected by your changes. Changes will only be effective for sendings that have not yet started.

  • We advise you not to modify your Campaign when sendings have started to avoid errors. This particularly applies to local Campaigns.

Deleting a Campaign

Any deletion is definitive, you will no longer be able to access your Campaign.

Understanding Campaigns listing

All the Campaigns you have created since the project was created are available on the listing.

From the Campaigns listing you can:

• Filter the listing by:

  • Date: Filter campaigns that were active over the period, meaning sends occurred between the two selected dates.

  • Status: Draft, Planned, Stopped, Completed.

  • Channels: Email, SMS, Push.

  • Labels: All CEP labels attached to the project.

    • You can select several options for each filter and combine filters.

• Access quick actions that adapts to the Automation status (by clicking on the three dots buttons):

  • If in draft:

    • Edit Campaign.

    • Run Campaign.
• Access key metrics:

  • Delivery: number of sent

  • Interaction: percentage of opens

• Access key dates related to a Campaign's status and content by hovering over the status icon on the listing page or within the Campaign form:

  • Created at: The date and time the Campaign was initially created (i.e., first saved).

  • Last edit: The date and time the Campaign's content was last modified since its creation.

  • Currently {Campaign status}: The Campaign's current status (e.g., Draft, Planned, Sending, Stopped, Completed) and the date/time it entered this status (this does not apply to the 'Completed' and 'Sending' statuses).

• Export your Campaigns Analytics (by clicking on the “Export” button).

• Search a specific Campaign.

• Fullscreen

• Banner

• Modal

• Image

• WebView

Customize your theme

Themes are fully customizable, including:

• Background and text colors

• Header, title, and image

• Number of CTAs

• Overall layout and appearance

Once your theme is ready, you will be able to select it from the dropdown menu during the "Message" step when setting up your campaign. (See: In-App - Part 4 - Editing Your In-App Campaign Message)

Create your In-App automation

Now that your theme is ready, go to Automations > iOS or Android > Create a New Campaign:

Name your In-app automation and set up targeting

Just like with a push campaign or automation, you can define the audience targeting conditions.

Set the trigger action

This is the user action that will cause the message to be displayed:

• Choose from any tagged and tracked event collected by the Batch SDK

• You can also set:

  • Priority: if multiple campaigns use the same trigger, set which one takes precedence.

  • Capping (optional): limit how many times a user can see this message.

  • Grace Period (optional): define a minimum delay between two displays of the same campaign.

  • Start/End Date: schedule your campaign’s availability window with start and end times.

Customize the message and CTA behavior

Now it’s time to craft your message 🌟

Select a theme for your In-App message using the dropdown menu:

Fill in the content for your campaign: title, body text, visuals, etc.

Define the behavior of your Call-to-Action (CTA):

• Choose what the CTA should do:

  • Redirect to a URL or screen

  • Trigger a smart re-opt-in

  • Copy something to the clipboard

  • Open the rating popup

  • …and more

You can also attach secondary actions to the CTA, such as:

• Tracking an event

• Adding or removing a tag

And that is it! With these steps, you are ready to launch personalized, real-time In-app automations that engage users exactly where they are: inside your app ✨

First, go to your Batch Dashboard and go to Automations > New automation > Select the channel of your choice (Recurring Email, Push or SMS), and name it to start a new automation:

Optional: you can add labels to your automation (up to 5):

Then, let's set up your recurring automation! 💪

Targeting

The targeting block is where you will define the segmentation of your automation.

By default, Batch considers that you will target your entire audience. First, you can select a specific country or language.

Then, you can refine your segmentation through different options, by clicking:

Add Conditions

From then on, you will be able to select native targeting elements but also profile attributes (data specific to your app business and selected thanks to the tagging plan).

Use Segment

It will allow you to call Segments as blocks in the targeting and combine segments (inclusions and/or exclusions) by calling up to 10 segments in your targeting:

When a segment is linked to an orchestration, you can access / view the segment by clicking on the eye icon 👀

Use Audience

You can add a specific Audience to your communication:

Play with AND/OR option

You can add up as many conditions as you want, and create specific scenarios by clicking on 'AND/OR':

💡 Let's take the example of a recurring automation to wish users happy birthday with a nice message like; "Happy Birthday 🎁 Celebrate your special day with 20% OFF – just for you!". This automation is to be sent based on user's birth date.

Here's what automation targeting should look like:

Timing

Now that we know who to send your communication to, let's define when to send it!

First, set up the date and the hour of the first sending of the automation, and then the end date if needed:

You can choose to send your on Local time or Global time (UTC):

• The Local Time option lets you send a message that will be received at a given time according to the user’s time zone. This ensures that marketing efforts target your users at a uniform time.

• On the other hand, the Global Time (UTC) option allows you to send a message to your users at a specific UTC time regardless of their location.

Finally, let's define the frequency of the automation!

Depending on your automation goal, you can adapt the frequency of sending between days, weeks, and months.

It is also the time to set up a capping rule if you want to limit the number of times a user will receive your automation:

Message

Message editors vary from one channel to another. To learn more about composition, visit the following sections:

Run your Recurring Automation

Now that your recurring automation is ready, you can either run it or keep it as a draft and launch it later 🌟

Once your campaign is live, you can track its performance in the Analytics section.

Body: Designed with Batch Email Composer or uploaded as HTML

All fields use personalization, except the sender address, which must be selected from predefined options set in the Settings.

Header information

Email Sender

The sender name and address appear as the source of the message.

• Email senders are categorized by orchestration type (marketing or transactional) and are defined in the Settings.

• Learn more about configuring email senders here.

Custom Reply-To

By default, replies to your email are directed to the sender’s address. You can specify an alternative reply-to address if needed.

Subject

The subject line is the first thing recipients see. Make it engaging by incorporating personalization.

Preheader

The preheader appears next to the subject line and is, by default, the beginning of your email body. You can override it to display relevant and concise text.

Email Body

You can create your email body using one of the following methods:

1. Email Composer

Batch’s Email Composer, powered by Stripo, allows you to design emails from scratch. Existing templates or modules can also be re-used

Helpful resources:

• Stripo Education Portal

2. Upload HTML Template

If you have a pre-designed email template, upload it directly.

• See the guide:

Preview Options

Preview your email in both Desktop and Mobile modes to ensure proper rendering across devices.

Send a Test

• Test emails include "[TEST]" at the beginning of the subject line for easy identification.

• The list-unsubscribe header is not included in test emails.

• Other behaviors are similar to test messages across all channels. See more details here.

Opt-in Management

Unsubscribe Link

You must include an unsubscribe link in Marketing emails. Learn how to add one with

When a recipient clicks the link:

• They are unsubscribed from your marketing emails.

• Recipients are redirected to a personalized landing page. See how to proceed in.

Suppression Rules

Batch maintains a suppression list with the following policies:

• Hard Bounces: Any email address that hard bounces is put on the suppression list for both marketing and transactional emails.

• Soft Bounces: After 5 consecutive soft bounces on marketing emails, the email address is put on the suppression list for marketing emails only.

Spam Complaints are treated as unsubscribes. The recipient’s marketing status is set to "unsubscribed," but their email is not added to the suppression list.

Email Deliverability

Batch offers extensive resources on email deliverability, sender reputation, and warm-up strategies. Access these resources in .

Delivery metrics

Email

• Sent: The message was dispatched by Batch.

• Delivered: The email was successfully accepted by the recipient's email server.

• Opened: The email was opened, this rate can be seen with and without machine opens (for instance due to Mail Privacy Protection). The open rate is calculated by dividing the number of email opens by the number of emails delivered.

• Clicked: At least one of the links in the email has been clicked. Batch unsubscribe links are not taken into account. The click rate is calculated by dividing the number of emails clicked at least once by the number of emails delivered.

• Bounced: Delivery failed. The bounce rate is calculated by dividing the number of email bounced by the number of emails sent. Detailed explanation about Bounces available here. For a detailed explanation, refer to .

• Unsubscribed: The recipient opted out via the List-Unsubscribe header or Batch unsubscribe link. The unsubscribe rate is calculated by dividing the number of email that led to an unsubscription by the number of emails delivered.

Push

• Sent: The message was accepted by the push provider (Apple or Firebase(Google)) for a specific device installation.

• Sent opt-in: The message was accepted by the push provider (Apple or Firebase(Google)) for a specific opt-in device installation. We recommend tracking this metric as pushes sent to opt-out devices are unlikely to be seen, making sent opt-in a more realistic indicator of deliverability.

• Opened: The recipient opened the notification or was influenced to open the app/site. This metric includes both direct opens (user taps/clicks the push) and influenced opens (user opens the app/site within 3 hours after receiving the push). The open rate is calculated by dividing the number of unique opens (direct & influenced) by the number of sent opt-in. Influenced opens are only available for messages sent after August 1st 2025.

• Opened directly: A complementary metric showing only direct opens (taps on the push notification).

• Bounced: Delivery failed, often because the app was uninstalled or other errors occurred. The bounce rate is calculated by dividing the number of bounces by the total number of messages injected into the push provider (where injected equals sent plus bounce).

Push analytics can be filtered by platform type: Web Push, Mobile Push, or specific platforms like Android or iOS.

In case your push notification redirects to a Mobile Landing (see In-App & Mobile Landing), Mobile Landing metrics can also be available:

• Clicked: The number of clicks on any button within the In-App message, excluding clicks on buttons configured with a “Dismiss”. This metric does not include other dismissal methods like clicking the top-right 'X' button or swiping.

• Click rate: total of clicked messages divided by the total of displayed Mobile Landings. For a push orchestration with Mobile Landing, the number of displayed Mobile Landings should be equivalent to “Push Opened” ones apart from rare exceptions (user opens its push in airplane mode, etc.)

In-App

• Delivered: The in-app was successfully displayed to the recipient who may then either click on a CTA or dismiss it after reading.

• Clicked: The number of clicks on any button within the In-App message, excluding clicks on buttons configured with a “Dismiss”. This metric does not include other dismissal methods like clicking the top-right 'X' button or swiping.

• Click rate: Total of clicked messages divided by the total of delivered In-App.

SMS

• Sent: The message was dispatched by Batch.

• Delivered: The message successfully reached the recipient's phone number.

• Clicked: SMS URL shortening and tracking must be enabled to track clicks. At least one of the links in the SMS has been clicked. The click rate is calculated by dividing the number of SMS messages clicked at least once by the number of SMS messages delivered.

• Bounced: The message could not be delivered due to issues like:

  • Absent subscriber: The phone is turned off or out of network coverage.

  • Unknown subscriber: The phone number is inactive.

  The bounce rate is calculated by dividing the number of SMS bounced by the number of SMS sent.

• Unsubscribed: The recipient opted out by replying with the appropriate STOP keyword. The unsubscribe rate is calculated by dividing the number of SMS that led to an unsubscription by the number of SMS delivered.

The number of installs is too low after my first update with Batch

This can happen for several reasons:

First session

Your users need to open the app once after updating it to a version built with Batch. Batch will place them in the NEW segment and retrieve their device token so you can send them a message right away.

The number of installs/push tokens will increase progressively the first week, as your users migrate and make their first session.

Token imports

If you’re coming from another push provider, you may need to import your push tokens and send a notification to your old users to accelerate the transition. Make sure you don't target the new segment the week following the integration of Batch in your app.

The number of installs is different from my other tools

The reason data on Batch and your usual analytics tool or app store analytics may differ slightly, is that Batch may use different methodology and metrics to process and display the stats (timezones, data collection method, etc).

If the difference is too big be sure Batch runtime is integrated correctly.

I'm wondering how often are the analytics refreshed

Audience tab

The Audience tab is the first screen you see when you click the Analytics tab (more information here). Daily Active Users, installs, starts and the revenue shown on the Overview tab are refreshed daily, at 12:00 PM GMT.

Notifications tab

The analytics shown on the Notifications tab is refreshed in real-time for the current day.

Note that the reengage rate and the repartition between influenced and direct opens are based on an estimate, which is recalculated within a few days after the campaign has been sent.

Userbase tab

The userbase tab gives you a complete overview of your current userbase (more information here). There are two kinds of data displayed on the Userbase tab:

Basis statistics

The number of installs and tokens are refreshed in real-time:

Native and custom data

The data is refreshed daily, at 12:00 PM GMT. Please note new custom attributes sent from the Custom Data API may take up to 24h to appear on the dashboard.

Automation analytics

Automation analytics exports can be downloaded from the dashboard. The export is in the form of a CSV file containing automations metrics, settings, and much more. It allows you to filter your automations' metrics & data to include in your export. These exports are available from the In-App tab.

For example, you can:

• Analyze In-App automations performance

• Compare automations metrics by label, type, source, country, etc.

• Run in-depth analysis thanks to the extended data exported: sending time, targeting type, message content, etc.

• Etc.

Set your export from the Automations list

First, click on "Filter" and select the status, date range, and labels of automations. Click on "Apply filters" button to save your choices.

Then, click on "Export" button on top of the last column.

Export filters

Before downloading the CSV Export, you can specify the granularity of your export. By default we are exporting the automations corresponding to the filters you selected. You also have the possibility to export directly the metrics for all your automations by checking "All automations" button.

Automation’s metrics & data

All exports automatically contain essential data by default:

• Essentials metrics represent all the metrics available in your CSV export by default, they are always included. Here is the list of the metrics: token; source; status; label; automation name; device synced; display; clicks; 1st button; 2nd button; close.

In addition to the default export data, you can add additional data:

• Extended data allows you to enrich your CSV export with the following automations setup information: start date (recurring and trigger); end date (recurring and trigger); smart segments; country; custom audience (YES/NO); languages; targeting applied (fullbase or custom targetting); trigger event; message; format; button 1 action; button 2 action; global action; tracking id.

Split data

You can choose the level of granularity of your CSV export. The automation granularty is always selected, you have the possibility to go further in the granularity of your CSV export by choosing to split the data by days.

Advanced analytics

Similarly to push automations, the Analytics button will let you see more detailed statistics about your automation.

Let's dive into the details of the available statistics here:

Summary

• Devices synced: number of unique devices that were targeted by the automation and have downloaded, or synced the automation locally. This is not the number of displayed of the In-App, see below.

• Displayed: number of times the message was displayed.

• Clicked: number of clicks on one of the buttons of the In-App automation. The top-right 'X' close button is not included in this total.

• Click rate: total of clicked messages divided by the total of displayed messages.

Performance

The performance section will run you through the results of your automation, from the number of displayed messages to click distribution.

• Displayed: Number of times the message was displayed.

• Clicked 1st/2nd button: Number of clicks on the message's buttons. Hover over the tooltips to read the content of the buttons in your message. (Fullscreen, Banner and Modal formats only)

• Close: Number of clicks on the native close button.

• Buttons: WebView format only - Total number of clicks on the message’s buttons. Click “See clicks details” to get the clicks and click rate per button.

Daily statistics

The histogram view allows you to compare visually two metrics of your choice on a given time range. You can also choose the array view to see all the metrics at once:

• Displayed: Number of times the message was displayed.

• Clicked: Number of clicks on one of the message's button.

• 1st / 2nd button: Number of clicks on the 1st / 2d button of the In-App message.

First, you will need to define your header information with:

• the Sender which is the email address and name that will appear as the sender of the message

• the Reply to field (optional)

• the Subject of your message.

Create the body of your email

1. Design your message with our Email Composer

Batch allows you to create an email from scratch through our Email Composer.

1. Upload your HTML template

If you have a template ready to be used, you can upload it here!

Multi-language

You can also create multiple versions of a message, one for each language, by clicking Multi-language, ensuring that profiles receive the message in their own language:

When adding a new language version, the default version will be duplicated, keeping your format options, images, and other elements intact, so you only need to edit the text that requires translation.

A/B Test

You can A/B test your email! Here's how:

• Enable the feature by toggling the switch at the top right of the Message section.

• Create variants: You can create up to four variants, either by duplicating an existing one or starting from scratch:

Testing your email message

1. Directly in your inbox

Now that your message is written and ready to captivate your readers, you can test how it looks on your device!

Use the Send test button on the email message window and type your email address:

If you want to reach more than one address, don't forget to separate all of them with a comma:

The email is immediately sent! ✨

1. Test your user data directly on Batch

It is possible to preview the dynamic data of your email using the "Preview As" feature. To do so, use your custom user ID (or one of your users), then enter it in the dedicated field:

You can also send this email, filled-in with the personalization data of the selected profile, using the 'Send test' feature as shown above.

🚀 Your first email campaign is now ready to be sent! Click on the 'Save and run' button at the bottom of the form to activate it or save it as a draft and come back later.

For both migration types, you need to create in parallel:

1. A campaign targeting the imported tokens, with the previous provider's payload

2. A campaign targeting the rest of the userbase, without the previous provider's payload

Targeting imported users

After we’ve completed your tokens import, a new filter will be available:

1. Imported tokens only, which are the manually imported tokens, not yet detected by our SDKs

2. Collected tokens only, which are the tokens already collected through the Batch SDK

There are a few things you need to keep in mind before targeting your newly imported users:

• The Imported tokens only filter is not targeted by default when you create a new campaign. Don't forget to select it the next time you want to send a notification.

• The first time you send a notification to your imported users, Batch will clean the inactive or invalid tokens that may come from your previous push provider. Depending on how many invalid tokens we find, the number of imported tokens will decrease a few days after the import.

Campaigns statistics

The campaign statistics are provided by the Batch SDK. This is why you may notice that the campaign statistics are not available for campaigns that target users who don’t have Batch SDK.

Imported tokens and APIs

The imported tokens can be targeted via the (via "Filter push tokens" or through Audiences if you have imported the Custom User ID with the push tokens).

Your API-scheduled notifications can be migrated in the same way as described above.

The list of your pending invites is greyed out until the user accepts the invite and creates his account. You can delete or resend an invite at any moment.

Managing Permissions

Batch lets you set specific permissions at the user-level to facilitate team collaboration.

There are several permissions you can grant or revoke:

• Administrate: Grants full access to company account (team members, users permissions, etc). Note: an account can have more than one Administrator.

• Review: Grants read-only access to the dashboard. Review users will not be able to create nor edit campaigns.

• App: Grants users rights to edit and manage apps.

• Campaign: Grants users rights to create, edit and delete campaigns.

• Privacy: Grants users rights to manage GDPR settings.

App-level Permissions

To facilitate collaborative work, a user with "Administrate" rights can grant another user access to a group of selected apps. This is useful if you want to make sure specific users cannot access all the apps on the dashboard or if you have multiple projects with separate teams working on each one.

The user will have the same permissions on all the assigned apps. Batch also allows you to grant access permissions from the app on the dashboard.

Troubleshooting

I didn't receive my invite

Here are some suggestions to find the issue:

1. Check your spam folder and look for an email sent by hello@batch.com.

2. Resend the invite: Ask the administrator of Batch account to double-check the email address they used or resend the invite.

3. Validation link: If none of the above work, your manager can send you the confirmation link he will see after inviting you.

I Get "[Email Address] Is Already Registered On Batch.Com"

If one of your teammates already has a Batch account registered with his email address, he needs to contact our support team (support@batch.com) with the following information:

• Email address of his first account.

• Email address of the team he wants to join.

We will add him to your team with all the apps he created with his previous account.

Can I Manage Several Accounts With The Same Email Address?

You cannot manage more than one account with the same email address.

If you have a Gmail account or use Google Apps, you can add a "+" at the end of your username to benefit from dynamic alias (e.g. andrew+secondaccount@gmail.com).

How Can I Delete My Account?

Just ask us to delete your account at support@batch.com. Our team will let you know when it's done.

Company Settings

Company Name

You can edit here the company name that will be displayed in the dashboard of your teammates.

Making 2FA Mandatory

Account administrators can require new and existing teammates to use two-factor authentication (2FA) when they sign into Batch.

Plans & Billing

You will find here all the information related to your plan and billing.

Plan

Batch will display here the current plan for your company.

Invoicing Information

All the information needed on your company to process the invoices: full name, company, VAT number, address, zip code, city and country.

Invoice History

Users on self-service plans can see here all their invoices and download them as pdf files.

GDPR & Privacy

In addition to the ability to request data removal or data access, you can edit all your GDPR-related information from the dashboard.

Company Information

Declare here whether you process or not any EU customer personal data and if you are subject to GDPR constraints. You can also edit the information needed about your company (e.g. company name, address, zip code, city and country) and see the date of the last modification.

Data Protection Officer

Optional - Name/email address of your company's DPO.

Types of Data Collected

List of the data collected with Batch. You can add custom fields if needed.

Data Processing Agreement (DPA)

You can read again the DPA here. Please note the DPA must be accepted to use Batch, unless you declared your company is not subject to GDPR constraints.

• For example, if your Campaign is scheduled to be sent on Friday, July 19th at 6pm global time (UTC), your users will receive it at 2PM in the US (UTC -4), 8PM in France (UTC +2) and at 2AM on July 20th in China (UTC +8).

• The dates displayed are based on your browser's local time.

Example: Order shipped 📦

Let's apply the above steps to an example:

They take the form of 1-to-1 automated and personalized scenarios, usually linked to account activity or a commercial transaction, like a password reset request or an order validation.

What about delivrability?

Some specific rules apply to transactional emails:

• They do not require a marketing opt-in status;

• They are sent in real time;

• They have a higher criticality than other scenarios, and tend to generate higher engagement rates as well.

With Batch, each email sending purpose is isolated for deliverability reasons.

Transactional emails are sent from a dedicated subdomain (e.g. service.domain.com) and a specialized IP / IP pool with an excellent reputation.

This protects the deliverability of transactional emails from other types of scenarios sent with Batch (newsletters, marketing automation, etc.).

Management on the Batch dashboard

To satisfy the need of brands and media to no longer have silos between marketing and transactional emails, we have chosen to handle them in a coordinated manner on the Batch platform.

This has several advantages:

• Technical simplicity: you have a single endpoint for all server-side data operations: our Profile API. In the case of a transactional scenario, it allows you to track an event enriched with additional data for message personalization purposes. This single event can be used across different types of scenarios and different channels, streamlining API calls and data flows and considerably simplifying technical implementations.

• Integrated tracking: delivery and engagement indicators are tracked in a centralized way on the Batch dashboard. You can consolidate information related to a recipient, such as scenarios received, opened and clicked.

• Operational team autonomy: business teams can modify templates or carry out A/B testing independently. This frees up the bandwidth of technical teams to concentrate on other tasks.

Technical implementation

When a transactional trigger is detected in your back-end, call the Profile API to track a user event for the given recipient, via its Custom user ID.

Attach to the event any data you need to personalize the email as event attributes.

In case of highly personalized emails such as order confirmations, you can use attributes objects to structure your data.

For example, in case of an order tracking email, track a parcel_sent event when the order has just left the warehouse.

Here is an example of how the payload could look like:

And that's it! The rest is done on the dashboard.

How to setup the email from the Batch dashboard?

Go to the Batch dashboard, Automations → Email → New automation → Email Trigger.

Set up entrance

Click on 'Select trigger' and choose the event that will trigger the email:

Target opt-out users

Click on 'Add targeting' and uncheck the toggle Only send to opted in users.

Transactional emails do not need a marketing opt-in status.

Compose your email

1. Add your sender

   Click on the message block and select a sender attached to your transactional sending subdomain.

2. Define the subject of your email

   You can add dynamic personalization by clicking on the brackets {...} if needed.

3. Compose your email

   Last but not least, there are 2 ways to create the body of your email:

   1. Design your message with our Email Composer.

      Batch allows you to create an email from scratch via our Email Composer.

   2. Upload your HTML template.

   If you have a template ready to be used, you can upload it here!

Do not forget to add your dynamic variables coming from the event!

Saving your automation

Click on the 'Save and run' button at the bottom of the form to activate it or save it as a draft and come back later.

Your email is now ready to be sent! 🎉 (in real-time as soon as the trigger event is captured by Batch, from your sending subdomain dedicated to transactional emails).

Prerequisites

Follow these steps to start the migration:

Migration types

Depending on your constraints, you will choose to keep or remove the SDK of your previous push provider for the first release of your app with Batch. Here are details on these two migration types to help you make a decision.

Keep both SDKs: Staged migration

In this case, the first app release integrates both the previous push solution’s SDK and Batch SDK. This makes it possible to use one or the other solution in parallel to send push notifications as long as the SDKs coexist in the app.

The timeline for teams training on Batch dashboard and tokens export/import is more flexible with this method. There is no sudden service interruption with your former push provider. The cohabitation of SDKs can cause duplicate pushes on Android. In this case, you need to use an Interceptor in your app (see Push payload).

Include only Batch SDK: Hot swap migration

The SDK of the previous push solution is removed from the app once Batch SDK is integrated. As soon as the version of the app with Batch is released, Batch is the only solution that collects the new push tokens, and becomes the only solution that you can use to target your userbase.

This method allows you to migrate within a short timeframe, but implies fixed tokens export dates and that your marketing teams are comfortable using the dashboard before the first app release with Batch.

Tagging plan

You should list the campaigns to be migrated to determine the tagging plan to be implemented.

Push tokens import

A push token is an anonymous ID generated by the push services (Apple, Google, etc.) that is used to target your users via push notifications. In the context of a migration, importing all your existing tokens makes it possible to reach your whole userbase, including users who don’t have a version of the app that includes Batch SDK yet.

Here are the detailed specifications for the tokens import: Importing your tokens.

Push payload

After migrating your push tokens to Batch, you will be able to target users who are still using a version of the app that does not include Batch SDK.

To contact these users correctly, you need to use the payload that is expected by the SDK of your previous push solution. You have to get in touch with your previous push provider to get it.

iOS

The iOS payload of a push notification is standard and push notifications are displayed by the system. The expected payload is still needed to manage deeplinks.

Android

On Android, push notifications are handled by the SDK. The expected payload is required to manage the whole content: the title and body of the push notification, the deeplinks, etc. In case of a staged migration (see Migration types), both SDKs might try to display the notification sent by Batch, which may result in duplicate push notifications.

To address this, here is an interceptor to be integrated into your app that disables the Batch receiver when the payload of another solution is detected (read more on how to register it ):

Testing

Once all elements have been integrated, you need to test the basic implementation following these guides: iOS / Android.

As part of the migration process, it is crucial to ensure that all users will be contacted correctly and that there is no unexpected behavior in any version of the app. You will find all the extra testing steps here: Testing.

Campaigns migration

Once your app has been released with Batch SDK and your tokens have been imported, you can start migrating your push campaigns. Here is how to proceed:

The process of campaign migration is detailed here: Campaigns migration.