When you type ${ in your message body, a dropdown appears with available variables. The following are the details for each variable.
Text variables
The text variable enables you to set a place for a text string, like “Subject line”.
You create the variable in the JSON editor, and then set the content for the variable in the Variables tab.
Unlike the other variables, the text variable doesn’t appear in the variables dropdown. Instead, any variable inserted in the ${ } format that isn’t recognized by the editor is treated as a text variable.
After you create your variable in the JSON editor, click it to display the Variable Settings, where you can edit the name and insert a placeholder and tooltip to display in the variable’s dedicated configuration field in the Variables tab.
NOTE: You can use the same variable name (case sensitive) in multiple places in the JSON. All instances of the variable share the same configuration, and the contents are set only once in the Variables tab.
User Data variables
Reconnect enables you to pull data from your section's user data feeds.
- Create a variable and select User Data from the dropdown.
- Click the user data variable to select the relevant feed property.
The variable structure is ${User data|FEED_NAME|PROPERTY_NAME} .
Notes:
- User data variables are currently supported in Email and SMS (Web and App Push coming soon).
- The user data feed and the messaging channel must use the same identifier (for example, email address).
Trigger-related variables
For each trigger type, include a variable related to the triggering event. For example, in a Cart Abandonment campaign, use product property variables related to the items left in the cart, like the product name.
- Set the variable in the JSON editor.
- Click the variable it configure its settings: The trigger's product property and the number of items.
Note that this variable does not appear in the Variables tab.
Important:
Some variables are converted to empty values. For example, in a Cart Abandonment message you insert variables for 3 items, but a user added only 2 items to the cart. The first 2 object variables of “Items in cart” are populated with values from the feed, but the third object’s value remains empty.
Cart Abandonment
Available trigger variables:
- Total cart value: The total price of all the items in the user’s cart.
-
Items in cart: You can use the following properties:
- Product quantity: Number of a particular product in the cart.
- Product total price: Total price of all instances of the particular product in the cart.
- All your product feed properties
- Default (when selected from the dropdown): ${Items in cart|sku|Item 1}
Product View
- Available trigger variable: Recently viewed products
- Available properties: All your product feed properties
- Default (when selected from the dropdown): ${Recently viewed products|sku|Item 1}
Price Drop
- Available trigger variable: Products with a price drop
-
Available properties:
- Price Drop (%)
- Price Drop ($)
- Previous Price
- All your product feed’s properties
- Default (when selected from the dropdown): ${Products with price drop|sku|Item 1}
Custom
-
Available trigger variables:
- Items in cart (for cart-related events only: Sync Cart, Add to Cart)
- Recently viewed products
- Structure: Strategy (fixed) | Attribute name | Slot #
- Available properties: All your product feed properties
Recommendation block variables
Use recommendation block variables to insert personalized product recommendations based on strategies you've created, using properties from your product feed.
- You can include up to 3 recommendation blocks: Select Recommendation Variable 1, 2, or 3 from the dropdown.
The JSON looks like this:
- Edit the variable as needed, listed from right to left (in the previous image, "item 1", "sku" and "Recommendation Block 1"):
- Slot number: The sequential number of the product from the API call, for a specific recommendation strategy.
- Product property: The property of a specific product as it appears in your product feed.
-
Recommendation strategy: Go to the Variables tab, and select the strategy to apply to this block:
Each strategy in the dropdown includes:- The strategy name (for example, "Homepage Affinity")
- The strategy's algorithm (for example, "User Affinity")
Click Create New Strategy to create a new strategy. The strategy is added to your section's assets.
Strategies that require additional context
Some strategies use algorithms that require context, which you select from the dropdown.
For example, for Purchased together with, you'll need to provide the context, such as Items in cart.
Algorithms that require context:
- Similarity
- Viewed together
- Purchased together / Purchased together Offline / Purchased together Offline & Online
Integration variables
Integration variables are a group of technical parameters that serve the integration call. These variables do not appear in the message and are mostly used by messaging providers to monitor and debug messages sent by Dynamic Yield. They don't have any additional settings, nor do they appear in the Variables tab.
| Variable | Values | Description |
|---|---|---|
| User identifier |
Email: Hashed email, Email, Other SMS: Phone number Push notifications: PushID |
The identifier type is determined in the channel integration. For example, if you set the identifier as hashed email when you set up your email integration, the dropdown for this variable will offer that option in an email message; whereas for an SMS message it will offer the phone number identifier. |
| Request ID | A unique numeric value | A unique ID generated by Dynamic Yield for each message request that Reconnect triggers. |
| Request timestamp | YYYY-MM-DDTHH:mm:ss.SSSZ | |
| Tracking pixel |
Example: <img src=\"https://www.acme.com/tremop/ |
Available for email only. Enables Dynamic Yield to track the email. For example, whether or not the email was opened. |
| Tracking link |
Wrapping link
Example: https://trem.dynamicyield.com/tremclk/?{redirectQuery} |
Available for email only. To track clicks and measure campaign performance, URLs that are retrieved from the product feed as variables (example: ${Items in cart|url|item1} ) are automatically wrapped by Reconnect before they're sent to your messaging provider. Learn more about Responsys template parameters. |
| Push tracking |
Example of the content the variable is converted to upon sending the message: { |
Available for app/web push notifications only. When push notifications are sent from Reconnect, you're required to add a tracking parameter to the reporting events, to enable Dynamic Yield to track the actions that are attributed to the push. Note: To use this data in the Track Engagement API, you'll need to extract the contents of the trackingData parameter from Firebase, and populate it into your engagement call. |