At Batch, we advise a 15-30 character limit for your title and a 120–140 character limit for your body description.

If you create a long message of more than 140 characters, not all 140 characters will be shown to the user. It will depend on whether the notification is shown as an alert on the lock screen or when the phone is actively used.

We recommend keeping your title and body message short as possible. Focus on keywords and short content, to encourage the user to click.

iOS' body specificity

iOS displays up to 180 characters, including spaces, spread over 4 lines for push notifications displayed on the lock screen. The text is displayed in full when the push is opened.

Android's body specificity

Android only displays one line of text from the lock screen. This means that only 50 characters are displayed, including spaces. The full message is displayed when the notification is opened..

We advise you to test your message on different devices (on iOS / on Android) and see how your message is displayed before sending it to your users.

All content adds to the total weight, including:

• Text

• Links

• HTML code (including conditional display code)

→ Attached images

Images can be attached to your emails in two different ways:

• Enclosed images: Enclosed images are not stored in the template itself. Images are loaded remotely and only the path to the image is referenced in your email template (e.g. <img src="https://path/to/img.png" alt="img"/>). This is Batch's default behavior when you create a template from the email composer.

• Embedded images: You may also embed an image encoded in Base64 within your HTML template (e.g. <img src="data:image/jpeg;base64,[base64code]" />). Use this approach for small images only, as it adds considerable weight to your template: each Base64 digit represents 6 bits of data. For example, a single 156KB JPEG image will add more than 200K characters to your HTML template.

Optimizing Your Emails

Batch automatically includes two tracking pixels in your emails:

• One at the top

• One at the bottom

This dual-pixel approach ensures open tracking even if the email is clipped.

Best Practices

1. Move your unsubscribe link to the top of long emails to reduce spam complaints

2. Minimize email size by:

   • Reducing the number and length of links

   • Condensing text

   • Optimizing HTML code to use fewer characters

When an email is sent from your campaign, the ESP (Email Service Provider) replaces the original links with tracking links of its own, for example:

This link:

Is replaced by this one once the email is received:

By managing the redirection using a link of its own, the ESP can track the CTA / link opened actions.

Unfortunately, replacing the universal link causes the redirection not to work. Therefore, when using universal links, you need to disable the ESP link tracking, which means you will not be able to track clicks on these links in your Batch campaign stats.

As an alternative, you can rely on the classic Analytics tracking you probably already add to your links (e.g. ?utm=, etc) and track clicks in your dedicated Analytics tool.

Dealing with universal links in your template

In order not to break redirection on universal links, you can disable the ESP’s link tracking by adding the data-msys-clicktrack="0" argument to your link HTML tag as follows:

Using the debug tool

First, go to Settings > Debug.

You can use the debug tool to find your most recent install, based on:

• An Installation ID, which is an anonymous ID generated by Batch.

