Recurring Automations

Recurring Automations are made for message sendings that repeat at specified intervals based on each Profile's local time or on Universal time (UTC). You can create Recurring Automations for each channel: Email, SMS and Push. They can be managed from the “Automations” tab of your dashboard.

Creating a Recurring Automation

To create a Recurring Automation, click on the “New Automation” button on the top right-hand corner of your Automations listing and select the channel you want to use to send your message.

Creating a Recurring Automation is similar to creating a Campaign, except for the Timing. Check Campaign documentation here.

• On a Recurring Automation, to define your Timing, you have to:

  • Set the day and time when you want the first occurrence of your message to be sent.

  • Set the day and time when you want to stop your Automation i.e. when you want the repetition to stop.

    • As for Campaigns, the day and time can be on the Profile's local time or on the Universal Time (UTC).

  • Set the frequency with which messages are sent.

    • The frequency has a minimum limit of 1 message per day and no maximum limit.

• If you want to limit the number of occurrences of a message a Profile will receive, you can use Capping.

  • When Capping is disabled, Profiles in your targeting will be able to receive the message on each occurrence i.e. each time the timing occurs.

  • When Capping is enabled, Profiles in your targeting will only be able to receive X occurrences of the message. X being the value you have set.

    • If a profile has several devices, then we will send X occurrences of the message per profile AND per device. For example, if you set the capping to 2 and a user targeted by your Automation has an iPhone and an iPad, they will receive 2 occurrences of the message on each of these devices.

Managing a Recurring Automation

Stopping a Running Orchestration

• A Recurring Automation can be stopped and relaunched as many times as necessary until the end date is reached.

• Sendings will resume on the sending date defined in the form and not immediately after the Automation is relaunched.

Modifying a Recurring Automation

• A Recurring Automation can be modified until the end date is reached.

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

• If your Automation 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.

• If you change the start date to within 24 hours of the first send, people will not receive the message again; they will receive a message on the next occurrence.

Deleting a Recurring Automation

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

Intelligent Warm-up mode

Intelligent Warm-up mode help you manage your email sender reputation by gradually increasing sending volumes in order to build trust with email providers.

You can define and manage the warm-up process with three key parameters:

• Initial Sending Volume: The volume for the first day's send (default: 500).

• Volume Increase Percentage: The percentage increase applied to the sending volume for each subsequent day (default: 50%).

• Engagement Selection Criteria: A single criterion used to target people from the least engaged to the most engaged. It creates an ordering based on a user attribute. Users without a value for the selected attribute are targeted last. Supported attributes are:

  • Date Attributes (e.g., last_email_open) are sorted by default from most recent to oldest.

  • Number (Float or Integer) Attributes (e.g., a custom scoring). The sort order is determined by you between descending or ascending. Integers are converted to floats for normalization before sorting.

The behaviors specific to the warm-up mode are as follows, the rest is identical to the functioning of Recurrings:

• Creation Blockers & Warnings: The system includes checks to prevent unsuitable warm-up plans:

  • Blocker (before launch): Warm-up duration less than 2 days or more than 89 days.

  • Warning: Volume increase percentage greater than 100%.

  • Warning (after launch): Warm-up duration more than 89 days. If certain criteria are modified during the warm-up process, it can result in a warm-up exceeding 89 days. In this context, we will not block saving the modifications, but the automation will stop after 89 days and the remaining tasks (sends) will be abandoned.

• Manual Intervention Allowed: You can manually intervene by modifying:

  • The daily increase percentage.

  • The engagement criteria.

  • The email content.

  • The targeting.

  • The ability to stop and resume the Automation.

• Restrictions (even before launch):

  • Timing cannot be based on Profile's local time (Global Time is enforced).

  • Capping setting is forced to 1 and occurrence is daily.

  • A/B testing is not allowed.

  • Replicating an IP warm-up orchestration is not allowed.

  • Stop/Rerun is blocked from the main listing (to enforce awareness of changes).

• Restrictions (after launch): Once the orchestration has started sending, the following cannot be changed:

  • Market/Transac subdomain.

  • Start date (unless the start date hasn't passed).

  • Initial sending volume.

• Data overload prevention:

  • A maximum of 4 Warm-up Automations can be running simultaneously across the same project.

Understanding Automations listing

The listing is common for Recurring Automations and Trigger Automations. All the Automations you have created since the project was created are available on the listing.

From the Automation listing you can:

• Filter the listing by:

  • Date: Filters out Automations that were active over the period.

  • Status: Draft, Running, 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 Orchestration.

    • Launch Automation.

    • Replicate.

    • Delete.

  • If Stopped:

    • Edit Orchestration.

    • Go to Analytics.

    • Launch Automation.

    • Replicate.

    • Delete.

  • If running:

    • Edit Orchestration.

    • Go to Analytics.

    • Stop Automation.

    • Replicate.

    • Delete.

  • If completed:

    • Go to Analytics.

    • Replicate.

    • Delete.

• Access key metrics:

  • Delivery: number of sent.

  • Interaction: percentage of opens.

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

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

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

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

  • First run: The date and time the Automation was run for the first time.

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

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

• Search a specific Automation.

What is explained on this page is focused on how Recurring Automations works for Email, SMS and Push v2 channels. For Push v1, the behavior is slighly similar with the main difference that it works by platform (iOS, Android, Web).