Manual, automatic and trigger campaigns

If you are already using Campaigns (the newest version of Scenario), for your trigger/event-based campaigns as well as for your manual campaigns, please check our articles on Campaigns > Automations > Triggered Campaigns (for event-based campaigns) and How to use one-shot campaigns (manual campaigns).

	Manual Campaigns	Automatic Campaigns	Trigger Campaigns	Real-time Trigger Campaigns
Seed lists
Temporary files as populations
Control group (ROI)
AB Tests
Split targeting
Measure submission speed
Use filters in follow-up sequences
Channel X
Manage access to statistics
SMS campaigns
Follow-ups in the same scenario (email, SMS, attribute points or rewards)		(SMS follow-ups are not possible)
Use sales filters as populations (orders and abandoned carts)
Use interactions in filters
Data export as an action

Creating your new campaign

1. Begin by clicking “New campaign” from the shortcuts as shown below.
2. Name your campaign and enter the “ROI settings” values if you wish to activate the calculation of your campaign ROI. If you leave the fields empty, the system will automatically count:
   • 14 days from the moment of launch for email
   • 3 days from the moment of the launch for SMS
3. Then go to “Campaign scenario” and click “Select starting channel and population”.
4. You will be presented with the option to select an automatic or a manual campaign

Selecting your population

Once you have selected the type of campaign you wish to use (we will detail their specificities further in this article), you will be asked to select the population (lists, filters, groups) that your campaign will then target.

Openings: In this article, when we are mentioning email openings, note that this metric will be impacted by the Apple Mail Privacy protection.

Manual campaigns are used for...

• Complex scenario trees, with different branches and reactions at each step.
• Pre-programmed, one-shot scenarios (mother's day, valentine's day, newsletters).

After they are launched, Splio will process the scenario tree for each targeted contact exactly once. This is an additional safety measure to ensure that all manual campaigns are always deduplicated. When the campaign is finished, you can view its statistics or add a follow-up to it.

Two special features are available for manual campaigns (for which we have separate tutorials, see links below):

1. Split targeting
2. A/B testing

It is not possible to perform a loyalty action in an A/B test campaign or Split targeting.

Example of a manual campaign tree structure explained

In manual campaigns, the first action (which sends an email or SMS message) can be followed by one or more sequences:

1. Contacts who were sent the initial message but did not open it received a new version a week later.
2. Those who opened the message (either the original one or the relaunch) but did not click any links were sent an additional incentive, e.g., a message with more details of the offer.
3. It was programmed using the “Email opened” reaction together with a filter which only matched the contacts who did not click any links.
4. Finally, all contacts who made a purchase of the promoted product received another message with a participation reward (a discount voucher).
5. To qualify for it, they had to click a link in the email and get matched by a filter which looked for purchasers of the promoted product.

Automatic campaigns are used for...

• Recurrent campaigns such as birthday or anniversary offers.
• Minimum frequency of once a month, maximum once a day.
• Make sure to include only the relevant contacts in the target filter, as Splio will send messages to all members, even those targeted during earlier iterations.
• You can create one follow-up action sequence (see below).

How to set up an Automatic campaign

Automatic campaigns are created by selecting the “Periodic date” option and selecting a frequency:

You will be able to insert a follow-up with one more action (without branches) for instance, to send a reminder after a day or two, or to credit the recipient with loyalty points.

If you are using Campaigns for your trigger campaigns, please refer to this article.

Trigger campaigns are used for...

A sending once per object (contact, order, or abandoned cart) in the filter or list used as population. Two sub-types :

Real-time trigger: launched immediately after the object enters the filter (contact, order, or abandoned cart) and is updated via the API (welcome campaign, post-purchase, abandoned cart).
In this case, the time schedule set in the campaign is ignored and it can be launched at any moment, and as many times as needed per day.

In the population of your real-time trigger campaign, you CAN use:

• a list
• any contact filter related to the update of a system or a custom field of your Contacts
• any Order or Abandoned cart filters. Using this type of filter will allow the campaign to target contacts who are not subscribed to a list, and the ones that are in the soft bounce and unsubscribed blacklist.
• a Contact filter including a loyalty filter for the welcome of your Loyalty members (using the Loyalty subscription date, only available in Loyalty filters)

You CANNOT use:

• a contact filter using the condition "date of creation in DB" with the operator "more than some time ago". Please use "less than some time ago" instead.
• a filter including Interactions
• any other Loyalty condition other than the program subscription date (for welcome campaigns)

Standard trigger campaigns: also launched once per object. However, in other aspects, they are processed like automatic campaigns. When an object lands in the target filter, it gets queued and the message will be sent the next time the campaign is processed. The timing and frequency of the campaign are defined in the scenario. This type of campaign can be sent from a minimum of once per month to a maximum of once per day.

• /!\ A common misunderstanding takes place when clients update their data via batch (e.g., DataHub). Contrary to some expectations, such campaigns are sent on schedule, once per day maximum. Datahub/Batch uploads work with plain triggers, the real-time sending is reserved to API connections.
• Please note that for trigger campaigns, if you decide to update the design, this change will only be taken into account once per day regardless of the send out of the campaign (event triggering).
• Warning: Never modify the filter for trigger campaigns! You should never, ever modify a trigger campaign filter once the campaign is running. This is because trigger campaigns are sent to all contacts (or, e.g., owners of orders) entering the filter.
• The filter used as a population in your trigger campaign is emptied before sendout. In other words, trigger campaigns are not retroactive.

All contacts added to the filter due to your modification will be targeted immediately!

Using the campaign category for trigger campaigns

Each trigger campaign is a separate scenario, set off when a contact is matched by a filter for the first time. To be able to create follow up campaigns from a trigger campaign, you must use the campaign category during setup.
Once created, a campaign category can't be deleted.

Then, you need to create a contacts filter that matches contacts who opened the email confirmation message earlier in the chain and include your campaign category:

The filter can then be used to create a follow-up campaign.
Notice the time constraint, which means that only the contacts who opened the email within the last 24 hours will be targeted (which is perfect if the follow-up message is set up to go once per day).