• A Custom User ID, should be the unique user ID you are sending to Batch from the SDK (more information here: (iOS / Android / web)

The debug tool shows all the native and custom data we have on your most recent installs:

• Custom User ID: This field shouldn't be empty if you are sending it to Batch and are logged into the app. Make sure that ID disappears after your log out.

• Attributes/events: Your attributes and events will appear in the right panel of the debug tool. Make sure important attributes are sent to Batch in the right format (e.g. date, string, boolean, etc) and at the right moment (e.g. on the first start of the app and/or when a value changes etc). Events will appear as soon as you perform the tracked action in the app.

• Last location: In case you share with Batch the most recent location of your user, you should see a latitude/longitude in the right panel of the debug tool.

To create a new audience, go to Data > Audiences and click on Add audience:

Upload the audience file

Upload a .txt, or .csv file, with one Custom ID per line only:

Use the audience in your orchestration

Once the audience is uploaded, create your orchestration and use the audience in your targeting.

2. Rich audiences

A rich audience is a static list of users, which you can associate to one or several attributes. You can then call these attributes in your orchestration for personalization purposes.

Rich audience file

The rich audience file should only contain the Custom User IDs and the associated attributes, each in one column.

• For rich audiences uploaded manually on the dashboard, only 1 associated attribute is allowed in the file, and its format should be STRING.

• For rich audiences uploaded through our Audience API, several attributes with different formats can be included.

Personalization

To personalize your orchestration with the values in your rich audience, first add the audience to the targeting.

In the title/body of your message, use the following code to call the attributes:

• For rich audiences uploaded manually on the dashboard:

{{audienceAttribute('audience name', 'att1')}}

• For rich audiences uploaded through the Audience API:

  {{audienceAttribute(<audience name>, <attribute name> ) }}

You are now ready to create your own journey using the Yes/No Split feature 🚀

You will find the list of the custom data received by Batch in Data > Profile data:

1. Targeting

Create a recurring automation, click Add conditions to select the attribute you will use to target the right users.

You can either use:

• time in the future to warn/remind users about a specific date coming up

• time in the past to remind users about a specific date in the past

• time in the past occurred 0 days ago to alert users on the D-day

2. Timing

Ensure you set the Frequency to 1 per day 👇

You won't need to set a capping for this type of automation, as this is important information and users should not trigger it often.

3. Message edition

Write your message by adding a title, a description and emojis.

You can even personalize your notification based on the same custom data you are sending to Batch (e.g the first name, the number of loyalty points/miles/jackpot left). This will add more context to your message.

2. Use your segment

Once your segment is created, you can use it in any type of campaign or orchestration. Click on the Use segment button to select your segment. You can add up to 10 segments.

Your automation is now almost ready to be sent!

3. Manage your segments

Use the page Data > Segments to manage your user segments. Create, delete, update and export them from the same page! Check the Estimated profiles of each segment and the number of orchestrations using it in real-time:

4. Export your segments

Download the list of profiles that match the conditions of your segment by clicking on the Export profile button next to your segment:

Once your export is processed, you will promptly receive an email containing the download link for your file!

The file will contain the following information:

• Custom ID

• Profile ID

• Phone number (if available)

• Email address (if available)

Learn more about the Segment feature on the Profile documentation.

Here is an example of an unsubscribe link:

Adding an unsubscribe link to a template via HTML

Here is how you can simply add an unsubscribe link for an email template in a single language:

If the email template already contains personalization conditions to change the language of certain text blocks, the same should be done for the unsubscribe link:

Adding an unsubscribe link to a template using the Email composer

You can also insert an unsubscribe link easily when using the email composer to create your email templates.

To do so:

1. Select the text

2. Add a hyperlink to the text area

3. Select the Unsubscribe option listed in the Link field on the left side panel.

Choosing a confirmation landing page

Once recipients click on the "unsubscribe" link:

• Batch removes the recipients from the marketing mailing list

• Recipients are redirected to a personalized landing page hosted on your side

Batch unsubscribe confirmation landing page is localized in FR/DE/ES/EN/IT: when inserting the unsubscribe variable, the landing page will be translated in the end user's browser language.

If you do not have one yet, you can use our default landing page:

• 🇫🇷 French: https://static.batch.com/list-management/landing.fr.html

• 🇩🇪 German: https://static.batch.com/list-management/landing.de.html

• 🇬🇧 English: https://static.batch.com/list-management/landing.html

• 🇪🇸 Spanish: https://static.batch.com/list-management/landing.es.html

• 🇮🇹 Italian:

You are now ready to create your own journey using the Random Split feature 🚀

To add the color background, click on the element of the structure in your email, and on the options panel on the left you'll find the Background color of content field. Choose a color among the proposition or type the color code of your choice:

Add a background image

To add a background image, go to the Appearance tab and find the Background image button in the General Settings part:

There, add your image by dropping one or with an external link. Check our documentation if you need help handling the image and editing it.

Once the chosen image is here, you can set it up! Define its position and click the "Repeat image" button if you want your image to be applied to the whole email, no matter how long it is:

a) Invalid file name in your ZIP file

If you receive the error labelled No index.htm(l) or mail.html file found, you should rename the HTML file to index.html (or mail.html). If the file is not named correctly, the import will fail.

Here is how to resolve this issue:

1. Unzip the ZIP file that contains the HTML email

2. Find the target HTML file

3. Rename the target HTML file to index.html (or mail.html)

4. Zip up the file

5. Upload the file

2. My images are not displayed in my email template

a) Wrong structure of the ZIP file

To import templates on the Dashboard, Batch needs the ZIP file to contain exactly one index.html (or mail.html) file and one "images" folder.

During the compression, some tools can put the index.html (or mail.html) file and the images folder in the same folder, which impacts the import of the images.

Make sure that they are no additional folders. Here is how it goes on Mac OS:

b) Invalid file names in your ZIP file

When creating ZIP files, the images must be in the sub-folder of your ZIP file. If the “images” file is not named correctly, they will not be displayed in your template.

Here is how to resolve this issue:

When creating ZIP files, the images must be in the sub-folder of your ZIP file.

1. Unzip the .ZIP file that contains the HTML email.

2. Rename the image file to images (it doesn't work without the "s")

3. Zip up the files

4. Upload the file

c) Invalid image names in your image file

In the HTML code of the template, each image should be referred to by its name and sub-folder. If the images mentioned in the HTML code do not have the same name as those in the "images" file, Batch will not link them and they will not be displayed in your email template.

How to add a pre-header to your email template

To take control of your email pre-headers, you can effortlessly add a pre-header directly within your template.

To do so:

1. Edit the HTML file of your template directly on the Batch Dashboard by clicking on Edit email:

1. Add a hidden div to the top of the body of the email with the following code:

By incorporating this step, you can customize your pre-header text, providing a concise and compelling summary that encourages recipients to open and engage with your emails.

Best Practices for Dark Mode Email Design

1. Use Transparent PNGs

   Avoid images with white backgrounds. Transparent PNGs prevent white boxes from appearing around logos and visuals when dark mode is enabled.

2. High Contrast Best Practices

   Make sure your text and background combinations remain accessible in both modes. Email Composer makes it easy to fine-tune colors for better readability.

3. Add Shadows and Borders

   On dark backgrounds, some visuals may blend in too much. Adding subtle shadows or borders helps them stand out.

4. Prefer HTML Text Over Images

   Text blocks in Email Composer adapt to dark mode and stay sharp. Avoid saving important copy as images, since it can distort or become unreadable.

5. Avoid Pure Black and Pure White

   Colors like #000 and #fff are often automatically changed by clients. Instead, use dark gray or off-white for a more consistent result.

6. Test With Dark Backgrounds

   Use previews in the Email Composer to see how your email behaves in dark mode. This step helps catch issues early and ensures consistency across devices.

Dark mode is here to stay. By applying these practices directly in the Email Composer, you’ll make sure your campaigns remain readable, accessible, and visually consistent, no matter how or where they’re opened.

🚧 There is no one-size-fits-all solution. The image you attached to your notification may be displayed differently based on:

• Your users' OS. iOS, Android, Mac OS and Windows manage notification images differently. Your image may be displayed correctly on iOS and cropped on Android for example.

• Your users' screen size.

• Your users' browser (for web push notifications only).

Using an Image Containing Text

Ensure the text is in the middle of the image or as far as possible from the image borders:

Last but not least, focus on the text of your notification and avoid including too many details in your image. Users will read the text of the notification before seeing the image.

Using a Portrait Image

Batch allows you to use a portrait image in your push campaigns, though we do not recommend it as both iOS and Android will display the image in full width, cropping the top and the bottom of your image.

Testing Your Image

You can click the "Send a test" button in the campaign editor to see how your message looks on your device (more information here: iOS / Android / Web Browser).

Understanding How Images Are Displayed

iOS/Android

On iOS and Android, the image attachment is displayed as a square thumbnail when the notification is collapsed. Your image will be cropped on the right and left-hand sides.

• IOS: with a force touch or by sliding the notification and clicking the "Display" button. iOS will display the image at full width.

• Android: by swiping down the notification.

Web Push Notifications

Users can receive web push notifications on desktop and mobile if they turned on push notifications from a compatible browser (e.g. Google Chrome, Mozilla Firefox, Microsoft Edge or any other Chromium-based browser).

On Android, web push notifications look like any other mobile notifications.

On desktop, the aspect of the notifications may change depending on your users' browser and OS:

• Windows: Images will be displayed exclusively for Chrome. This also applies to any Chromium-based browser (e.g. Microsoft Edge, etc). Firefox uses a custom format to display push notifications. That format doesn't support images yet.

• MacOS: Recent versions of Chrome, Firefox and Microsoft Edge use MacOS' native notification format, which doesn't support images yet.

You can easily preview your message on different OS' and browsers from the campaign editor to make sure it will be displayed correctly:

From the Content tab and Blocks, you will be able to drag the Text feature to the layout and drop it on your email:

Write your text

Once you create the block:

1. Click on it and start to add your text.

2. Set up your text parameters on the settings panel on the left.

3. Use all the properties displayed on the top of the composer to edit your text.

Alternate text

If the image doesn't appear, you can choose to add an alternate text.

You can add this text directly in the Email composer, by clicking on the image:

Add links

Once you added your text:

1. Click to edit.

2. Highlight the text you want to make clickable.

3. Click the chain link.

4. Choose the type of link you want to add.

5. Paste your URL into the box.

6. You're done!

Learn how to handle link tracking in emails on our dedicated article.

• Upload an image from your computer

You can then drag and drop the image you want to use for your campaign or upload it from your computer by clicking the arrow and selecting the image of your choice on your files.

• Use an external link

You can use an image URL link that you host on your end. In the External link field, copy the link to your image.

Personalization

Once your image is selected, you can apply different effects to it. Indeed, you can:

• Choose the orientation (vertical, square, horizontal)

• Adjust the height of the picture

• Apply different filters to your visual

Then, if you want to place text on the banner image, click on the "T" button in the toolbar at the top of the template. Draw your text zone, and then replace the caption with yours. You can set the font size, color, and type:

Finally, you can add images to your banner and place them where they suit you:

By uploading a .CSV or .TXT file to Batch from the dashboard Profiles → Audiences tab.

The dashboard will automatically display the number of IDs that match your audience:

2. Exclude it from your targeting

In your campaign/automation creation form, in the Segmentation part, click on Use audience:

Choose the audience you want to exclude in the dropdown menu:

Select "contains none of", so that the segmentation now excludes the audience you picked:

You can exclude as many audiences as you want:

You can now exclude audiences from your campaigns targeting! ✨

Using the Email address

The Email address allows you to send targeted and relevant communications to your customers.

Batch supports importing your known email subscribers in two ways:

• Profile API

• Using our mobile SDKs iOS/Android

Using the Custom ID

As the Custom ID is a native field you can use to attach a unique user ID to one or several devices.

If you have Batch’s web or mobile SDK deployed, it is assigned to your users when they are connected to their customer account.

Using the Installation ID

The Installation ID is an anonymous ID generated by Batch the first time users open your app or your website, whether they opt-in for push notifications or not. That ID changes each time users reinstall your app.

Once you get your Custom ID or Installation ID, you can use it to find the user's profile.

In the upper section, you'll have a profile overview, with information such as the user's location, his opt-in status on all channels, as well as the platforms he is on:

In the lower section, you'll get information on the user's attributes, and the different events he triggered:

When an action is required by your users, you can emphasize that by adding an image containing a word, an action, or a question that will guide your users in doing what is needed.

Inform your users

Add valuable information to your message, such as the product category related to the offer, the article being discussed, or new content that is finally available.

Increase your user retention

