To send a message after a user completes an event of some kind (like a purchase), use a triggered campaign. Triggered campaigns can be activated by an API call, or by a journey.
This article describes how to activate a triggered campaign. You'll do this from the campaign review page, after verifying that the campaign is set up correctly.
NOTE
To learn more about sending messages from journeys, read Sending Messages from a Journey.
In this article
Activating an API-triggered campaign
To activate a triggered campaign, go to the campaign review page and click the Activate button:
Activated triggered campaigns are in the Running state, and you can send them to users.
API calls for triggered campaigns
To send an API-triggered campaign, use these API endpoints:
POST /api/email/target
POST /api/push/target
POST /api/sms/target
POST /api/inApp/target
POST /api/webPush/target
TIP
To use these endpoints to schedule a triggered campaign for later, include a
sendAt
value in your request. However, this disables Send Time Optimization
for that send.
To send an API-triggered campaign to a list of users, use this endpoint:
Viewing scheduled sends of triggered campaigns
To view message sends scheduled by a triggered campaign, navigate to Insights > Logs > Scheduled Messages.
Use the delete buttons at the top of the page to delete scheduled sends.
Viewing past sends of triggered campaigns
To view past sends of triggered campaigns, navigate to Insights > Logs > Sent Messages.
From here, you can see a list of sent messages, preview them, and resend them. To preview and resend, hover over the message and click the View and Resend links that appear.
WARNING
When resending a message, Iterable uses the current version of the original message's template. Since that template may have been modified, the resend may look different than the original.
Next steps
Before sending a triggered campaign be sure it looks as it should. See Reviewing a Campaign Before Sending.
Comments
0 comments
Article is closed for comments.