Overview
Alerts can be personalized in the content creation step of Alert creation using the Text personalization button. To personalize, do the following:
-
-
- Click the Text personalization button.
- Add the attribute to be personalized in the Personalisation attribute field on the screen that pops up.
- You can specify user attributes as fallbacks for the personalized attribute. Note: User Attributes must be enabled in Inform Settings for this option to be available. For more information, refer to User Attribute settings.
- Click Copy and close to copy the personalized attribute to the clipboard.
- Paste the copied value in the message editor using standard keyboard shortcuts.
-
| info |
Naming convention to be followed for Personalization The names of the user attribute added for personalization can contain only the following: String characters, a combination of alphabets and numbers, and underscores. For example, the attribute name to be personalized can be username or user_name, or usernmae1, while user name and user name1 are not allowed. If the attribute name were to contain any character other than string characters or underscore or alphanumerics, for example, spaces, only numbers, or special characters, personalization would not work. |
Message Body
Hi {{username|default("{{UserAttribute['
USER_ATTRIBUTE_USER_NAME
']|default('user')}}")}}!
Your order {{orderid}} has been placed successfully.
Happy Shopping!
Team MoEngage
The following flow diagram depicts how personalization works when User Attributes are disabled.
Note: If the user attributes are disabled (post enabling), the standard SLA would apply to the subsequent API requests.
Message Body
Hi {{firstname}}!
Your order {{orderid}} has been placed successfully.
Happy Shopping!
Team MoEngage
Sample Payload with personalization
{
"user_id": "john_doe",
"payloads": {
"SMS": {
"recipient": "+1555555555",
"personalized_attributes": {
"firstname": "John",
"orderid": "#order HXY-12345-ZSDF"
}
},
"EMAIL": {
"recipient": "john.doe@moengage.com",
"personalized_attributes": {
"firstname": "John",
"orderid": "#order HXY-12345-ZSDF"
}
}
}
The firstname and orderid need to be sent when the request is triggered.