This guide presents the list of available elements to create an automated campaign. This list can also be helpful if you want to create a reusable template or a campaign starting from scratch, adapt a template provided by DI or modify one of you existing campaigns. A campaign must, at the minimum, contain a trigger and an action. The elements have only one entry point and most have only one exit point. An exit point determines the continuation of the campaign.
Triggers
The trigger is the starting point of an automated campaign. It's an event that triggers the automation.
Example: Use an opt-in form to trigger a welcome campaign.
| Recurring | Launches the campaign repeatedly, according to the selected frequency. |
| Dates | Launches the campaign on the dates and times indicated. |
| After imports | Launches the campaign after each import of contacts into the project, either automatically or on-demand. |
| Manual launch | Allows you to launch the campaign manually. |
| Process and API | Allows you to launch the campaign for one contact at a time, using the contact's profile, web services or a customized process. |
| Contact creation | Launches the campaign when a contact is created in the project. |
| Contact update | Launches the campaign when a contact is updated. |
| Contact opt-in | Launches the campaign when a contact subscribes. |
| Contact opt-out | Launches the campaign when a contact unsubscribes. |
| Profiling table | Launches the campaign when data is added to or modified in a profiling table. |
| Visited pages | Launches the campaign when a contact visits one or more web pages from a website that is configured with Journey. |
| Viewed products | Launches the campaign when a contact consults one or more products (available only if you have the e-commerce module). |
| Abandoned carts | Launches the campaign when a contact is engaged in a buying process but abandons his shopping cart (available only if you have the e-commerce module) |
Actions
An action indicates what must be executed when the campaign gets to this element.
Example: Send a reminder for a promotion.
| Send an email | Sends an email to targeted contacts. |
| Send an SMS | Sends an SMS to targeted contacts. |
Send a web push | Sends a web push notification to targeted contacts. |
| Export contacts | Extracts data according to a defined selection. *To use this action, an SFTP server must have been configured for your account beforehand (see Configuring an SFTP Server). |
| Update contacts | Changes the value of a field in the contact profile. *Only general fields are available; administrative and subscription fields cannot be modified by this action, nor can those that are part of the unique key. |
| Unsubscribe contacts | Allows you to unsubscribe or deactivate contacts. |
| Grant promo code | Allows you to grant a promo codes from a promo code lot previously created. You must create an email and integrate a promo code block into that email. |
| Postal sending | Exports the list of contacts who are eligible for the postal communication type. |
| Postal update | Exports a file with contacts to remove from the postal list or a file with updated data on contacts who are eligible for the postal communication type. |
Delays
A delay indicates a waiting period before moving on to the next element.
Example: Use a delay to follow up with a contact who did not answer your subscription invitation (by combining other elements, such as a condition).
| Delay - Period | Indicates the time to wait for the next action, according to a specified period (minutes, hours or weeks). |
| Delay - Weekdays | Indicates the time to wait for the next action, according to the next week's day specified. |
| Approbation | To approve the sending of an email in 2 steps. You must activate the "Prepare sending and request approval" option in a "Send an email" action. You won't see this option if you use Send Time Optimization since it's not compatible. |
Conditions
Conditions are used to select the contacts that meet or do not meet the defined criteria.
Conditions have 2 exit points (a true for a met condition and a false for a not met condition). For example, the condition could indicate if the contact is a member (true) or not (false).
True = Purple exit point
False = Grey exit point
| Contact data | Verifies if the contact meets the condition based on profile data or in a relational table. |
| Groups (Segments) | Targets contacts that are included in one or several groups. |
| Multiple conditions | Allows you to define several conditions. |
| Personas | Targets the contacts that correspond to one or several personas. *To use this condition, you must have created personas. |
| Engagement | Targets contacts who have interacted or did not interact with at least one email from your project. |
| *Delivery | Selects the contacts to whom a message from the ongoing campaign has been successfully delivered. *Place a delay before this condition to allow time for recipients to interact with your message. |
| *Opens | Selects the contacts who opened a message selected from the ongoing campaign. *Place a delay before this condition to allow time for recipients to interact with your message. |
| *Clicks | Selects contacts who have clicked on one or several links in a message sent in the ongoing campaign. *Place a delay before this condition to allow time for recipients to interact with your message. |
| *Opt-out | Selects contacts who unsubscribed from a communication type using an opt-out link in a message sent in the ongoing campaign. |
| *Spam complaints | Selects the contacts that have made a spam complaint related to a sending from the ongoing campaign. |
| Remove duplicates | Filters contacts with the same contact data (email or phone number) and keeps the contact with most recent or the least recent. |
*These conditions are part of the conditions on send, and must absolutely be placed after a message has been sent or after a delay.
Splits
Splits are used to distribute contacts in different scenarios and test different campaign variations.
| A/X Split | To distribute all incoming contacts on the test variations (branches) randomly. When a winning variation is selected, incoming contact will be redirected to that winning variation. |
| A/X Test | To distribute a fraction of the targeted contacts on test variations (branches). When a winning variation is selected, the remaining contacts will be redirected to that winning variation. For example, if you have a variation A (10%) and a variation B (10%), the remaining contacts (80%) will be redirected to the winning variation. |
| Contact distribution | Generally used to distribute contacts over time by adding a different delay for each exit point. Each purple exit point randomly redirects a certain maximum number of contacts. The grey exit point will catch the remaining contacts and redirects them to another branch. |
Endings
Campaign endings are used to determine whether or not the intended objectives have been achieved.
Example: An end could be a success if a contact clicked a link in a message or a failure if the contact did not click.
| Endings name | Description |
| Success | Corresponds to the desired result of your campaign. In the campaign report, you will see the success rate of the contacts that reached this result. |
| Abandon | Arbitrary end allowing you to define that the end is of the abandoned type. |
| Failure | Arbitrary end allowing you to define that the end is of the failure type. |
| Neutral | Arbitrary end allowing you to define that the end is neutral. |
Utilities
| Note | Allows you to add notes, like 'Post-it' notes, to the canvas to enhance collaboration or facilitate quick understanding. Examples: Add a note like "Inactive re-engagement branch" to identify a branch or "High engagement contacts targeting added. 2025.05.12 - Michele D." to coordinate with the team. |