Dynamic content
Dynamic Content allows you to personalize your push messages by modifying the message content with corresponding Tag values that you collect from your users. This allows you to address your user by name, and use any of his or her preferences in the message to make it relevant for every single user.
Personalizing messages sent via API with Dynamic Content
To personalize messages sent via API with Dynamic Content, please ensure you use the appropriate syntax for Dynamic Content placeholders.
1. To reach out to non-tagged users with a message containing some default Tag value, use the following Dynamic Content syntax: {Tag_name|format_modifier|default_value}
.
For example, the message “Hello {Alias|CapitalizeFirst|friend}!” will be sent to users with no alias specified and will look as “Hello friend!”.
2. To ignore non-tagged users, add a Dynamic Content formatted as follows: {Tag_name|format_modifier}
. When there is no closing ”|” character, Ignore non-tagged considered to be checked.
For example, a message “Get a -20% coupon in {Restaurant|CapitalizeFirst} now!” will be sent only to those users who have any Tag value set on their devices or specified in “dynamic_content_placeholders” parameter of an API request. Non-tagged users won’t receive any message.
3. To send a message to non-tagged users, format Dynamic Content as follows: {Tag_name|format_modifier|}
. When there is a closing ”|” character, Ignore non-tagged considered to be unchecked.
For example, a message “Get a -20% coupon in {Restaurant|CapitalizeFirst|} now!” will be sent to all the audience targeted including users with no Tag values specified. As a user has no Tag value and no default value is specified, non-tagged users will receive a message as is — “Get a -20% coupon in {Restaurant|CapitalizeFirst|} now!”.
Results
As a result, imaginary Klaus and Annie will receive push messages from the same campaign, but personalized with their names and preferences: