You can personalize Message ActionsA configurable behavior that occurs when a user interacts with your message, e.g., opening a web page. using HandlebarsAirship’s message personalization syntax using double curly braces, more commonly known as {{handlebars}}. Use handlebars to insert variables and conditional logic in messages and templates.
, taking advantage of information specific to your audience to personalize your audience’s experience when they interact with your message.
Use properties from a custom event, attributes, or an uploaded list to personalize adaptive linksA mobile wallet pass link that supports templates for both Google Pay and Apple Wallet. When a user taps the link, Airship determines the user’s platform and generates the right pass for the user. , send your audience to their own, specific deep link, or send users to their accounts with web links.
Like messages, you can personalize actions using information from:
- AttributesMetadata that you can use to group and target your audience. Attributes differ from tags in that when evaluating users with attributes, Airship uses operators, e.g., equals, less than/greater than, contains, before/after, to determine whether or not to target a user. Supported attribute types are TEXT, NUMBER, and DATE.
- Properties from a Custom EventEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom events can trigger automation and journeys. You can code them into your app or website, or send them to Airship from an external source using the custom event API. Custom events contain
propertiesthat you can use to personalize messages. that triggers a journey or automation rule - Column names (properties) from an Uploaded AudienceA reusable audience list that you create. Uploaded lists are static and updatable. In the API, they are referred to as static lists. or
/create-and-sendpayload — for SMS, email, and open channels only - External Data FeedsA connection to an external API. When you send a message, Airship uses a response from that API to personalize messages.
If two personalization variables use the same name, Airship generally attempts to use the most recent variable. In general, this means that Airship will use a property from an custom event or uploaded audience rather than an attribute with the same name, but you may want to make sure your variables use unique names to prevent confusion.
You should set a default value when personalizing message actions to ensure that personalized actions resolve correctly, even if the value you use to personalize the action does not exist.
I'm a big fan of {{$def product_name "stuff" }} from This Cool Company.
Go to {{$def product_url "https://www.mysite.com"}} to get your own!Personalized Deep Links
A deep link sends a user to a specific location in your app. If you’ve configured deep link templates — deep links with merge fields that you can personalize for your audience – you can fill templated fields in the path of your deep link with personalizable properties.
For example, if your deep link template is:
https://example.com/products/{{category}}/{{product_id}}You would see the category and product_id fields when adding a deep link action. You could personalize the deep link with values from the event or data that you use to personalize your message.
Personalize Adaptive Links
Adaptive linksA mobile wallet pass link that supports templates for both Google Pay and Apple Wallet. When a user taps the link, Airship determines the user’s platform and generates the right pass for the user. take query parameters that personalize information in the pass that each member of your audience installs. For example, if you want to add a user’s name, captured in a custom event, to a pass, you might add ?name={{name}} to the adaptive link URL.
When sending a message supporting personalization, you can reuse personalizable information in the adaptive link to personalize the passes that your audience receives.
In general, you’ll need to know the field names in your wallet templates, and then use handlebars to produce the values that you want to add to the pass that your audience installs.
Click Add another field to add additional parameters to your adaptive link.
Personalize Web Page Action
You can personalize a web page URL to send your audience to a relevant page when they interact with your message.
Insert handlebars in your URL to personalize the URL for each individual recipient. You might want to personalize URLs to send a user to their account login or the page of a product they visited.
Example URL: https://www.example.com/user?id={{name}}&cart={{cart_id}}
Standard handlebar syntax (using double curly braces) is URL encoded, so you can personalize individual parameters in a URL. Use triple braces to escape URL encoding and personalize a complete URL — {{{url}}}.
Personalize Share Action Text
You can personalize the Share Text that users will see when they share your message on social networks. This can help you shape the way your audience talks about you, and make it easier for your audience to share their experiences with their groups of friends.
I highly recommend {{product.name}} from Cool Company!
Go to {{product.url}} to get one!Personalize Message Center Actions
Message center actions support the same personalization sources as a message itself. For example, if you set up an automation based on a custom event trigger — like an abandoned cart — to send a push notification with a message center action, you can personalize both the push notification and the message center message from the same information in your custom event.
When you select a message center action, you can select a template or create a new page in our Interactive Editor.
See Content Templates to learn how to create Message Center templates.
Personalize Media URLs
You can use HandlebarsAirship’s message personalization syntax using double curly braces, more commonly known as {{handlebars}}. Use handlebars to insert variables and conditional logic in messages and templates. to personalize media URLs, helping you maximize the impact of your messages for each member of your audience.
You should use the default handler ($def) when personalizing media URLs to make sure that your media URL resolves appropriately if variables in the URL are empty or don’t exist.
https://example.com/{{$def user_profile_image "default.png"}}In the Content step a message, enable Media.
Enter your URL with handlebars. You can personalize URLs using attributes, custom event properties, etc.
For App channels, set the Media type.
