Skip to main content

Iterable - Mobile Push, SMS, & Web Push - Message Preparation

Learn how to prepare a message for use with Jacquard SMS and push optimisation

Updated yesterday

To deploy a Jacquard experiment from Iterable, you should have already created a data feed and set up your system webhook.

The setup process is the same for mobile push, SMS, and web push. The only difference will be which channel you select in Iterable.

1. Create a new campaign

Start by creating a new campaign.

Set up the campaign as you normally would by giving it a unique name and selecting the campaign type and audience.

2. Attach a data feed

Once you have selected the template, you'll enter the campaign editor where you'll need to attach the data feed you created for the campaign. Enter the Content module.

Scroll down until you see Data feeds on the left. Check the box for Connect data feeds for dynamic template creation and then select the data feed for this campaign using the dropdown menu.

Uncheck Cache data feed response. Check the Merge the data feed and user contexts and Use data feed alias options.

3. Insert handlebars code in the appropriate field

With your data feed attached, configure the Subject using the handlebars alias you created and the returned value variant_text in the following format:

{{{your_data_feed.variant_text}}}

You'll simply need to replace your_data_feed with the actual alias you chose. Using our WeeklyOffers data feed example, our SMS Message field looks like this:

4. Enable shorten and track (SMS only)

For SMS messages, ensure you enable Shorten and track in the Content module. You'll find it in the Links section just below where you set up your data feed. Jacquard uses Iterable's system link tracking and, therefore, requires you to use Iterable's native link shortening.

Minimum Jacquard message setup complete

With these minimum settings complete, you can now set up the remainder of your mobile push, SMS, or web push message as you normally do.

If this is a trigger you've set up, you can then push the trigger live following your normal process.

If this is a broadcast message, there's one additional deployment step you'll need to take.

Did this answer your question?