Personalisation of Campaigns

User Attributes that have been tagged up to the platform from an App or Site, or synced with the platform via API can be used to personalise comms. For details on adding attributes see the following articles:

• App: https://support.xtremepush.com/hc/en-us/articles/208460869-Tracking-User-Attributes-like-Name-Balance-etc-with-tags
• Web: https://support.xtremepush.com/hc/en-us/articles/208460025-Measurement-Tagging-on-site-events
• API: https://support.xtremepush.com/hc/en-us/articles/210324225-Tag-Attribute-syncing-methods

This article covers how to personalise content in campaigns and the syntax related to campaigns.

The Personalisation Button

Keep an eye out for the personalisation button in content editors. If you press this it will allow you to search for available attributes and add them:

Syntax to only send message if personalisation is possible

If your message  will not make sense with out the variable user attributes in the message then the format of personalisation is as follows:

{{USER-ATTRIBUTE_NAME}} 

 Double curly brackets around your attribute name.

For example a message like:

Hi Sam, your balance is €20 tap today to top-up at a 10% discount 

May be created using the following attribute for personalisation:

Hi {{user.first_name}}, your balance is €{{user.balance}} tap today to top-up at a 10% discount 

This message will only send to users where personalisation is possible as it would not make sense without the attributes filled in.

You will see the personalisation button on many of the content fields on the xtremepush platform. Clicking this button will give you access to a drop down of available attributes selecting an attribute will add it in the above format.

It is possible to create personalised content with alternative messaging where personalisation is not possible.

Alternative Text when personalisation is not possible

If you are doing relatively simple personalisation like just adding a user then you can specify alternative text using the following format:

{{USER-ATTRIBUTE_NAME || 'ALTERNATIVE'}}  

This allows you send a personalised message where the attribute is available but still send a fallback message when not.

• {{ user.first_name || 'Hi' }}, we've added great new feature x to our app check it out
• Will send a personalised or non-personalised message based on availability of the users name:
• Sam, we have added great new feature x to our app check it out
• Hi, we have added great new feature x to our app check it out

You can do more advanced alternative messaging where the attribute is combined with some text and there is also alternative text: 

{{' SOME Text ${USER-ATTRIBUTE_NAME}' || 'ALTERNATIVE'}} 

This allows you to use a personalised attribute with accompanying text where the attribute is available but still send a fallback message when not.

• {{ 'Hi ${user.first_name}, we' || 'We' }} have  added great new feature x to our app check it out
• Will send a personalised or non-personalised message based on availability of the users name:
• Hi Sam, we have added great new feature x to our app check it out
• We have added great new feature x to our app check it out

What Happens if I have no alternative and I don't yet have a users Attributes for personalisation 

Users with attributes will get a personalised message. For users who are missing attributes, xtremepush will start the progressing of trying to send a message but it will stop when it finds there are missing attributes. This is all logged in the notification log. For example you may see an entry for your campaign in the logs  that has a 1 in the targeted, column and a zero in the sent column:

If you click the drill icon on the far right you will be taken to a detailed log page and will be able to see "not personalised" as the reason for failure to send:

 This is preferable to sending a message that makes no sense or contains something like Hi{{firstname}} but if you have a lot of failures of the "not personalised" you should consider adding alternative text as described above.