Images help users visualize the presented content, enhancing their understanding and improving the overall user experience.

Control your narrative

Selecting the right image style — whether it is grainy or crisp, colorful or monochrome, illustrations or photos — enhances your branding and sets you apart from competitors. When people can easily recognize your brand, it ensures they remember you, signifying a lasting impact on them.

In the Folder field, there are two ways of saving your module:

• Email: the module will be only available on the campaign you are working on.

• Project: the module will be found for all the campaigns you create.

Saved modules

Once your modules are saved, you can find all of them in the Content > Module part on the right. Choose the one you want and drag it to its place on your new email:

You can track your opt-out users in the Analytics → Reach tab:

Batch can only have information about what's going on in the app. When a user installs and opens the app, we receive a push token from Apple/Google that allows us to communicate with them:

If the user opt-outs from notifications in the device settings, no information is provided to Batch servers. The actual opt-in status will be updated only when the user opens the app again. Likewise, we do not know in real time when an opt-out user activates push notifications again.

Therefore the Batch database is potentially always "out of synchronization" with reality regarding the opt-in status.

Batch always targets all opt-in and opt-out tokens: it allows us to update the state of the tokens, clean the database and recover the users who would have reactivated the notifications. The notification will never be displayed to an actual opt-out user, it will be blocked by the device.

App uninstalls

There are two pages where you can track your app uninstalls:

• Analytics → Audience

• Push → Campaign statistics → Undelivered

In this example, we report that 509 users, who were targeted by the push, did not receive it because they uninstalled the application. Uninstalls concern both opt-in and opt-out users, as long as they were targeted by the campaign.

Unlike opt-outs, we receive by return loop the uninstalls that took place between the sending of the last campaign and the campaign of the day. This loop occurs only once a campaign has been sent. That's why you will see uninstalls only on days when a push has effectively been sent.

Knowing that, do not hesitate to send your push notifications a little earlier than most other apps. For instance, you can schedule your push notification at 11:55 AM to make sure your users receive it before they receive alerts from other apps at noon sharp. Or you can also decide to send your notification at 12:02 AM instead of noon sharp ti stay on top of the notification pile.

2. Make sure you pick the right scheduling mode

There are two main ways to schedule orchestrations in Batch:

A. Campaign or Recurring Automation

You can pick between two options when scheduling a simple or recurring push campaign:

• Profile's local time: This option lets you send a push notification that will be received based on the user's timezone, at the same hour in every country. This ensures that marketing efforts target your users at a uniform time.

• Universal time (UTC): This option allows you to send a push notification to your users at a specific UTC regardless of their location. Every user will receive the message at the same time.

B. Trigger Automation

You can try out different sending times in our Automation Builder thanks to the Random split feature:

• Click the "+" sign to add a random split and up to 4 variants (you can choose the ratio between them).

• Select your preferred delay for each option by clicking the "+" sign and adding a Delay. You can set it for a specific duration or wait for a certain time.

You can check the result of each variant in the Analytics tab of your automation:

3. Send your notifications when users are most likely to engage with your app/website

Go to Analytics > Push > More > iOS / Android / Web and set the dates for 3 days maximum. This way, you will be able to see the analytics, hour by hour. The "Starts" chart (blue) shows when your app is most opened by your users (in UTC):

Check your app's peak hours—these are the times when users naturally engage the most. This indicates they are available and more likely to open your notifications during that period.

4. Check the influenced opens

If you notice more influenced opens than direct opens, it may indicate that your push campaign was sent too early. Instead of opening the notification immediately, users opened your app within three hours after receiving it.

To check the ratio of direct to influenced opens, visit the campaign's analytics section:

5. Match the send time with the audience and the content

General timing strategies are useful, but always adapt them to your audience and the type of content you're sending.

• Media apps: Perform best with early weekday morning pushes.

• Fashion, lifestyle, and entertainment apps: See higher engagement in the late afternoon or on weekends.

2. Find information on your device

On the dashboard, go to Data > Find Profile, and paste your ID (with the correct ID type selected):

In the Platforms section, find your device and click on Inspect 👇

Then click on Inspect in app debug:

3. Send a test notification

You can send a test notification from 3 different places:

a) From the debug tool

In case you just need to test your integration, you can use the Send test push button, and Batch will send a generic message with an image to your device:

b) From the list of registered test devices

You can see the list of all of the registered test deices from Settings > Push Settings. This is helpful to check if the token of your saved devices is still valid, and delete them if it's not the case:

c) From the campaign editor

You can send test notifications to your device to see how your campaign looks from the campaign editor.

Click on Send a Test and add your Installation ID or Custom ID in the corresponding field, then hit Send test.

Click ⚙️ to select your device in the saved devices, or copy your Installation ID in the corresponding field. Hit Send a test.

This may happen due to:

• Formatting issues: The IDs included in your audience are not formatted correctly (e.g. extra space, lower/upper case issue, extra semicolon, etc).

• The wrong type of IDs: The type of IDs included in your audience doesn't match the unique user IDs sent to Batch by the app as custom user IDs.

• Opt-out installs: None of your targeted IDs matches an opt-in install.

• Wrong "Audience type": Make sure you have selected the correct "audience type" when you uploaded your audience (e.g. Custom User ID, Installation ID).

