About custom scenarios

The creation of an automated marketing scenario lets you build a series of actions that occur based on specific conditions and that help you reach your marketing goals. It is possible to create a scenario from one of the various templates available, or to create one from scratch.

If you choose to use a template, the creation process is greatly simplified since steps are already configured, and the scenario frequency, time and targeted contacts are set. All that is left to do is to select the message to be sent for the various message-related actions in the scenario, and if so required, specify a few additional information to properly run the scenario. Once the scenario is created using a template, you can use it as is or add, edit, delete steps or elements as needed; the template will always remain the same. As for custom scenarios, all the steps need to be configured. To see the steps involved in the simplified approach, you might prefer reading Creating a Scenario Using a Template.

Here is an example of a common custom scenario:

 

 

 

 

 

 

 

Prerequisite
To be able to create scenarios, the Marketing Automation module must be activated for your account.
Access Path
> Campaigns > Marketing automation

How To

Select the scenario template
  1. In the Marketing automation page, click on Create a scenario.
  2. In the window presenting all the available templates, select the Custom scenario option to create a scenario from scratch and click Next.
List of possible launch options
          
Launch option
Description
Recurring
Scenario that is executed repetitively, as per a defined frequency.
Fixed dates
Scenario that is executed on the specified dates and times.
Manual
Scenario that is not executed automatically, but by a user via the scenario launch page, or via Web services.
For more information, see Launching a Scenario Manually .

Post import
Scenario that is executed each time contacts are imported into the project, either automatically or on demand.
By trigger
Scenario that is triggered by an action performed on your contact list or a given action performed by your contacts on your site.
  1. Click Next.
Define the triggering action (for triggered scenarios only)

If you want to create a scenario that will be launched automatically when a specific action is done on your list of contacts or on your site, you need to specify what is this triggering action.

Once you have selected the scenario by trigger, you will be presented with a list of actions that can be set to trigger the launch of an automated scenario.

  1. Depending on the enabled modules in your account, two types of actions can trigger a scenario:
    • actions that affect your list of contacts (creation, update, opt-in or opt-out)
    • actions registered on the journey of your contacts (visited page, event, viewed product, abandoned cart)
  2. You must select one of the two options.

  3. Each type of actions lists different actions. You must select the one you want and also specifiy any additional information needed, if any.

List of actions on the contact list that can trigger a scenario
          
Action
Description
Contact creation
The scenario will be launched whenever a new contact is created in the application.
You also need to specify how the contact must be created for the scenario to be launched. You can select only one source or all. In addition, if you target contacts created following a request by form, you will have to indicate which ones. Know that if you select multiple options, any contact meeting any of the options will be added to the scenario.
Contact update
The scenario will be launched whenever a contact is updated.
You also need to specify how the contact must be updated for the scenario to be launched. You can select only one source or all. In addition, if you target contacts updated following a request by form, or those who were updated by clicking on an operational link in the message for this purpose, you will have to indicate which forms. Know that if you select multiple options, any contact meeting any of the options will be added to the scenario.
Contact opt-in
The scenario will be launched whenever a contact subscribes to a given communication type.You also need to specify which type of communication the contact must subscribe to for the scenario to be launched. You can choose only one communication type, or multiple ones. Also, you must select at least one opt-in source. If you target contacts who subscribes through a form or by clicking on an operational link in the message for this purpose, you will have to indicate which ones. Know that if you select multiple options, any contact meeting any of the options will be added to the scenario.
Contact opt-out
The scenario will be launched whenever a contact unsubscribes from a given communication type.You also need to specify which type of communication the contact must unsubscribe from for the scenario to be launched. You can choose only one communication type, or multiple ones. Also, you must select at least one opt-out source. If you target contacts who unsubscribes through a form or by clicking on an operational link in the message for this purpose, you will have to indicate which ones. Know that if you select multiple options, any contact meeting any of the options will be added to the scenario.
Manual launch
This option lets you launch manually a scenario set by trigger, for one contact at a time, from the contact's profile, or to launch it on demand through Web services or using a workflow.
Include contacts only once per X
To be certain that a contact is not included in the same scenario more than once in a given period, check this option and indicate the period.
Note that if an action occurs more than once, a contact already part of a scenario not completed will be ignored as long as the previous scenario is not completed.
List of behavioral actions that can trigger a scenario
          
