Swrve’s rich customer profile data includes both default and custom user properties that give you a current and detailed picture of your users’ status. These user properties are then available for injecting personalized details into your campaign content, such as a customer’s name, a flight destination city, a favorite team, or a personalized coupon code. The process to create a tailored, personalized experience for your users is now easier than ever!
The manner by which Swrve personalizes your campaign content depends on the campaign channel and how a campaign is delivered to a user’s device. To make user properties available in triggered campaigns, such as in-app messages or push via API, the Swrve SDK downloads a pre-configured set of user properties that it then uses to personalize the content of a campaign at the moment it’s triggered. Before you can personalize campaigns with realtime properties, you and your development team must complete the following:
- Upgrade your app to the latest Swrve SDK that supports realtime personalization.
- Implement custom properties in your app and then configure the realtime user properties you want to use for personalization purposes. For more information, see Manage user properties or contact your CSM at firstname.lastname@example.org for assistance.
Swrve supports image personalization in your in-app message campaigns as of iOS SDK version 7.0.0, Android SDK version 8.0.0, and Unity SDK version 8.0.0.
As explained above, some types of campaigns use any default or custom property that your app sends to Swrve to personalize message content. As soon as Swrve receives the user property, it is immediately available for use in your campaigns. These campaign types include:
- Scheduled push notifications
- Triggered push notifications
Other campaigns use realtime user properties to download the property values to the user’s device ahead of time and then inject the personalized campaign content at the moment the user triggers the campaign. Realtime user properties are available for use in campaigns as soon as you configure them. These campaign types include:
- In-app messages
- Push via API campaigns
- Embedded campaigns
Additionally, triggered push campaigns also support using the payload values from the campaign trigger event.
|Campaign channel||Realtime properties||Custom properties||Trigger event payload values|
|Push via API||X|
|Email and SMS||X|
Personalize your campaign content
The process for personalizing your campaigns with user properties is the same, regardless of channel and campaign type. There are two ways to insert a user property in your campaign content:
- Select the property using the Insert property dialog
- Manually insert the property as text, using Swrve’s personalization syntax
Insert property dialog
To insert the user property using the Insert property dialog:
- On the Content screen of the campaign workflow, move your cursor to the point in the text where you want to insert personalized content and select Insert property.
- In the Insert a user property dialog, enter part or all of the custom property name in the Select item box and then select the property from the list of values.
- To include fallback text that displays if a user doesn’t have a value for the custom property, select Add custom text and then enter the fallback value. Or select Don’t show if you don’t want the content to display for that user.
The following examples demonstrate how to personalize your campaign content by including the customer’s name or coupon code.
Push notification (Batch and Push via API)
Push notification (Triggered)
Triggered push notifications also include the option to personalize your content with payload values from the campaign trigger event.
To insert a trigger event’s payload value into your push notification content:
- In the Insert property dialog, select Trigger event payload values.
- In the Select event list, select the event you want to use to trigger the campaign.
- Next, in the Payload list, select the payload key you want to use to personalize your content.
- Optionally, include fallback text that displays if a user triggers the event without the specified payload key.
Note that while the steps to personalize image URLs and single line text values are the same, the device preview renders personalized single line text and personalized images differently.
Single line text
When personalizing single line text values, the device preview value displays sample as a placeholder value. If you provide a fallback text value, that value replaces sample in the preview.
When personalizing image URLs, the device preview displays a placeholder image. If you provide a fallback value, Swrve displays that image in the device preview.
Similarly, if you provide a separate fallback image, that image replaces the placeholder image in the preview.
Insert as text using Swrve’s personalization syntax
When sending or creating campaigns via API or in bulk, use Swrve’s personalization syntax to include a dynamic user property value in your content:
To include fallback text that applies if a user doesn’t have a value for the custom property, add a fallback parameter: