Personalization Guide for App Content PZ
Follow the steps given here to create personalization in the JSON code editor.
Personalization in Netcore CE enables the creation of dynamic content that adjusts based on user data and behavior.
The personalization syntax follows a structured format, helping the SDK understand what data to retrieve and how to handle cases where certain data might be missing.
Basic Personalization
Event Payload Personalization
Use the following format to personalize content using event payload data. If the specified event property is unavailable, a fallback value will automatically be used.
Syntax
[%__payload-property$event_name$default_value__%]
User Attribute Personalization
Use the following format to personalize content with stored user attributes. If the specified attribute is unavailable, a fallback value will be used.
Syntax
[%__user_attribute$netcore_user_attribute$default_value__%]
Syntax Breakdown
Every personalization expression is enclosed within special markers and contains three essential components. Let's break down the structure.
Enclosing Markers
- Each signature must start with
[%__ and end with __%]. - These markers indicate that the content needs to be processed dynamically.
Component Separation
- The signature contains three components, separated by the $ symbol.
- All three components are required for a valid signature.
Component Details
| Component | Description |
|---|---|
| User Attribute Property | Specifies which event property or user attribute should be retrieved. |
| Attribute Type Identifier | |
| Default Value |
By following this structure, you can easily integrate and personalize In-App Messages while ensuring a seamless experience.
Examples
Event Payload Example
[%__purchase_amount$order_completed$0.00__%] (Inserts purchase_amount from order_completed event, defaults to 0.00 if missing)
User Attribute Example
[%__first_name$netcore_user_attribute$User__%] (Displays user's first_name, defaults to User if missing)
Updated about 12 hours ago