- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
01-15-2019 04:39 PM
I like to understand the best way to track adobe analytics s.tl() call , gone through the tealium documentation
Like to know the best way to track events [ s.tl() ] call which satisfies in all scenarios or use cases.
01-25-2019 04:04 PM
Hi @tester123 - that's a tall order "call which satisfies in all scenarios or use cases".
If you'll also review the docs on Adobe Analytics then you'll see that some things like link tracking can be set to occur "automatically". However for custom events meaningful to the site being tracked, you'll most likely use a Set Data Values extension to capture the variables you want when the custom event occurs. There's no overall 'fits every situation' rule for this.
Here's an example (image below) where we're setting the actual event (e30) and the other variables we want to capture at that time. It will help to review the Adobe docs on event tracking as well so that you can better understand event tracking. Then at the end is the 'Condition' which informs Tealium when to set these values. In your Adobe tag, the data layer variables have been mapped to populate the Adobe tracking pixel when it fires on the site as the result of a normal pageview, or utag.view() or utag.link() call.
I hope this sample helps - it does take a little time to set this up "the Tealium way" but when you get it working it's satisfying. Some interactive debugger sessions are also helpful for learning exercises.
10-29-2019 04:18 PM
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?
- 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?
Copyright All Rights Reserved © 2008-2023