Building a great campaign is only half of the equation — making sure your users actually receive it and engage with it is just as important! With alerts, you can set up performance thresholds that notify you when a campaign isn't performing as expected. If a campaign exceeds one of your alert thresholds, you'll receive a notification outside of Iterable prompting you to log in and troubleshoot the issue.
As of October 2023, the alerts feature is in beta for select Iterable customers. Don't see it yet? Check back in a few weeks!
In this article
- Required permissions
- Setting up alerts for your project
- Enabling and disabling alerts for a campaign
- Editing your project's alerts
- Current feature limitations
- Frequently asked questions
To create and manage alerts for your project, you'll need the Manage Project Settings permission.
To turn alerts on/off for a campaign, you'll need the Draft Campaigns permission.
Setting up alerts for your project
To set up your project's alerts, click the gear icon and select Alerts in the Settings menu.
This opens the Alerts page, where you can create and edit your project's alerts.
You can create alerts for all messaging channels (Email, Push, SMS, In-App, and Web Push) for both blast and triggered campaigns. Alerts can notify you when a campaign has a high bounce rate or unsubscribe rate, a low click rate or clicks, a low open rate or opens, or low sends. (To learn more about how these metrics are calculated, see Metric Definitions.)
Create an alert
To create an alert, check the box next to the performance metric you want to monitor. Then, enter a percentage and time frame.
Choose a destination
Next, set up a webhook to connect Iterable to your alert destination. On the Alerts page, scroll down to the Alert Destination section and click Add Webhook.
Right now, we support Slack as an alert destination, and we'll be adding support for additional destinations in the future.
Give your webhook a name (for example, "Slack Webhook") and optionally, choose an authentication option. Leave the Endpoint URL blank for now (you'll fill this in later after you generate a web request URL in Slack).
Create a Slack workflow
You can set up a Slack workflow to receive performance alert notifications about your campaigns without having to log in to Iterable. Here's how:
Open Slack and click More > Automations.
Click Create a Workflow.
Select Start from Scratch > From a Webhook.
Click Set Up Variables, and add variables for all the information you want to see in the notifications you receive about underperforming campaigns. For example, you might want to know the campaign name, ID, medium, type, and state; the template ID; the metric that triggered the alert; and the link to the campaign's analytics page.
For each variable you set up, add a key and a data type. The key is the name of your variable, and the data type is the kind of data that Slack will populate for the variable in each notification you receive. You can choose from the following variables:
campaignName, Data Type:
campaignId, Data Type:
campaignMedium, Data Type:
campaignType, Data Type:
campaignState, Data Type:
templateId, Data Type:
metricAlertName, Data Type:
campaignAnalyticsLink, Data Type:
metricAlertText, Data Type:
When you're finished setting up your desired variables, click Continue.
Under Steps, click Messages > Send a Message to a Channel.
Select the Slack channel where you want to receive messages about campaign alerts.
Add the text of the message you want to receive in Slack when a campaign alert is triggered in Iterable. You can type text and emojis and insert the variables you set up earlier — at send time, Slack will replace each variable with the relevant information for the affected campaign. Your alert message might look something like this:
Scroll down to the Preview section to see what your alert message will look like in Slack. When you're happy with your message, click Save.
When you're finished setting up the workflow, click Publish.
Open your published workflow, and click the pencil icon next to Starts with a Webhook. Scroll down to the Web Request URL section and click Copy Link.
In Iterable, go to Settings > Alerts, and scroll down to the Alert Destination section.
Click the three dots next to your Slack webhook, and click Edit.
Under Endpoint URL, paste the web request URL you copied in Slack, and click Save Changes.
The next time one of your campaigns triggers an alert, you should receive a message in your selected Slack channel.
To learn more about setting up workflows in Slack, see Slack's support article Create More Advanced Workflows Using Webhooks.
Enabling and disabling alerts for a campaign
When you create and turn on alerts for your project, they automatically apply to all campaigns of that message type and channel for which alerts are enabled.
Any new campaigns created after the alerts feature was released in October 2023 automatically have alerts enabled, but you can turn alerts on or off for individual campaigns in the Delivery section of the campaign details page.
You can check which campaigns have alerts enabled at a glance on the Campaigns page. Campaigns that have alerts enabled are indicated with a bell icon.
Editing your project's alerts
You can make changes to your project's alerts settings at any time. Turn an alert on or off, or adjust the percentage or time frame, then click Save.
When you edit an alert for triggered campaigns, Iterable uses the new alert settings for all campaigns that haven't been sent yet. For example, if you create an alert that notifies you of a <10% click rate after 24 hours and then change the click rate percentage to <5% before Campaign 1 has been sent, you'll only be notified if Campaign 1's click rate is less than 5% 24 hours after it was sent. If you edit the alert after Campaign 1 has started sending, you'll be notified if its click rate is less than 10% after 24 hours.
Current feature limitations
As of October 2023, the beta version of this feature has a few limitations:
- You can only turn alerts on for a campaign if project alerts are set up for that message type/channel.
- Project alerts apply to all campaigns for which alerts are enabled — you can't apply specific alerts to a specific campaign.
- Alerts are not available for journey-triggered campaigns at this time (only stand-alone blast campaigns and API-triggered campaigns).
- You can only receive alert notifications via webhooks (not via email or Iterable's notification center).
- You can't compare recent alert values to a previous set of values.
Frequently asked questions
Do I need to configure a project-level alert before I can enable it for my campaign?
Yes. Right now, any alerts you wish to apply to a campaign must be set up on your project's Alerts page.
Are alerts automatically enabled for campaigns I've already created?
No, only newly created campaigns. However, you can open any campaigns you created prior to when this feature was released and manually turn on alerts in the Delivery section.
Will I be able to receive alert notifications by email in the future?
Yes, future versions of this feature will support email notifications.
Can I set up alerts for conversions or events?
Not at this time.