You can prevent these issues by using the preview displayed by Batch dashboard when you upload your audience to double-check what will be imported:

Also, please note that the estimate has been designed for high volumes of profiles. As a consequence, it is not precise for small amounts of IDs. Even if the estimate shows 0 Profiles, your campaign may actually target less than 10 users.

My audience is matching fewer profiles than IDs in my audience

This may happen because:

• Users may not have the app: Some of the users you targeted in the audience may not have installed the app or may have uninstalled the app.

• Users may not have turned on notifications: The IDs included in your audience may match users who did not turn on push notifications and, as a consequence, don't have a token.

• ID not collected: Some of the custom user IDs you targeted in your audience may match users who logged out from the app. As a consequence, Batch cannot find any installs attached to specific user IDs. If your audience contains advertising IDs, Batch may not be able to collect the advertising ID of your users (e.g. limited ad tracking turned on or app limitation).

My audience is matching more profiles than IDs in my audience

This may happen in the following cases:

• Multiple installs: If your audience targets Custom User IDs, Batch may have more than one opt-in install per ID. This usually happens when users install the app on different devices and log into the same user account in the app.

• Outdated tokens for reinstalls: Batch may keep temporarily several tokens for users who reinstall the app, though some of them may be invalid. This happens because Batch gets feedback on the validity of the tokens in an asynchronous way, every time you target all your user base with a push campaign. So the user's profile still get a push token.

Edit the block

By clicking the new social block, the editing window opens on the left side of your screen:

Choosing social media

You can add more social media or choose different ones by clicking on the ➕ icon:

Then select through several options the look of the social media icons and the size of it.

There, you have two choices:

• Generic icons

A long list of designs with known icons is ready to be used! Once you have chosen the right one, you can then set up the link to your social media accounts:

• Custom icons

You may want to personalize these icons in order, for example, to add the icon of your brand and the link to your website. Choose the Custom icons line in the list:

Or add a new Custom icon:

You'll be able to add and edit your own icon image and a link to any website! Check our documentation if you need help in editing your image.

Edit icons

Once your icons are in the right order, it's time to edit it!

Activate the More button to see all the settings. There, insert the appropriate URL links; enter the title and the alternative text:

And finally, the general setting of the block such as alignment, padding, and spacing:

Footer

The link to your social media account is generally in the footer of your email, next to the unsubscribe link and contact details. See how to add an unsubscribe link for more details.

Here is a breakdown of every browser's character limit per OS:

Windows 10+

Chrome and Chromium-based browsers

Google Chrome, Microsoft Edge, Opera and other Chromium-based browsers use the same Windows 10 native format for notifications. Notifications not opened yet will be placed in the notification center.

• Title: Up to 70 characters (space included), split into two lines of text.

• Body: Up to 140 characters (space included), split into four lines of text.

• Image: Displayed as a landscape image both when the notification is received and stored in the notification center.

Firefox

Firefox uses a non-native format on Windows. As a result, the content is displayed differently, and notifications are not stored in the notification center.

• Title: Up to 50 characters (space included), on one line of text.

• Body: Up to 200 characters (space included), split into four lines of text.

• Image: Firefox doesn't display images in notifications.

MacOS

Firefox, Chrome, and other Chromium-based browsers use MacOS' native notification format. Unread notifications are stored in the notification centre.

• Title: Up to 35 characters (space included), on one line of text.

• Body: Up to 40 characters (space included), on one line of text. MacOS displays two lines of text for each notification in the notifications centre (75 characters).

• Image: MacOS doesn't display images in notifications.

Android

Notifications use Android's native format, used by apps too. New notifications will be displayed on the locked screen of the device and in the notification centre.

• Title: Up to 40 characters (space included), on one line of text.

• Body: Android will display one line of text when notifications are collapsed (around 50 characters). The message will be entirely displayed once unfolded.

• Image: Displayed as a landscape image. Users need to expand the notification to see the image. Please note that Android will only display one line of text in the body of your notification if you include an image.

iOS

Batch allows you to display a badge in the top right corner of your iOS app icon when your users receive a new notification. Here is how it looks:

You can add a badge to your notifications on iOS:

• From the Dashboard

• Via the Transactional or Campaigns API.

From the Dashboard

You set a badge count (e.g. 99) by copying/pasting the following code in Advanced settings > Payload:

Using the Campaigns API

This can be easily achieved by adding the same code to the custom_payload field. Here is how it looks for a new campaign:

Find more information on how to use our API in the dedicated documentation.

Incrementing the badge value

iOS allows you to set a specific value for the badge count (e.g. 0, 3, 99) but doesn’t provide any mechanics to automatically increment or decrement the value displayed on your app icon when a notification is received.

Send your campaigns at the best time using the best delivery option

4 options are available on Batch: Now, Scheduled, Recurring, or Trigger.

"Now" and "Scheduled" campaigns are in the Campaigns tab:

You can find "Recurring" and "Omnichannel Trigger" orchestrations in the Automations tab:

Selecting the optimal timing for push notifications can enhance traffic and increase engagement. When is the right time? Find some tips in our article: What is the best time to send push notifications?

Adapt your wording to the audience

Are you wondering if you should use a formal or familiar tone in your mobile communication? Learn how to use the A/B test feature in our dedicated article!

