Dynamic Templating for Inline Lists

Personalize SMS, email, and open channel messages for each member of your audience using dynamic content.

We improved Airship's templating scheme to support dynamic content when sending to SMS, email, or open channels using an Inline List An ad-hoc, CSV-formatted list of email, SMS, or open channel addresses that you want to register and/or send a message to. Unlike static lists or segments, you upload this list while creating your message. or the create-and-send API. With dynamic content, you can customize messages for recipients based on demographic information, the interests of your audience, and other information that you include with your audience. Now you can send a single message to a wide audience while ensuring that the message is relevant to each individual member of your audience.

If your users indicate interests in different categories of products, you can send a single message with relevant content for the different categories that your users are interested in. If you know your audience's location, you can use dynamic content to notify users about events nearest to their location. In both cases, you can send a single message rather than sending multiple messages or segmenting your audience.

For example, if you wanted to tailor your message based on your audience's interest in footwear, you might send a message with the following logic: {{#eq category “Footwear”}}Get up to 60% off shoes!{{else}}Check out these sweet deals!{{/eq}}

To take advantage of dynamic content, you must use an Inline list or the /create-and-send API when sending SMS, email, or open channel messages. In the CSV or JSON payload representing your audience, you will include columns or keys informing the logic you want to use to personalize content. When creating your message, you'll insert evaluation logic into the fields in your message. Presently, we support equality operators ({{#eq}}) and if-else statements ({{else}}), with more to come.

For more information about Inline lists and dynamic content, see: