Hello @mitchellt, I've consumed all the revelent documentation on event tracking, Tealium Events and Set Data Values extension, but I am still not understanding how to configure the following very basic use case: When a custom page event occurs, such as "tealium_event: modal_open", utilizing utag.link(), how do I listen for that event and map it to a unique Adobe event, such as event3? Questions: - Does the extension "Set Data Values" actually listen for variables being pushed into the data layer, or does it set a new variable for you basic on conditions? For example, if the code is firing a utag.link() function, and setting "tealium_event" to something custom, why do I need to then set it again with the "Set Data Values" extension? - Subsequently, if "Set Data Values" isn't listening for custom "tealium_event" values coming from utag.link() calls, is the current Tealium recommendation to write custom code to listen for these? - How does "tealium_events" work with Adobe AppMeasurement "Event Serialization"? - How do you configure a custom s.tl() call with Adobe AppMeasurement? Is that the screenshot you shared below? And if so, if I am interpreting that correctly it means a new "Set Data Values" extension needs to be configured for every s.tl() function that fires? Is that accurate? Thank you, Laura
... View more
The basic premise is this:
Our tag template logic includes conditions to check if any e-commerce variables are populated in the data layer (eg "order_id" populates "_corder"), and use those values for the default tag mapping
For example, for an e-commerce site that tracks orders, in the tag you may have to normally map "orderId" to "order_id", and the same for each of the other order data points.
By configuring the extension, you save yourself the trouble of setting up the mapping for these data points for every tag you use, as the tag would reference "_corder" for the "orderId" every time it was available.
... View more