Explore topicsMake Every Message More Relevant
Adapt message content using permitted profile attributes and event context, with conditional templates and dependable defaults that keep experiences understandable when customer information is incomplete.
Make messages more useful across varied customer contexts.
Use supported customer attributes and event properties to adapt message content to the context available at send time.
Map each personalized element to a supported profile attribute or event property and identify when that value is available. A saved preference and the event that triggered a journey can provide different kinds of context. Check availability for the chosen channel instead of assuming every field follows a customer into every message.
Define clear content conditions so different audiences receive appropriate information without relying on unsupported assumptions about individual intent.
Use a small number of understandable conditions to choose content, such as a relevant plan, language or completed milestone. Define the alternative branch as carefully as the preferred one. Preview representative records for each condition so conflicting rules, unexpected values and unnecessary offers can be identified before a message reaches customers.
Provide useful fallback content when attributes are missing, and preview representative records before approving personalized messages.
Choose a useful default for nonessential information, such as a greeting, and use conditional logic when a missing value changes the meaning of the message. Some messages should be withheld instead of completed with a generic substitute. Test blank, missing and unexpected values alongside ordinary records, including links and the final rendered content.
Dynamic personalization connects available customer context with a clear content decision. Useful templates explain what to show, what to do when information is missing and when sending a message would be less helpful than withholding it.