Action
Description
Sites
Choose the site or sites for which you want to create automated scenarios amongst those configured to be tracked or registered by the Journey module.
Available actions depends on the actions configured for the site.
Visited page
This option is offered for all sites, so it is always possible to launch a scenario on site page visits.
Specify here all the visited page on which you want to trigger the scenario. If you want to include all the pages or sections of a site, use *.
In addition to trigger a scenario when a page is visited, you can add other conditions to be met to trigger the scenario.
If you select more than one condition, the contact will have to meet them ALL for the scenario to be applied.

Event
This option is only offered if you have configured special events to track.If this is the case, you will need to select one amongst the available events. Only one event can be selected to trigger a scenario.
Viewed products
This option is only offered if you have enabled the E-Commerce module and have configured it to track viewed products.
You must specify also the number of inactive minutes (between 10 and 720 minutes) must occur before the scenario is triggered.
Abandoned carts
This option is only offered if you have enabled the E-Commerce module and have configured it to track abandoned carts.
You must specify also the number of inactive minutes (between 10 and 720 minutes) must occur before the scenario is triggered.
Include contacts only once per X
To be certain that a contact is not included in the same scenario more than once in a given period, check this option and indicate the period.
Note that if an action occurs more than once, a contact already part of a scenario not completed will be ignored as long as the previous scenario is not completed.
Define the scenario's properties

The scenario configuration page opens.

  1. The first thing to do is to name your scenario, as by default it is called New scenario. To do so, open the Identification section, under the Properties tab, and click on the Edit link. You can then edit the name and enter a description, which is optional.
  2. Scroll to the various sections to set the other properties, such as the targeted contacts, the display options, and to view scenario validation messages.
    1. If needed and if categories exist in your project, assign a category to your scenario, especially if you have a lot of scenarios and want to group them, or if you want to use categories to set access rights. Categories must however be created before, via > Configuration > Categories > Campaigns
    2. You then need to specify the scenario type, that is selecting when and how the scenario will be executed, by clicking Configure.
    3. In the Scenario configuration window, select the launch type amongst the available types as well as the related options (date, time, etc).
    4. Following comes the selection of contacts to be targeted by the scenario, either all the contacts in the project, or contacts belonging to specific groups or matching specific criteria.
    5. Once the scenario type and contacts are both selected, click Save.
      The defined launch and contact selection options are shown in the left panel, in the Scenario type section. To change either option, click Modify and make the necessary changes.
  3. Description of properties fields
                     
    Section
    Field or Description
    Option or Description
    Identification
    Name
    Name given to the scenario when created. You can change the name anytime, as long as the scenario has not been launched.
    Category
    Campaign category associated to the scenario. This field only displays if campaign categories exist in the project. If no category was assigned to a scenario, the Non categorized value is used. If needed, you can select a new category here, from the drop-down list of categories.
    Description
    Description of the scenario.
    Schedule or
    Launch options
    You must select when and how the scenario will be executed. There options. As part of the scenario configuration, you must also select the targeted contacts.
    To define the scenario type, click Configure. If it has already been configured, because it is a template, then the button will be named Modify.


             


      
    Recurring
    Scenario that is executed repetitively, either every day, every week or every month, depending on the selected frequency.
    • If the frequency is Daily, you must specify one or more times, up to a maximum of 5 different times, in a 24 hour format, and also select the applicable timezone.
    • If the frequency is Weekly, you must specify one or more execution days, as well as the time (using the selector) and timezone, and make sure to save by clicking Apply.

    • If the frequency is Monthly, you must specify the day or days of the month on which the scenario should be executed, separated by a comma. Is you enter 29, 30 or 31, know that these will be ignored is the selected month does not have such days. The The last day of the month option makes sure the scenario is always executed on the last day of the month, regardless of the month.
    Fixed dates
    Scenario that is executed on the specified dates and times. You can set up to 10 different dates, within the same time zone.

    Manual
    Scenario that is not executed automatically, but by a user via the scenario launch page, or via Web services. No configuration other that selecting this type of scenario is required. Once the scenario is active, a launch page will be available to select the target contacts and to launch the scenario.
    For more information, see Launching a Scenario Manually .

    Post import
    Scenario that is executed when contacts are imported into the project, either automatically or on demand.
    You have the option to target all contacts in the project, only those that were added through import or only those contacts that were modified after import. You can choose to further limit the number of contacts by defining additional selection criteria.

    By trigger
    Scenario that is triggered by an action performed on your contact list or a given action performed by your contacts on your site.
     
    Targeted contactsAll launch types require the selection of contacts targeted by the scenario, except for Manual where contacts are selected at the time the scenario is manually launched.

    Note that marketing automation messages are sent based on the permissions that are granted to the user who created the campaign. So if a user is subject to message mailing restrictions, the message will only be sent to those contacts to whom he/she is entitled to send messages. It is therefore possible that the message is not sent to some contacts, even if they were selected.

             


      
    All contacts
    The scenario will apply to all the contacts in the project.
    Contacts targeted by the following groups
    The scenario will apply to all the contacts that belong to the selected groups.
    Contacts that match the following criteria
    The scenario will apply to all the contacts that meet the specified criteria.
    All imported contacts
    The scenario will be executed each time contacts are imported into the project and will apply to all imported contacts, whether new or edited.
    Added contacts only
    The scenario will be executed each time contacts are imported into the project and will apply only to contacts that were added through the import.
    Modified contacts only
    The scenario will be executed each time contacts are imported into the project and will apply only to contacts that were edited through import.


  4. Continue the scenario creation by defining its content, on the next step.
Define the scenario's steps

After having defined the scenario's properties, you need to create the actual scenario, that is to add the actions triggered by the scenario, to define the conditions in which an action will be executed as well as the end of each branch of the scenario, all under the Content tab.

**If you have decided to create your scenario from a template, the scenario will already have steps. You only need to select to message to send, and/or to add extra steps if needed.

By default, custom scenarios (not using a template) have two columns, Start and New step. The first column is used to add the launching action or condition, as the New step column is used to add all other steps of the scenario and is always as the last column, empty. Each column corresponds to a specific date and time in the scenario. Columns can be edited, by clicking , or even deleted, with ; the deletion of a column however is only possible if the column is empty.

It is possible to start the scenario with either an action or a condition.

Examples  You might want to send a message to all your contacts to invite them to a special event. Then you add a condition. Or you could want to start by searching for contacts that are members and then send the message only to those contacts.

  • To start your scenario with an action, choose one amongst those listed and drag it to the Start column. When you drag an action, small dotted-line squares appear to show you valid locations in the scenario for your action. It is recommended to always put the first action/condition in the first column, even if the system lets you drop it in other columns.
Description of possible actions
          
Action
Description
Message sending
Action that sends an email message. An editor opens to let you choose the SMS to send, either an existing one in the project, or an SMS specially designed for the current scenario.

How To

Depending on the type of SMS to send, the procedure will be slightly different.
  • If you want to send an SMS that already exists in the project and that is not to be only used in the current scenario, choose Use a generic message created beforehand.
    1. Click Continue.
    2. In the message sending window, change the default name of the action in the Label field.
    3. Click  to open the message selection window.
    4. Select a message amongst the existing messages in the project. If needed, filter the messages by name or communication type.
    5. Click Select.
    6. Back to the message sending window, add additional clauses to further limit the number of contacts based on these criteria.
    7. Once the message named and selected and clauses added if so required, click Save.
      If you want to view this message, or edit it, you need to access it via the message editor - > Messages > EMail.
  • If you want to send a message that will only be used for this scenario, select Use a message dedicated to this scenario.
    Messages reserved for this scenario do not show anywhere else than in the related scenario; they are not listed with the messages of the project.
    1. Click Continue.
    2. Click  to open the message selection window.
    3. Select a message amongst the messages already connected to this scenario or create a new one by clicking Create a message. If needed, filter the existing messages by name or communication type. If creating a new message:
      1. Change the default name of the message.
      2. Select the communication type to associate to the message.
      3. Click Create.
        The new message will show in the list of available messages. All is left to do is to create the message itself.
      4. To write the message, you must select this new message in the list and click Select.
        The message sending window opens, with the selected message as the message to send.
      5. Click the edit icon. This will open the message editor, where you can create the content of the new message according to the normal procedure (see Creating an HTML Message).
      6. One the message is created, go back to the Scenario page to continue with the creation of the scenario.
SMS sending
Action that sends an SMS message. An editor opens to let you choose the message to send, either an existing one in the project, or a message specially designed for the current scenario.

How To

Depending on the type of message to send, the procedure will be slightly different.
  • If you want to send a message that already exists in the project and that is not to be only used in the current scenario, choose Use a generic SMS created beforehand.
    1. Click Continue.
    2. In the sending window, change the default name of the action in the Label field.
    3. Select the SMS to sent by clicking on the icon . If needed, filter the messages by name or communication type.
    4. Click Select.
      If you want to view this message, or edit it, you need to access it via the message editor - > Messages > SMS
  • If you want to send an SMS that will only be used for this scenario, select Use an SMS dedicated to this scenario.
    SMS messages reserved for this scenario do not show anywhere else than in the related scenario; they are not listed in the SMS lists of the project.
    1. Click Continue.
    2. In the sending window, change the default name of the action in the Label field.
    3. Select the SMS to sent by clicking on the icon . You will see a list of all SMS messages created just for this scenario.
    4. In the selection window, select an SMS amongst those already connected to this scenario or create a new one by clicking on the new SMS link. If creating a new SMS:
      1. Change the default name of the message.
      2. Select the communication type to associate to the message.
      3. Click Create.
        The new SMS will show in the list of available SMS messages. All is left to do is to create the message itself.
      4. To write the SMS, you must select it in the list and click Select.
        The sending window opens, with the selected SMS as the message to send.
      5. Click the edit icon. This will open the message editor, where you can create the content of the new SMS according to the normal procedure (see Creating an SMS Message).
      6. One the message is created, go back to the Scenario page to continue with the creation of the scenario.
Send a web push notification
Action that sends a web push notification in the subscriber's browser.
When adding this action to a scenario, an edit window appears to let you select the notification to send, either one that already exists in the project, or one to be used exclusively for this scenario.

How To

Based on the type of notification to be sent, the procedure is slightly different.
  • Choose the option Use a generic notification created beforehand to select a notification that already exists in the current project, and that is not exclusive to this scenario:
    1. Click Continue.
    2. In the send window, change the default notification name in the Label field.
    3. Click the  icon to make your selection amongst the project's existing notifications. 
    4. To get a more selective list, add criterion as needed.
    5. Click Save.
      To view or edit the notification, open if from Messages > Web push.
  • Choose the Use a notification dedicated to this scenario to send a notification that will only be used with this scenario. These dedicated notifications only show within the scenario; you won't see them in the project's list of web push notifications.
    1. Click Continue.
    2. In the send window, change the default notification name in the Label field.
    3. In the selection area :
      • To use a notification already created, click , then select the desired notification.
      • To use a new notification, click  and the link Create a new notification, or theicon if there are no notifications already related to this scenario:
        1. Provide a new name for this new notification.
        2. Select the related Website.
        3. Select the communication type to related it to.
        4. Click Create.
          The new notification will display in the list of available notifications for this scenario. 
        5. Click Select fo add it to the scenario.
        6. Back on the Send window, and the selected notification shown in the Notification field, click the edit icon to open it in the message editor in order to edit its content and parameters.
          For detailed instructions, refer to the article Creating, testing and sending a web push notification.
        7. Once the notification is created and edited, go back to the Scenario page to continue the definition of the scenario.
Send a mobile notification
Action that sends a push notification related to a mobile application.
When adding this action to a scenario, an edit window appears to let you select the notification to send, either one that already exists in the project, or one to be used exclusively for this scenario.

How To

