A triggered campaign is an email, SMS, push, or in-app campaign that is sent after a triggering event has occurred. An example would be an order confirmation email triggered by a purchase event.
Here's an example of a triggered email:
Creating a triggered campaign
Follow these steps to create a triggered campaign in Iterable:
Navigate to Messaging > Campaigns.
Click Create New Campaign.
Enter a Campaign Name, select Labels as necessary, specify Triggered for Campaign Type, choose a Message Medium, and select Send Lists.
Click Continue to Templates to select a template for the campaign.
Select a template and click Continue to Design, or click Create a New Template.
Make any necessary edits to the campaign's content.
Choose to either Create A/B Experiment or Save & Continue to Review.
On the Review & Launch page, you will see a Sample API Request for the campaign. In your app, after the campaign is active, trigger it by calling the
POST /email/targetAPI endpoint.
Triggered campaigns do not send messages until they are in the running state. For example, a triggered campaign in the ready state will not send messages. By contrast, a workflow campaign automatically transitions from ready to running when the first user arrives at its associated workflow node.
To view message sends scheduled by a triggered campaign, navigate to Insights > Logs > Scheduled Messages.
Here you'll find all triggered messages that have a future send date
sendAt in the API call is set to a future date).
You are also given the option to delete any or all of these messages in the event that you want to cancel the sends.
To see messages that have already been sent by triggered campaigns, navigate to Insights > Logs > Sent Messages.
From here, you can also view a preview of the sent message and/or resend the message if you'd like. The preview and resend will both be rendered in accordance to the current template version, which may be different from the version used for the original message.