Journeys are a great way to automatically send messages to your users when they reach important stages in the customer lifecycle. Whether you want to send a cart reminder email, happy birthday message, or promo code, journeys can do it all!
Message tiles send your users a message when they reach that stage of the journey. The following message tiles are available:
- Channel optimization — Sends the message on the channel where each user is most likely to engage (based on past engagement data)
- Email — Sends an email to the user's email inbox
- Embedded message — Displays an embedded message in your app or website to users who pass through the tile
- In-app — Sends an in-app message to your mobile app or website
- Push — Sends a push notification to the user's phone or tablet
- RCS — Sends an RCS message to the user's phone
- SMS — Sends a text message to the user's phone
- Web push — Sends a web push notification to the user's browser
- WhatsApp - Sends a WhatsApp message to the user's phone or device
Read on to learn how to set up your journey's message tiles.
# In this article
# How campaigns work in journeys
When you add a message tile to a journey, it creates a new campaign. In the message tile, you define the campaign's content by selecting a template and configure channel-specific delivery settings. See Setting up message tiles.
Journeys send the message when a user arrives in the message tile, which means all campaigns that you build in a journey are triggered campaigns.
# Sending journey campaigns
To publish your journey, all message tiles must be complete and meet campaign
content requirements. When you publish your journey, its campaigns move from
Draft to Ready status. Once the first user reaches a message tile, the
campaign changes to Running status and users receive the campaign message.
# Editing a campaign for a published journey
When you edit a published journey, you work in a draft version of the journey. To learn more, see Editing Journey Drafts in Studio.
Campaign content edits are an exception to the draft-and-publish flow, as content edits are not gated by journey publishing. When you save an edit to campaign content for a message tile that already exists in the published journey, the change takes effect immediately and users receive the updated version.
NOTE
For large campaign edits, Iterable recommends creating a new message tile in your journey draft and rerouting the journey path to it. The new tile's campaign won't send until you publish the draft. This approach lets you control when your changes go live. To keep a record, you can leave the previous tile disconnected on the canvas, with a note that describes your changes.
# Setting up message tiles
Drag a message tile onto the Studio canvas and double-click it to open the tile settings menu. You can tweak these settings to make sure each user receives the campaign in the right place and at the right time.
You can base a message tile's content on one of your project's reusable templates or on the template of an existing campaign or another journey's campaign, or you can start from scratch. When you select an existing template, Iterable copies the content from it to a new template ID that is attached to your campaign. Changes to the copy don't affect the original template.
When you're finished setting up a message tile, click Create campaign to save the tile settings and complete the setup.
The available settings vary by channel.
# Channel Decisioning tiles
Want to send a campaign to each user on their preferred channel? Channel Decisioning tiles use past engagement data to determine where each user is most likely to engage. When each user arrives in the tile, Iterable determines which channel a user has engaged with the most, and then sends the message to that channel.
NOTE
Right now, Channel Decisioning tiles only work for email, SMS, and push campaigns.
| Setting | How to use it |
|---|---|
| Send channels | Select the channels you want Iterable to choose from when deciding where to send this message. |
| Unable to determine user channel preference | Sometimes Iterable won't have enough or the right kind of data to determine which channel a user prefers. Use this section to prioritize fallback channel(s) or tell Iterable to choose one for you. |
Once you've configured and saved these two settings, you'll set up the campaigns for each channel within the tile as usual.
# Email tiles
| Setting | How to use it |
|---|---|
| Campaign name | Give your new email campaign a name. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing email templates. |
| Quiet Hours | Turn on Quiet Hours to prevent this campaign from being sent during certain hours of the day in each user's time zone. |
| Send Time Decisioning | Turn on Send Time Decisioning for this campaign to have Iterable select the ideal delivery time for each user. |
| Ignore Frequency Cap | Disable Frequency Management when this campaign sends. (Marketing messages only.) |
| Conversion events | Select the event or events that you want to track as conversions for this campaign. |
Attribute only conversion events with explicitly set campaignId field | If you select this option, incoming events must have a campaignId field that matches your campaign's ID to count as a conversion. |
| Attribute any conversion events received within set period | If you select this option, any incoming events that arrive within your specified time frame after the campaign is sent will count as conversions. If multiple campaigns use the same conversion event, the conversion is assigned to the campaign that was sent most recently. |
| Create A/B experiment | Create an experiment for this campaign to test different subject lines, sender/from names, preheader text, and more. |
# Embedded Message tiles
Embedded Message tiles display an embedded message in your app or website to users who pass through the tile.
| Setting | How to use it |
|---|---|
| Campaign name | Give your new embedded message campaign a name. |
| Placement | Select the placement within your website or app where the embedded message should be displayed. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing embedded message templates. |
| Display priority | Determines which campaign should be displayed when a user is eligible for multiple active embedded message campaigns. Drag the campaigns to set the display priority order for the placement. |
| Display until | Determines how long the campaign should be displayed. Specify the date and/or user profile update that should end the campaign for each user. (Journey is off or archived is selected by default, since embedded messages can only be sent from a journey while the journey is live.) |
NOTE
All users who pass through an Embedded Message tile are eligible to see the associated embedded message. However, the Display Priority and Display Until criteria determine if and for how long the message is displayed to each user.
# In-app tiles
| Setting | How to use it |
|---|---|
| Campaign name | Give your new in-app campaign a name. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing in-app message templates. |
| Quiet Hours | Turn on Quiet Hours to prevent this campaign from being sent during certain hours of the day in each user's time zone. |
| Destination | Select the apps and websites where you want to deliver the in-app notification. All mobile apps is selected by default, but you can change this to All websites, Everything (all of your apps and websites), or choose Custom to select only some of your apps/websites. |
| Display priority | Set the level of urgency for this campaign. Messages with the highest display priority ranking are delivered to your users first. |
| Conversion events | Select the event or events that you want to track as conversions for this campaign. |
Attribute only conversion events with explicitly set campaignId field | If you select this option, incoming events must have a campaignId field that matches your campaign's ID to count as a conversion. |
| Attribute any conversion events received within set period | If you select this option, any incoming events that arrive within your specified time frame after the campaign is sent will count as conversions. If multiple campaigns use the same conversion event, the conversion is assigned to the campaign that was sent most recently. |
| Create A/B experiment | Create an experiment for this campaign to test different subject lines, sender/from names, preheader text, and more. |
# Push tiles
| Setting | How to use it |
|---|---|
| Campaign name | Give your new push campaign a name. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing push notification templates. |
| Quiet Hours | Turn on Quiet Hours to prevent this campaign from being sent during certain hours of the day in each user's time zone. |
| Send Time Decisioning | Turn on Send Time Decisioning for this campaign to have Iterable select the ideal delivery time for each user. |
| Ignore Frequency Cap | Disable Frequency Management when this campaign sends. (Marketing messages only.) |
| Destination | Select the app or apps where you want to deliver the push notification. All mobile apps is selected by default, but you can click Custom to select only some of your apps. |
| Conversion events | Select the event or events that you want to track as conversions for this campaign. |
Attribute only conversion events with explicitly set campaignId field | If you select this option, incoming events must have a campaignId field that matches your campaign's ID to count as a conversion. |
| Attribute any conversion events received within set period | If you select this option, any incoming events that arrive within your specified time frame after the campaign is sent will count as conversions. If multiple campaigns use the same conversion event, the conversion is assigned to the campaign that was sent most recently. |
| Create A/B experiment | Create an experiment for this campaign to test different subject lines, sender/from names, preheader text, and more. |
# RCS tiles
NOTE
To add an RCS message tile to a journey, you need an RCS message type and an RCS sender in a launched state. See Setting up RCS and RCS Registration Statuses.
| Setting | How to use it |
|---|---|
| Campaign name | Give your new RCS campaign a name. This name displays in the message tile and in the journey. It does not display to recipients. |
| Labels | Apply labels to the campaign. See Working with Labels. |
| Content | Add content to your message. Click Browse templates to attach and edit one of your existing RCS templates or Start from scratch to create a new template. |
| Locale | Select locales, if needed. |
| Send test message | Specify if you want to send a test message to yourself, an internal list, as random users, or to another user. |
| Edit | Specify how you want to edit the template after it's created: preview with data, open in a new tab, or replace the existing template. |
| Quiet Hours | Turn on Quiet Hours to prevent this campaign from being sent during certain hours of the day in each user's time zone. For RCS, Quiet Hours is off until you turn it on. |
| Conversion events | Select the event(s) that you want to track as conversions for this journey campaign. |
Attribute only conversion events with explicitly set campaignId field | If you select this option, incoming events must have a campaignId field that matches your campaign's ID to count as a conversion. |
| Attribute any conversion events received within set period | If you select this option, any incoming events that arrive within your specified time frame after the campaign is sent will count as conversions. Last-touch attribution uses a window of 1–168 hours. |
# SMS tiles
NOTE
To send SMS messages from a journey, you must have an SMS provider set up for your project.
| Setting | How to use it |
|---|---|
| Campaign name | Give your new SMS campaign a name. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing SMS templates. |
| Quiet Hours | Prevent this campaign from being sent during certain hours of the day in each user's time zone. For SMS messages, Quiet Hours is turned on by default. |
| Send Time Decisioning | Turn on Send Time Decisioning for this campaign to have Iterable select the ideal delivery time for each user. |
| Ignore Frequency Cap | Disable Frequency Management when this campaign sends. (Marketing messages only.) |
| Conversion events | Select the event or events that you want to track as conversions for this campaign. |
Attribute only conversion events with explicitly set campaignId field | If you select this option, incoming events must have a campaignId field that matches your campaign's ID to count as a conversion. |
| Attribute any conversion events received within set period | If you select this option, any incoming events that arrive within your specified time frame after the campaign is sent will count as conversions. If multiple campaigns use the same conversion event, the conversion is assigned to the campaign that was sent most recently. |
| Create A/B experiment | Create an experiment for this campaign to test different subject lines, sender/from names, preheader text, and more. |
# Web push tiles
| Setting | How to use it |
|---|---|
| Campaign name | Give your new web push campaign a name. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing web push notification templates. |
| Quiet Hours | Turn on Quiet Hours to prevent this campaign from being sent during certain hours of the day in each user's time zone. |
| Conversion events | Select the event or events that you want to track as conversions for this campaign. |
Attribute only conversion events with explicitly set campaignId field | If you select this option, incoming events must have a campaignId field that matches your campaign's ID to count as a conversion. |
| Attribute any conversion events received within set period | If you select this option, any incoming events that arrive within your specified time frame after the campaign is sent will count as conversions. If multiple campaigns use the same conversion event, the conversion is assigned to the campaign that was sent most recently. |
| Create A/B experiment | Create an experiment for this campaign to test different subject lines, sender/from names, preheader text, and more. |
# WhatsApp tiles
| Setting | How to use it |
|---|---|
| Campaign name | Give your new WhatsApp campaign a name. |
| Content | Add content to your message. Click Choose a template to attach and edit one of your existing WhatsApp templates. |
| Conversion events | Select the event(s) that you want to track as conversions for this journey campaign. |
# Testing journey campaigns
You can test your campaigns with template preview tools and send proofs from your journey. To learn more, see Testing and Publishing Journeys.
In addition to supporting personalization with Handlebars{{fieldName}}.
If your journey includes an upstream Live Data{{liveData.objectName.fieldName}}
in your campaign content. To learn more, see Using Live Data in Journeys
For testing journey campaigns, use representative sample data that mirrors the
trigger's data fields or the liveData structure that your journey provides at send time.
# Analyzing campaign performance in journeys
Once your journey is live, you'll see campaign performance metrics show up on your message tiles. To learn how to customize which metrics appear on a journey's message tiles, see Monitoring Journey Engagement.
To see more in-depth performance data for your journey's campaigns, click View Journey Insights.
# Want to learn more?
For more information about some of the topics in this article, check out this Iterable Academy course. Iterable Academy is open to everyone—you don't need to be an Iterable customer!