This article provides various tips to help troubleshoot campaigns.
# In this article
# Why didn't a user receive a message from this campaign?
When sending a campaign to a list of users, there are various reasons that individual users on the list may not receive the message.
# Suppression list in campaign
Was the user included on a suppression list used for your campaign? If a user is included on a send list and a suppression list, they won't receive any type of communication associated with that campaign.
# Unsubscribed
Is the user unsubscribed from the channel, unsubscribed from an opt-out message type, or not subscribed to an opt-in message type? In any case, they won't receive the campaign.
# Send skips
Iterable logs send skip
events on each user's profile page in the Event History
tab. When a campaign is skipped for a user, the send skip event includes a
field called reason that explains why the send was skipped. Possible reasons
for a send skip include an invalid reply-to email address, a mismatch between a
user's locale and the campaign's content, errors in Handlebars code, or your
project's Frequency Management settings.
For a list of potential send skip reasons, see Reasons for Send Skip Events.
# Email bounces
Two types of email bounces can occur during a campaign. A hard bounce generally means the email is invalid or has a typo. A soft bounce generally means that an email was rejected because a mailbox is full, a SPAM filter was encountered, etc. Bounce events are logged to users' event histories with data that highlights why the email was bounced. This data can also be exported via CSV in any Campaign Analytics page.
For more information, see Email Bounces.
# SMS bounces
SMS bounces occur when a phone number is invalid, unreachable, or has opted out of receiving SMS messages. Iterable does not automatically unsubscribe users who bounce from SMS messages. Instead, Iterable logs the bounce event to the user's profile and allows you to manage the user's subscription status as needed.
For more information, see SMS Bounces.
# ESP suppression
Email service providers (ESPs) often maintain their own suppression lists to help protect sender reputation. Each ESP has its own rules for managing suppression lists. Common reasons include multiple bounces, spam complaints, or unsubscribes.
In Iterable, these events are related to ESP suppression:
-
Unsubscribe with an
unsubSourceset toESP -
Bounce
with a status of
recipientStateset toSuppressed -
SendSkip with a
reasonofSuppressedByMessageService
To learn about suppression lists maintained by ESPs, see their documentation:
# Resubscribing users on an ESP suppression list
Sometimes a user on an ESP suppression list wants to receive your emails again.
Resubscribing a user in Iterable does not remove them from the ESP suppression
list. If you re-subscribe the user in Iterable but do not remove them from the
ESP suppression list, the ESP bounces the message and Iterable categorizes the
bounce with the recipientState of Suppressed.
For a user to receive your emails again, you need to first remove the user from the ESP suppression list, and then resubscribe them in Iterable as needed.
The process for removing a user from a suppression list varies:
-
ESP managed by Iterable
If you're using an ESP managed by Iterable (such as Amazon SES shared pool), you can't access or manage suppression lists directly. Instead, contact Iterable Support to request that a user be removed from the suppression list.
-
Your own ESP account
If you're using your own ESP account, you may be able to remove the user from the suppression list directly. Contact your ESP for more information.
-
SMS suppression lists
Generally, users can resubscribe to SMS by replying with an opt-in keyword. To learn more about how users can resubscribe to SMS, read SMS Unsubscribes and Resubscribes.
# Journey configuration
If you're using a journey to trigger an email send, make sure to check your journey's advanced options, as lifetime and simultaneous entrance limits may be in place that will prevent a user from entering into a journey. These two settings will check to see if a user has entered a journey anytime previously or if they are currently in a journey, which may prevent the user from processing as expected.
# Duplicate marketing send prevention (18-hour rule)
Iterable has a built-in sending limit for blast campaigns and journey sends that are sent from a marketing channel. A given marketing campaign ID can only be sent to the same user once in an 18-hour period. This limit helps prevent your team from accidentally sending the same campaign to the same user multiple times.
If you're seeing fewer recipients than expected for a campaign, some users may have already received the campaign within the past 18 hours, or may share a recipient ID (such as a phone number) with a user who did. Iterable doesn't log a send skip event for these skipped sends.
The 18-hour limit applies to:
- Blast campaigns from marketing channels, whether you send them from the
Iterable app or through
POST /api/campaigns/{campaignId}/sendorPOST /api/campaigns/{campaignId}/schedule. - Journey sends from marketing channels.
The 18-hour limit doesn't apply to:
- Transactional messages.
- Embedded messages. To learn more, see Embedded messages and the 18-hour rule.
- API sends through
POST /api/campaigns/triggeror the target endpoints (for example,POST /api/email/target), unless you setallowRepeatMarketingSendstofalse. - API target endpoint sends with a
sendAtvalue in the future. These sends bypass the limit even if you setallowRepeatMarketingSendstofalse. - Resends, proofs, test sends, and journey test sends.
To test repeatedly, use a test send or proof, or use test users with unique email addresses or phone numbers.
To change how the 18-hour rule works for your project, contact Iterable Support to request a review of your use case.
# How Iterable identifies duplicate sends
Iterable compares the campaign ID to a recipient ID that depends on the channel:
| Channel | Recipient ID |
|---|---|
email or userId, depending on your project type
|
|
| In-app |
email or userId, depending on your project type
|
| Push |
devices.platformEndpoint, or the user and device token together |
| RCS |
phoneNumber* |
| SMS |
phoneNumber* |
| Web push | The user and browser token together |
email or userId, depending on your project type
|
* If multiple user profiles share a phoneNumber, only one of them receives a
given marketing SMS or RCS campaign in an 18-hour period. Iterable skips the
others.
# Journey sends and the 18-hour rule
For journey sends from marketing channels, Iterable checks the campaign ID and recipient ID across all of a user's visits to a journey. A user who re-enters a journey, has simultaneous entries, or loops back through a Loop tile doesn't receive the same marketing campaign again within 18 hours.
Messages that the 18-hour rule doesn't apply to, such as transactional messages, send each time a user reaches the tile. This includes each pass through a Loop tile. For more information, read Sending messages on each loop pass.
# Embedded messages and the 18-hour rule
Embedded messages don't follow the 18-hour rule. Embedded messages appear passively in your content, where users can scroll past them. They don't interrupt users or send notifications, so making a user eligible for the same campaign more than once carries little risk. Sending an embedded campaign also doesn't deliver a message. It marks the user as eligible to see the message, so your app displays the message when the user scrolls to the embedded placement.
# Transactional messages and the 18-hour rule
The 18-hour message deduplication rule doesn't apply to transactional messages. You can send the same transactional campaign to the same user more than once, such as when a user requests two password resets.
# API sends and the 18-hour rule
By default, API sends through POST /api/campaigns/trigger
and all POST /api/{channel}/target endpoints ignore the 18-hour rule.
These endpoints share a parameter called allowRepeatMarketingSends that
controls whether the 18-hour rule applies.
- It defaults to
truewhen omitted from the request, and the 18-hour rule is ignored. - To apply the 18-hour rule to API sends and prevent duplicate marketing sends,
set
allowRepeatMarketingSendstofalse. - Transactional campaigns ignore this parameter. Setting it to
falsedoes not apply the 18-hour deduplication rule to transactional campaigns. - The
POST /api/{channel}/targetendpoints ignore this parameter when the request includes asendAtvalue in the future (scheduled sends).
# Why is my campaign not sending?
# Data feeds
If you see a campaign that's stuck in the sending stage, check your data feed configuration and your data source logs for errors. If you find errors, contact your development team and Iterable Support to help identify the root cause.
# DNS configuration (email channel setup)
If you and your team aren't receiving emails or proofs, make sure your DNS is set up correctly.
If your team is using Amazon SES, you can find DNS settings in Iterable on the Settings > DNS Setup page, and check that all records are verified.
If you use another ESP to send email, check your ESP's configuration and logs, or contact support.
# Limitations within your project
Is your campaign using experiments or throttling? Some teams use experiments or rate limiting to gain insight into the types of emails that work better than others and maintain stabilization for a web infrastructure.
If you're using an experiment, make sure that the experiment configurations are correct, and see which factors (i.e. time zones, send time, etc.) might contribute to the campaign not finishing yet.
If you're using rate limiting, double-check the rate limits within your channels settings, and also check to see which other active campaigns or journeys might cause you to hit the rate limit.
# Is the triggered campaign in a running state?
In order for a triggered campaign to send a message, it must be in the running state. To put a triggered campaign in the running state, activate it.
Journey campaigns automatically transition from ready to running when the first users arrive at their associated journey tiles. By contrast, triggered campaigns do not automatically transition from ready to running when a triggering API call is made.
# I updated my campaign, but some users still get the old one, why?
One of the most common reasons users might receive an old version of a campaign is that the campaign is part of an experiment that has unchanged variants associated with it. If some users are getting versions of your campaign that don't reflect recent updates:
Check if the campaign has an active experiment. Experiments can override standard template updates, causing content from the previous version to be sent.
If a campaign is associated with an experiment, review each variant to ensure that the template and its content are up to date.
Cross-check current templates with the previous version to confirm that all updates have been applied for all variants.
If possible, send test emails for each variant to confirm that the correct content is being delivered.
NOTE
If outdated content has already been sent, update the experiment immediately and determine if affected users should receive the correct content in a follow-up send.
# Get support
If you're still not sure what is causing unexpected results with your campaign, contact Support.