Dynamic Yield

This destination is currently under final review and will be available soon.

Dynamic Yield helps businesses deliver digital customer experiences that are personalized, optimized, and synchronized. This integration allows server-side tracking.

Key features

The Dynamic Yield destination provides the following key features:

• Events structure: our Events reference covers Dynamic Yield events, meaning that your data is properly bridged to the expected fields in an optimized way.

• Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

• Refined data: you can freely push additional information based on your specific needs (E.g. adding custom events and custom event properties).

• Smart mapping: data mapping can be readjusted using your datalayer defined fields.

• Send all properties: send all your event properties to Dynamic Yield with a single click.

Destination setup

Use Destination filters to refine events and/or other properties matching your specific needs.

Configuration

Settings	Description
API Key	Required Your API key as generated in Dynamic Yield interface. More details are available by following this LINK.
User Identifier	User identifier generated by Dynamic Yield and managed, with their client-side tags, via cookies. More details are available by following this LINK (See cookies _dyid and _dyid_server). When keeping "Default", the above two cookies are used to retrieve a value. Selecting "[Custom Property]", you can specify a property holding the related value. Regardless of the chosen option, If no value is available our standard property user.tcId is used.
Custom Property	When selecting "[Custom Property]" with the above User Identifier, you can Input your custom property name holding the user identifier (E.g. user.mycustomid).
Send All Properties	When activating this option all properties included in the root of your Commanders Act events are also sent to Dynamic Yield in the properties object. Properties with child/sub properties are converted into a single one using the underscore character "_" as separator (E.g. device_lifecycle_last_session_start).
Custom Event Properties	Map your custom event properties by setting their field names in Dynamic Yield property name and adding the field name holding the value in Your event property. E.g. if you input size in the Dynamic Yield property name and items.0.product.size [1] in Your event property, you will have a custom event property in Dynamic Yield called size with a value based on the content of the field items.0.product.size.

[1] Using "dots" (".") you can navigate deeper to the specific field you want to get the value of. See Events reference for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.

Quick reference

Commanders Act Events	Dynamic Yield Types (dyType)
add_to_cart	add-to-cart-v1
add_to_wishlist	add-to-wishlist-v1
generate_lead	newsletter-subscription-v1
login	login-v1
purchase	purchase-v1
remove_from_cart	remove-from-cart-v1
search	keyword-search-v1
sign_up	signup-v1
video_start video_complete video_ad_complete	video-watch-v1
[Any Other Event] [1]	[Not Set] [2]

[1] Custom events are also supported. [2] Dynamic Yield custom events don't have a type. More details are available following this LINK.

Field Mappings

Most properties can be remapped using our "Smart Mapping" feature.

Commanders Act Properties	Dynamic Yield Properties
User Identifier	user.dyid user.dyid_server
context.device.lifecycle.session_id	session.custom
context.device.ip	context.device.ip
event_name	events[0].name
(event_name)	dyType [1][2]
value	value [1]
currency	currency [1]
items.0.id	productId [1][3]
items.0.quantity	quantity [1][3]
items.X.id	cart.X.productId [1]
items.X.quantity	cart.X.quantity [1]
items.X.product.price	cart.X.itemPrice [1]
id	uniqueTransactionId [1]
user.email	hashedEmail [1]
(event_name)	progress [1][4]
search_term	keywords [1]
Your event property	Dynamic Yield property name [5]

[1] This property is set in events[0].properties. [2] See Quick reference for more details. [3] Included for add_to_cart, remove_from_cart and add_to_wishlist events. [4] Set with VIDEO_STARTED , VIDEO_FINISHED or PREROLL_FINISHED depending if the event name is video_start, video_complete or video_ad_complete respectively. [5] See Custom Event Properties in Configuration for more details on how you can send custom properties to Dynamic Yield.