In addition to the message itself, you can also A/B test images, deeplinks, and emojis!

Use emojis

Emojis are important, but can also be overwhelming. Here are a few examples of how to use emojis wisely in your messages.

Discover all the best practices in our dedicated article!

Attach an image to your push

You can easily improve your open rates by adding an image, GIF, or video to your push notification.

You do not know how to add images, videos, or GIFs to your push? Here is the article you need: How can I attach an image, an audio, a GIF or a video to a push notification?

Personalize your messages using Dynamic Content

You can personalize your push notifications from the campaign editor using the data you have collected from your users. For instance, you can customize the name, the city, or the amount left in the pot's user.

This feature is also available for In-App messages and works in a very similar way.

Here is our article dedicated to in-app dynamic content: How to personalize the content of my in-app message?

You can also use dedicated DNS debug tools like EmailStruff's DNS tool.

→ SPF:

• Strict alignment: Type your subdomain name in the TXT field of the tool (subdomain.domain.com)

• Relaxed alignment: Type your bounce subdomain name in the TXT field of the tool (bounce.subdomain.domain.com)

→ DKIM

Type the selector + your subdomain name in the TXT field of the tool (scphxxxx._domainkey.subdomain.domain.fr).

→ DMARC

Type _dmarc.subdomain.domain.com in the TXT field of the tool to check your DMARC record.

Dig Command

Alternatively, you can use the dig command following the same logic:

Common Issues with Strict Alignment

When operating in strict alignment mode, the presence of TXT entries within the same domain often disrupts email authentication.

The most frequent cause is a Google Postmaster Tools verification code being incorrectly placed at the subdomain level. Ensure that you only verify your root domain with Google Postmaster Tools.

Subsequent subdomains do not require individual verification to be added to the tool's monitoring.

Simply write javascript: in the URL bar of your website and copy and paste the following code:

batchSDK('ui.showPublicIdentifiers')

Through the Inspect window

Open your website, right-click somewhere on the page and select Inspect or Inspect Element in the context menu that appears.

Once you have the developer tools open, click the Console tab, paste the following code:

For both methods, Batch's SDK will then return your identifiers:

Ensure that:

• Subscribed to notifications? is set to Yes ✅

• The Registration token field is not empty ✅

In case you just need to test your integration, you can use the Send test push button, and Batch will send a generic message with an image to your device:

b) From the list of registered test devices

You can see the list of all of the registered test devices from Settings > Push Settings. This is helpful to check if the token of your saved devices is still valid, and delete them if it's not the case:

c) From the campaign editor

You can send test notifications to your device to see how your campaign looks from the campaign editor.

Click on Send a Test and add your Installation ID or Custom ID in the corresponding field, then hit Send test:

Click ⚙️ to select your device in the saved devices, or copy your Installation ID in the corresponding field. Hit Send a test:

Right-click anywhere on your website, then click Inspect:

Then click on the Application tab and go to IndexedDB > BatchWebPush > BatchKVData:

You should then be able to get your Installation ID, for example here: 1bb71252-2b58-4285-9fe0-321c37ce5730.

b. Firefox

Right-click anywhere on your website, then click Inspect Element:

Go to Storage > Indexed DB > Your Website URL > BatchKVData:

Your installation ID is displayed on the first line, for example here: 61b11de8-5cc9-454f-a0b3-162f740b53a.

c. Safari

Right-click anywhere on your website, then click Inspect Element:

Then click on the Storage tab and go to Indexed Databases > BatchWebPush > BatchKVData:

You should then be able to get your Installation ID, for example here: ebccf486-961f-403e-97a3-39daf001f98c.

Emojis are fun, but they can help you get better at communicating with your audience. Use them to:

• Improve your open rate: Adding visual elements such as emojis impact positively your user attention. It has been proven that emojis increase the visibility of your message and thus your open rate by 80% (average between iOS and Android).

• Increase your user retention: When used as a tool of classification for your campaign, emojis help your users to know what subject is covered by your message. You now have a clearer way to communicate with your audience.

• Shorten your messages: Push notifications are short messages. Every character matters, especially in the title of your message. When it feels right, substitute words for emojis.

• Be more impactful: Users have a very short attention span. Train your audience to associate an emoji with a type of content when they see it.

• Think outside the box: Get creative by adding disruptive elements to your message that will make it stand out and differ from your competitors.

How to Use Emojis?

Step 1: Adding Emojis to Your Message

Here are all the existing methods to insert emoji in your title and body text:

• Windows 10+: Simply press the Windows key + the period button to display Windows's emoji keyboard on Windows 10. In case you are using an older version of Windows, you can copy-paste an emoji from Emojipedia: iOS / Android / Windows.

• Mac: press CTRL + CMD + Space to display the emoji keyboard and pick an emoji.

• Chrome 68+: Right-click any text field and select "Emoji" or "Emoji & Symbols".

• Using a browser extension: You can use the extension on Firefox or by EmojiOne on Chrome.

• Using Emojipedia: Or simply copy/paste emojis from .

Step 2: Use Them Wisely

Where Should I Add Emojis?

Emojis serve various purposes and can be placed in different positions:

• In the title: This is the most effective way to attract the attention of your users. You can use an emoji to inform them when a live show starts or present the topic of the message.

