Campaigns and Automations
General
With email channel come specific capabilities in campaigns and automations:
- Target or exclude specific email domains (eg.: gmail.com) for deliverability purposes.
- Decide to send an email to marketing opt-in emails (in most cases) but also to opted-out emails, for service messages such as data leak announcement or evolutions of terms & conditions that all customers must receive.
- Benefit from automatic deduplication at sending time: avoid sending the same email several times to the same email address if several profiles have the same email address.
- Have the Estimated reach excluding automatically email duplicates. Note that the total number of profiles displayed alongside the reach estimation will include all profiles, including duplicates.
Email Campaigns
Batch allows the creation of email campaigns, sent immediately or scheduled, with its Campaign Builder interface.
This article shows you how to target your first campaign:
Note that the Campaign Builder is omnichannel. Within the same creation interface, it is possible to setup email campaigns or push campaigns. Push campaigns can be mixed across iOS, Android and web channels.
Email Recurring Automations
Email recurring automations behaves almost like campaigns, with the following major difference : they can run automatically on a recurring basis.
Capping can also be applied to recurring automations to avoid overwhelming customers.
This article explains how to create a first recurring automation:
Email Trigger Automations
Trigger Automations are built thanks to our visual Automation Builder. The Automation Builder allows the building of multistep scenarios.
Trigger automations are triggered based on unitary events occurrence.
They can be controlled by the following capabilities:
- event filtering, to discard automation entrances based on event parameters,
- targeting, to only engage relevant audiences leveraging all the data stored in Batch data platform,
- cancel event step, to exit a person from the automation if certain events happen (eg. an order, a call to the support, etc.),
- capping, to have a maximum number of times a person can receive messages from the automation,
- grace period, too avoid too frequent automation entrances,
- parallel automations, to manage automations leveraging as an entrance criteria an ID that is not the custom user ID such as an order ID or a booking ID,
- delay, to control wait times between steps,
- splits, to create different branches in automations based on targetings leveraging profile information (Yes/No split) and algorithms (Random split). Splits can be chained,
- quiet hours, to control the time an automation is allowed to send messages. If the time is not optimal, the message can be skipped or sent at a better time.
The following articles shows you how to test and send a first trigger automation: