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.
- In terms of native attributes, you can use for targeting : Email optin, SMS optin, Last email click, Last email open, Email domain, Last visit, Has custom ID
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.
- quet days, to control the day an automation is allowed to send a message. If the time is not optimal, the message can be skipped or sent at a better day.
The following articles shows you how to test and send a first trigger automation:
Zoom on quiet days in Automation Builder:
When creating scenarios in the Automation Builder, you can now specify one or several days of the week when the profiles won’t receive any messages. Example : I don’t want profiles to receive messages during the weekend (on Saturday and Sunday). This feature gives you more power to send their content at times that are appropriate. In the French market, it makes it easier to comply with current SMS legislation. Indeed, under the LCEN (French law on confidence in the digital economy), sending commercial SMS messages is prohibited between 8pm and 10am, on Sundays and public holidays. The setting happen in the Trigger Event configuration, in the section "Quiet times". In this section you can:
- Enable Daily Quiet hours and define a time slot during which profiles will not receive messages.
- Enable Weekly Quiet Days and define one or several days during which profiles will not receive messages.
You can enable Quiet hours alone but Quiet days can only be enabled with Quiet days (to make sure we will not send the messages at midnight + 1 minute on the following day). When you activate Quiet hours / Quiet days, you need to define what is the required behavior for the messages that should have been sent during the Quiet time :
- Send at the next available time (ex: an sms message should have been sent on Sunday, which is a Quiet day, it will be sent in the first hour of the open message slot on Monday and, only after that, the user will continue their journey).
- Skip the message step and continue (ex : an sms message should have been sent on Sunday, which is a Quiet day, it will not be sent and the user continues their journey directly).
When Quiet Times (Quiet hours / Quiet days) are enabled, they are applied by default to all automation messages. However, it is possible to deactivate the Quiet time from the Advanced Settings of each Automation message. Note that: The Quiet times (Quiet hours / Quiet days) are based on users local times. If no local time can be found, the Quiet times will be based on the UTC Timezone.
Zoom on Wait until specific time and weekday in Automation Builder:
When creating scenarios in the Automation Builder, you can now specify at what time and on what day of the week the users must proceed to the next step thanks to a new “Wait until” Delay step.
- If the step following the “Wait until” is a message, then the users will receive it at the time and on the day entered in the “Wait until”. Example: I use the “Wait until” followed by a sms message to send it at 11am on Monday.
- If you use the Wait until feature with a Random split, clients can do AB testing on the sending time to see what sending time performs best. Example: Send the message at 7pm to 50% of the users entering the Automation and at 8pm to the other 50%.
Note that:
- Just like for any Delay step, cancellation events can be set. If one of these events is triggered by a user during the wait time, he will exit the automation.
- When quiet hours are enabled, we display the quiet hours in the delay step sidesheet to make sure clients take it into consideration when setting up a Wait until.
- The “Wait until” is based on users local times. If no local time can be found, the Wait until date will be based on the GMT timezone.