• In the body: As push notifications have to be short, you can easily replace a word with an emoji. This will allow you to save space, emphasize your communication and encourage users to open the notification and know more about your app.

• In the button of your In-App message: This space is also a good one to use emojis if you want to boost the performance of your campaign.

• In your web push: As with mobile campaigns, you can add emojis to your web push campaigns. We recommend that you put the emoji at the beginning of the push body (so that it is seen and attracts the eye).

How Many Emojis Should I Use?

Feel free to use as many emojis as you like, as long as your message remains clear, understandable, or funny—depending on your goal.

Which Emojis Should I Use?

There is a large variety of emojis you can use. When it comes to picking the right emoji for the right meaning, the best solution is to stay relevant:

• When talking about sport/food/piece of clothing: Use emojis that embody the theme or the action ( 🥊, 🍔, 🎩, 🤳, etc).

• When talking about a live event: Use emojis that illustrate the upcoming event or a recording (🔴, 🔜, ▶️, 🆙, etc).

• When explaining a feature/service: Use emojis inviting the users to know more by opening the message (📍, ℹ️, ✅, 🆕, etc).

• When suggesting to open the app: Use emojis that show that there is more to discover in the app (👉, ➡️, 🔥, ⏳, etc).

Can I Use All the Available Emojis?

Depending on your industry, some emojis may be inappropriate or confusing for your audience. Cultural context is key when crafting your message. For example, 🙏 can be interpreted as a prayer or a gesture of gratitude, while 🙃 is often seen as playful or sarcastic but is also used in text-flirting.

Also note that some emojis may be sex-correlated such as 📯, 🍆, 🍑, 💦, 🍌.

How Can I Be Sure Emojis Will Improve My Campaign Performance?

If you haven't used emojis with your audience before, try Batch's A/B testing module to measure their impact on your campaign's performance. Run the test over a period of time and analyze how your audience responds.

Click on "A/B Testing" at the top right corner to turn the A/B Test on.

There are four actions every marketer should take to grow their push opt-in base and make sure users don't disable notifications over time:

1. Improve the onboarding experience in your app, to explain the value behind push notifications before triggering the system opt-in prompt.

2. Set up a re-optin campaign using Batch In-App messages

3. Leverage iOS' provisional authorization

4. Allow opt-in users to adjust their push preferences from the app

1. Improving your onboarding

On iOS and Android (starting from Android 13), the "native" request for push authorization can only be displayed once. For this reason, and following Apple and Google recommendations, we advise you to develop a pre-permission screen that can be displayed:

• As an additional step, in your onboarding tutorial

• On the first session

• Or/and after a meaningful action: login, order confirmation, service subscription, etc.

Here is how a pre-permission prompt looks like:

If users click the "Turn On notifications" buttons, they will see the system permission prompt that can only be displayed once.

From a technical point of view, here is what must be done:

• iOS: Simply call the BatchPush.requestNotificationAuthorization() method of Batch SDK when users click the right button on your pre-permission screen.

• Android: Make sure your app targets at least Android 13 (API 33) and you are using a recent version of Batch SDK (1.19.2 or higher). Then, call the Batch.Push.requestNotificationPermission(context) method when needed to trigger the push opt-in prompt.

2. Creating a push re-optin campaign

You can use Batch In-App messages to improve your push opt-in rate. Indeed, In-App messages can be displayed to every user, whether they are opt-in or opt-out to push notifications. ​ Our platform allows you to segment your audience according to the push opt-in status (true or false) by using the native attribute "Push opted-in":

Then, you can target opt-out users via our In-App messaging technology to suggest users to subscribe / re-subscribe to push notifications, by setting up a re-optin campaign:

3. Leveraging iOS' provisional push authorization

On iOS 12 (and higher), the Provisional Authorisation feature allows you to send push notifications to users who haven't displayed the system permission prompt yet.

Users will have a chance to fully turn on push notifications for your app directly from the notification they received:

4. Allowing users to customize their push preferences

We observe a better opt-in rate for apps that have:

• A thematic opt-in demand

• A notification preferences page in the app allowing users to manage themselves their push preferences by theme.

This makes sure users can simply disable a category of alerts instead of disabling push notifications for the entire app from the system settings.

Creating a re-opt-in automation using In-App messages

Getting opt-out users to turn on push notifications is key to re-engaging your audience, especially in the first 7 days following the app install. This can be done in a couple of minutes using an In-App message.

Batch In-App Messages are a powerful tool to encourage opt-out users to enable push notifications. These In-App automations allow you to efficiently invite such users back by suggesting they turn on notifications. With Batch's advanced targeting and personalization features, you can display these messages at the right moment and context, following a meaningful action.

• Media: When users reach the end of an article, share or save an article, create or log into their account, get a premium subscription, etc.

• Retail: When users add an item to their wish list, add a favorite brand, or after the checkout, to be sure they get alerts on their delivery.

• Etc.

Pre-requisites

Here is the list of prerequisites for setting up your opt-in automation:

• SDK: On Android, make sure your app includes the 1.19.2 version of Batch SDK (or higher). Your Android app must also target, at least, Android 13 (API 33). Install the latest version of your app and find your install in the debug tool (Settings → Debug) to check the current version of Batch's SDK used in your app.