Based on the type of notification to be sent, the procedure is slightly different.
  • Choose the option Use a generic notification created beforehand to select a notification that already exists in the current project, and that is not exclusive to this scenario:
    1. Click Continue.
    2. In the send window, change the default notification name in the Label field.
    3. Click the  icon to make your selection amongst the project's existing notifications. 
    4. Select the recipients, either subscribers on Android or Apple.
    5. To get a more selective list, add criterion as needed.
    6. Click Save.
      To view or edit the notification, open if from Messages > Notifications.
  • Choose the Use a notification dedicated to this scenario to send a notification that will only be used with this scenario. These dedicated notifications only show within the scenario; you won't see them in the project's list of mobile notifications.
    1. Click Continue.
    2. In the send window, change the default notification name in the Label field.
    3. In the selection area :
      • To use a notification already created, click , then select the desired notification.
      • To use a new notification, click  and the link Create a new notification, or theicon if there are no notifications already related to this scenario:
        1. Provide a new name for this new notification.
        2. Select the related application.
        3. Select the communication type to related it to.
        4. Click Create.
          The new notification will display in the list of available notifications for this scenario. 
        5. Click Select fo add it to the scenario.
        6. Back on the Send window, with the selected notification shown in the Notification field, click the edit icon to open it in the message editor in order to edit its content and parameters.
          For detailed instructions, refer to the article Creating, testing and sending a mobile push notification.
        7. Once the notification is created and edited, go back to the Scenario page to continue the definition of the scenario.
Contacts export
Action that exports contacts that meet the related condition. An extraction file is created and saved on the file server, which you can access to download the file. To be able to perform this action, a file server must have been configured for your company. If this is not the case, contact us for such server to be assigned to you.

How To

  1. If needed, change the default name of the action in the Label field.
  2. Under the Source tab, select the contacts to export. By default, all contacts are exported. However, it is possible to limit the number of exported contacts by selecting one of the two possible options, either to export contacts that belong to specific groups, or to export contacts that meet specific criteria.
  3. Under the Destination tab, select the file server on which you want the file to be exported. If no server has been configured for your company, none will be available for selection and this action will not be possible. Then, specify the full path of the file, from the root of the file server. If you want the path to include a personalized name that includes the date of the planned export, select the related Dynamic option.
  4. Go to the Options tab to select the actual contact data that you want to export. You have the choice of exporting all the fields in the project or to select the specific data to export. You can also export data recorded in a relational table by selecting this option and the desired table; you will then have to choose the specific fields in this table that you want to extract. It is also possible to choose an hashing algorithm for obfuscated fields. The extracted file can be compressed if needed, in a .ZIP or .RAR format, by checking the related option.
  5. Click Save.
Profile update
Action that edits the value of a field in contact profiles. Only general fields are available for this action; administrative and opt-in fields cannot be edited with this action, nor fields composing the primary key.

How To

  1. If needed, change the default name of the action in the Label field.
  2. Choose the field to update from the list of available fields.
  3. Enter the new value to assign to the selected field. If you prefer assigning a string, instead of a value, select the related option.
  4. If you wan to apply the new value to a limited number of contacts, you can do so by specifying criteria to meet for the update to take effect.
  5. Click Save.
Unsubscribe
Action used mostly for re-engagement campaigns designed to win back inactive contacts, that will unsubscribe contacts who still do not open or click your message.
The opt-out process differs depending on whether the consent center is enabled or not.
  • With the consent center enabled, contacts who still do not reply to the message will be unsubscribed from one or more communications, based on the choice made when selecting the communication types from which to unsubscribe contacts.
  • With the consent center disabled, contacts are simply deactivated.
It is also possible to limit the number of contacts to unsubscribe by specifying other criteria to meet for the opt-out to occur.

How To

  1. If needed, change the default name of the action in the Label field.
  2. If the consent center is enabled in the project, you will have to specify which communications you wish to unsubscribe contacts from. Otherwise, when there is no consent center, contacts are just deactivated and no longer eligible to receive messages.
  3. In both situations, you can choose to limit the number of contacts to unsubscribe by specifying additional criteria. If this is what you want, check this option and define the criteria to be met using the project fields; for instance, you could choose to only unsubscribe contacts who live in Montreal (City = Montreal).
    You can add as many criteria as you need.
  4. Click Save.
  • To start the scenario with a condition, choose one amongst the general conditions provided (not the conditions following a sending) and drag it to the Start column. When you drag a condition, small dotted-line squares appear to show you valid locations in the scenario for your condition. It is recommended to always put the first action/condition in the first column, even if the system lets you drop it in other columns.

    Adding a condition is essential as it determines which contacts are to affected by the related action. In general, conditions offer two responses, one for contacts who meet the condition, and one for those who don't. However, it is possible to have more that two responses by using the Multiple branches option.
Description of conditions
          
Conditions
Profile condition
Condition that validates whether a contact has or not the provided value in a table or project field. This condition involves two possibilities, either the value is true or false. And an different action is usually associated to each response.
Example You want to start your scenario by finding out, in your contact profiles, who has accepted to receive promotional messages. The promotion you are planning to send will only be sent to those contacts for whom the value is true. You could then send an invitation to those contacts who have not subscribed to receive promotions. Following this new invitation, you could add another condition, and so on.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true andLabel when false fields. Example Using the previous example, we could have the condition named Subscribed to promotions? and use Subscribers for those contacts that meet the condition and Non subscribers for contacts who do not meet the condition.
  3. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
  4. Once the condition is defined, click Save.
  5. Afterwards, when adding a new action, the condition will show two possible branches to place the action - those who meet the condition and those who don't.
Group condition
Condition that targets contacts by searching those belonging to one or more specified groups. An action is associated to the contacts that are in the selected groups and another action is performed on those that are not in those groups.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
    Example Let's take a group of contacts who speak French, and another group who speaks English. We could have a condition labeled French? and have French contacts as the label when the condition is True and Other contacts as the label for when the condition is False.
  3. Amongst the available groups, select those groups in which you want targeted contacts that respond positively to the condition.
  4. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
  5. Once the condition is defined, click Save.
  6. After wards, when adding a new action, the condition will show two possible branches to place the action - those who meet the condition and those who don't.
Multiple branches
Condition that lets you have more than two branches for a condition and validates whether a contact has or not the provided value in a table or project field.
Contacts first pass through the first branch, where the condition is True. The second branch is added automatically to hold all the contacts that do not meet the condition (not True).

How To

  1. If needed, change the default name of the condition in the Label field.
  2. On the line of the first condition, click to define this condition.
  3. In the condition definition window, enter a name for the condition in the Label field.
  4. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
  5. Once all conditions are defined, click Save.
  6. When using multiple branches, the last one will always include all the contacts that do not meet the previous and various conditions.
Persona condition
Condition that lets you target contacts who correspond a one or multiple personas. An action will be associated to contacts who met the criteria of the persona(s) or another action will be associated to the contacts who don't. Note that if you have not defined personas, this condition will be of no use.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
    Example You could set the True condition to the name of the persona, and to "Others' for the False condition.
  3. Select the persona(s) you want to apply the scenario to.
  4. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
  5. Once all conditions are defined, click Save.
  6. Then, when adding an action, the condition will show two possibles branches for the action - contacts who meet the condition, and contacts who don't.
Conditions following a sending
Delivered messages
Condition that must follow a message sending action and be placed in a step following the message.
This condition selects the contacts to whom the message was sent with success.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
  3. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
Opened messages
Condition that must follow a message sending action and be placed in a step following the message.
This condition selects the contacts who have opened the message.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
  3. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
Clicked links
Condition that must follow a message sending action and be placed in a step following the message.
This condition selects the contacts who have clicked on at least one link in the message.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
  3. It is also possible to target your contacts even more precisely:
    1. by searching for those who clicked on a specific link, via the Specific links tab. For this option, you must select the desired link amongst the list of links included in the message. If needed, a search tool is available to filter the existing links and to locate the desired one quicker. Furthermore, you can select an option that ignores parameters when searching (in an URL address, parameters are all those characters after the ? separator).
    2. by searching for those contacts who have clicked on a link associated to a specific attribute, via the Attributes tab. You must then enter the searched attributes.
    3. by searching for contacts who meet other criteria, via the Additonal criteria tab and by defining those criteria using the necessary+ clause and + (clause).
Opt-outs
Condition that must follow a message sending action and be placed in a step following the message.
This condition selects the contacts who have unsubscribed from the message.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
  3. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
Spam complaints
Condition that must follow a message sending action and be placed in a step following the message.
This condition selects the contacts who have reported the message as spam.

How To

  1. If needed, change the default name of the condition in the Label field.
  2. If needed, provide a more suitable name for the True and False conditions in the Label when true and Label when false fields.
  3. To further limit the number of targeted contacts, you can specify other criteria by checking the Restrict to contacts that also match the following criteria option and define the conditions to be met by clicking + Add. You can add as many conditions as needed.
Define when each step is to be performed

Each step can contain multiple actions to execute, and this execution must me defined for each step, except for the launch that is defined as part of the scenario's properties.

  1. Click on the column header of the step to see the edit icon  display and then click on it.
  2. In the Step window, select the number of days to elapse between the preceding step and the current one. If you choose a delay in days, you will also need to specify a specific time.
Define the end of the scenario

You must define a scenario end for each branch in the scenario. Scenario ends correspond to results and also provide a way to group results in the execution log. There are 4 default ends, which have default meanings, that can be changes if so needed. It is also possible to add custom scenario ends to meet other marketing goals. The result associated to a branch that ends with a failure or a success is quite clear, but you still can decide to give it another meaning. As for the other branch ends, it is completely up to you to decide what is an abandon or a neutral end.

Scenario results are visible under the History tab, where you can see a column for each scenario end, as well as the number of corresponding contacts.

Example

If the scenario is designed to encourage contacts to subscribe to your monthly newsletter:

End (success) - The contact has subscribed.

End (failure) - The contact has declined your subscription offer.

End (abandon) - Thee contact has reported your message as spam.

End (neutral) - The contact has not done anything in the prescribed period - so this neither a failure or a success.

  1. In the Scenario end section, select the end you wish to associate to a branch and drag it to a valid location, indicated by a dotted-line square .
  2. If so desired, you can add another end by clicking on Configurable goals and then :
    1. In the pop-up window that display, click on Add a goal.
    2. Enter a name for the goal and select a type among those by default. You can create up to 100 custom ends. Therefore, if you have many customized ends, you can sort them in the order of your choice by clicking on the reordering arrow .
      Also, if needed, you can edit, archive and delete any custom goal by clicking on the corresponding icon.
Move scenario elements around

Moving elements within the scenario is simple - you just need to click on the element you want to move and drag it to a new location, which will be indicated by coloured dotted lines.

You can also move scenario elements to the right panel, under Saved elements in order to put them somewhere else in the scenario later on.

In addition, the last 10 deleted elements are placed in that same right panel, under Deleted elements for future use.

You might want to move, for example, elements because you have forgotten a step and you want to insert one before. To do so, you would need to move the step(s) following the one you forgot, add the new step and replace the saved elements after.

  1. To save an element in order to use it later, just click on this element and drag it to the Saved elements section.
    This element and all those that follow it will be moved to the saved element section.
  2. To delete an element, you can either drag it to the right panel, under the Deleted elements section or click , except if the element is a scenario end. Scenario ends can only be deleted with the icon, available when clicking on the element.

    The deleted element and those that follow it will be moved to the deleted element section.
Edit, cut, group or delete scenario elements

You can edit, cut, group or delete any scenario element, as long as the scenario is not completely executed. Possible options for an element display when clicking on the element.


  1. To edit an element click on the element and then on .
  2. To cut an element, click on the element and then on .
    The element and all those that follow it will be moved to the Saved elements section.
  3. To delete an element, click on the element and then on . You can also drag the element to the Deleted elements section if it is not a scenario end.
    The element and all those that follow it will be moved to the Deleted elements section.
  4. To group an element and all the other that follow it, click on the element and then on . You can give the grouped region a name, as well as select a frame color. You can close regions to better display complex scenarios, and open them to see the elements it contains. To do so, simply click on the + or - sign next to the name of the region. You can remove grouping by clicking on the region name and then on Remove region.
Validate the scenario

Before proceeding to the scenario launch, it is important to review the various steps to make sure your scenario is complete and ready. Validation messages are shown under the Properties tab, in the Validation section. A scenario can only be activated once the validation message indicates No problem detected.

  1. Go to the Properties tab, in the Validation section, to see if there are error messages or warnings.
  2. Correct errors if there are any. An indicates an error, as a  indicates that the element or branch is incomplete. You can view where are located incomplete elements by checking the Display or Display incomplete elements option.
  3. For a scenario to be considered valid, and to be able to go to the next step, the validation message must show No problem detected.
    When such is the case, the Properties section will also display that the message is in preparation and ready to be activated.
Activate the scenario

Once the scenario is valid and complete, you need to activate it. This is done via the Properties tab, in the Properties section. The link to activate is only displayed if the scenario is complete.

  1. Under the Properties tab, in the Properties section, click on the Activate link show next to the scenario status.
    The scenario is now active and will be launched and executed as per the defined launch date and time, except for scenarios set to be launched manually.