Once your message content has been defined, you can use test profiles to preview and test it. If you inserted personalized content, you can check how this content is displayed in the message, using test profile data.
Click Simulate content.
Click Manage test profiles to add a test profile.
Find your test profile with the Identity namespace and Identity value fields. Then, click Add profile.
Once you selected your test profile, you can close the Add test profile window.
From the Preview & test window, test profile data is added to the message content.
Select the type of device to preview content: iOS or Android.
You must check alerts in the upper section of the editor. Some of them are simple warnings, but others can prevent you from sending the message. Two types of alerts can happen: warnings and errors.
Warnings refer to recommendations and best practices.
Errors prevent you from testing or activating the journey as long as they are not resolved, such as:
The push version of the message is empty: this error is displayed when the push notification body or title is missing. Learn how to define push notification content in this section.
Surface doesn’t exist: you cannot use your message if the surface you have selected is deleted after the message creation. If this error occurs, select another surface in the message Properties. Learn more on channel surfaces in this section.
Push iOS/Android payload has exceeded limit of 4KB: the push notification size cannot exceed 4KB. To respect this limit, try to reduce the use of images or emojis. Learn how to manage your push notification content in this section.
For better deliverability, you should always use the phone numbers in the formats supported by the provider. For example, Twilio and Sinch only support phone numbers in E.164 format.
When your push message is ready, complete the configuration of your journey or campaign to send it.