Dynamic Yield helps businesses deliver digital customer experiences that are personalized, optimized, and synchronized. This destination leverages the Experience API to track meaningful events, so you can use the information for behavioral targeting, reporting, setting optimization goals, recommendations, and audience building.
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).
Automatic hashing: information is automatically hashed matching partner specifications.
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.
Use Destination filters to refine events and/or other properties matching your specific needs.
Endpoint
Required
Select your endpoint data center: EU or US.
API Key
User Identifier
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 its value in Your value
.
Event Mapping
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. See Event Mapping
in Configuration for more details.
Most properties can be remapped using our "Smart Mapping" feature.
User Identifier
user.dyid
user.dyid_server
partners.dy.session_id
session.dy
[1]
context.device.ip
context.device.ip
event_name
events[0].name
(event_name)
dyType
[2][3]
value
value
[2]
currency
currency
[2]
items.0.id
productId
[2][4]
items.0.quantity
quantity
[2][4]
items.X.id
cart.X.productId
[2]
items.X.quantity
cart.X.quantity
[2]
items.X.product.price
cart.X.itemPrice
[2]
id
uniqueTransactionId
[2]
user.email
hashedEmail
[2]
(event_name)
progress
[2][5]
search_term
keywords
[2]
Your event property
Dynamic Yield property name
[6]
[1] if no property is provided, the cookie _dyjsession
is used.
[2] This property is set in events[0].properties
.
[3] See Quick reference for more details.
[4] Included for add_to_cart, remove_from_cart and add_to_wishlist events.
[5] Set with VIDEO_STARTED
, VIDEO_FINISHED
or PREROLL_FINISHED
depending if the event name is video_start, video_complete or video_ad_complete respectively.
[6] See Custom Event Properties
in Configuration for more details on how you can send custom properties to Dynamic Yield.
Required
Your API key as generated in Dynamic Yield interface. More details are available by following this .
User identifier generated by Dynamic Yield and managed, with their client-side tags, via cookies. More details are available by following this (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.consistent_anonymous_id
is used.
Change the standard mapping (See ) between Dynamic Yield's events and yours or add new mappings.