In this article we will learn about the 3 sending methods available for automated messages:
The API sending method is for messages that will be triggered via the API using the "automationtemplates" method. It is important to enable the API sending method if messages will be triggered via the API.
The event triggered sending method is used when a message is to be sent as the result of a contact behavior or event.
Some examples of triggered events include:
- A change in a contact attribute value.
- When a contact is added to a list.
- A custom event (when a contact adds an item to a cart or when a contact browses an item on your website).
Some examples of the types of messages that take advantage of event triggers include:
- Welcome message - learn more about setting up a welcome message.
- Abandon cart message - learn more about setting up an abandon cart message.
How to enable an event triggered sending method
- Create a new automated message or edit an existing draft.
- Complete the message headers and message content and publish the draft.
- Choose the Event Triggered sending method from the left navigation bar.
- Select the desired trigger event and associated options.
- Add an optional audience filter (set to "all contacts" by default). Changing the filter determines which contacts are eligible to receive the message after they qualify for the trigger.
- Click the button labeled "Enable"
For detailed instructions and examples of event triggered messages read about automation use cases.
A recurring message sending method is used when a message is to be sent automatically based on a set schedule.
Audience rules are used in conjunction with a schedule to determine when a message is sent and to which contacts.
For example, a message could be set to send every day to contacts that haven't opened a message or clicked a link in the past 30 days.
An example of a recurring message includes:
- Welcome series - learn more about setting up a welcome series.
For detailed instructions and examples of recurring messages read about automation use cases.
In the next article we'll learn about automated message performance.