• Tagging plan: Make sure all the user actions you plan on using as triggers for your In-App message are tagged as events with Batch's SDK. On Batch's dashboard, go to Profiles → Custom Data → Events (or Settings → Custom Data → Events if you are using our Mobile Engagement Platform) to check the list of events available as trigger events. If the action needed is missing, your developers will need to tag it following Batch documentation: iOS / Android / Cordova / Flutter / React Native.

Automation creation

You will need to create an In-App automation using the following instructions:

1. Targeting

Add the "Push opted-in" condition to your targeting and set it to "No" to target exclusively users who did not turn on notifications. We recommend you turn on the "Re-evaluate targeting just before display" option to improve your In-App automation behavior.

On Android, make sure you add a condition to target exclusively Android 13 (and higher) users:

2. Trigger conditions

Here is where you choose when the re-opt-in automation will be triggered:

• Display event: We recommend using a custom event linked to a specific action sent to Batch through your tagging plan. Select an event triggered after an engaging action from the user: signing up or logging in to your app, adding an item to the cart, etc.

• Capping: This feature helps you to control marketing pressure. In the example below, we have set a capping of 2 and a 72 hours grace period. A user will see the In-App message 2 times maximum, with a delay of 3 days minimum.

3. Message edition

Then, edit your message:

1. Select the In-App theme you want to use, in the format adapted for your use case (e.g., banner, modal, full screen, image, or webview). If you do not have a theme yet, create one from Settings → Theme → New theme.

2. Add wording for the text and the buttons of your message, according to your theme.

3. Configure the button action: Choose the "Smart push re-optin" option as the primary action. You can add another action for advanced use cases (e.g., track an event when users click "later" to show them another In-App message later.)

Clicking a button linked to the "Smart push re-optin" action will have different outcomes based on your users.

• If users never triggered the push permission prompt, → Batch will trigger the push permission prompt, allowing users to turn on push notifications.

• If users have already triggered the push permission prompt and didn't turn on notifications → Batch will direct users to the system settings, in the section dedicated to your app, where users will be able to turn on push notifications.

4. Testing the automation

To test a re-opt-in automation, your installation has to be opt-out. In this state, you can’t receive the test push via the Send a test feature. That’s why you need to create a Custom Audience with your Installation ID (See the guides for iOS and Android).

Once your Custom Audience is ready and attached to your test automation, you can activate it.

Then, you can trigger the display event of your In-App automation, and you must see your In-App message, and you can click on the buttons.

Using dynamic content wisely in your messages

Dynamic messages can be very handful to build user loyalty by creating bonds and addressing users in a personalized way.

It will definitely help you make a difference in the eye of your audience.

Here are some examples :

In-app feature

The built-in actions are Batch actions associated to a call-to-action of an In-App message, you just need to have the In-App feature enabled to use this feature. When creating an automation, they allow you to set up actions beyond the different actions associated to a button.

How to do it?

Creation of automation A: link your buttons to events

In order to be able to retarget users who have interacted with a previous In-App automation, you need to track events on your In-App automation A:

1. When editing your first In-App automation, you will have to associate your button with an event. To do this, choose the button of your choice (Dismiss, Deeplink, Clipboard, Rating...) then click on "Add secondary action" > "Track event".

2. Configure your event: select an already created event or create a new one, you can also add a Label for extra information like the name of the campaign or button.

3. You can also associate your second button, if you have defined one, to another event

4. Your button is now linked to an event (in the example below "Later"), which will be tracked once your users click on it.

Custom event activation

Once the first campaign has been sent and the first users have interacted with it, the event you have configured will show up in your custom data. It is necessary to activate it in your Settings > Custom data in order to view them on the dashboard when creating the second In-App automation.

Creation of campaign B: retarget

Now send a second In-App automation to users who interacted with the In-App automation A

To do so, you just have to adjust the targeting by choosing exactly the same event defined in campaign A. You will be able to decide to target or exclude the users who interacted with the buttons of your campaign A:

Use case: retarget users who have not copied a promotional code

Your campaign A could be an In-App message with a promotional code, in the case below, the first button allows the user to copy/paste the code "PROMO10" and redirects to the page where the code can be used.

The second button of this In-App message indicating "Maybe later" allows the user to simply close the message. However, this button is in fact linked to an event via the "Track event" functionality, so all users who click on "Maybe later" will be linked to an event in Batch:

Below, we see that after clicking on "Track event" in order to link an event to the dismiss button "Maybe later", it is necessary to configure this event. You have to name it and give it a label if you want:

Then, in this example, once the event is brought up in Batch following the first clicks of your users on the dismiss button of the In-App message, it will be possible with campaign B to retarget all the users who clicked on "Maybe later" in order to offer them a new (or the same) promotional offer for example!

Why Use Separate Subdomains Instead of a Root Domain?

Most mailbox providers track the reputation of each subdomain separately. Think of it like having different phone numbers for different departments in your company—each builds its own reputation based on how it's used.

We strongly recommend using dedicated subdomains for different email types—particularly separating transactional emails (e.g. password resets, receipts, account notifications) from marketing emails (e.g. newsletters, promotional campaigns).

Here is how a typical email setup looks like: