Omniture events do not fire / send data via DTM when using s.tl tracking methods
I am using Adobe Dynamic Tag Manager (DTM). I have a Direct Call Rule . I have
- install evars and props using the GUI
- I am using "custom page code" parameter to send events to AA using javascript. Javascript has some case statements and uses data items.
When I use the st method eg. track pageviews - yes. I can see that my events are firing and also props are dispatched - just like for a debug digital debug device.
When I use the s.tl method, for example, don't track pageviews - yes. I don't see my events firing, but evars and props are dispatched as per normal tracking.
Is this a known bug? Please note that everything is fine with javascript, events are set and fired correctly, so there is no problem with JS. Help me please.
source to share
For calls, s.tl
AA requires most events and variables to be "registered" to one or both of these two variables: linkTrackVars
and linkTrackEvents
.
The DTM does this automatically if you assign values in one of the built-in fields, but if you expose events and variables in the custom code section, you will also need to fill in linkTrackVars
and linkTrackEvents
.
linkTrackVars . All requisites, eVars and most other named variables should be specified here. The only exception is pageName
, but it doesn't hurt to enable it (AA automatically turns it on to keep track of which page the call was called on s.tl
). You shouldn't include an object prefix, so for example you should use "prop1" and not "s.prop1". If you have more than one variable, you must delimit a comma, no spaces, i.e. "Prop1, eVar1". If you have events that you want to track, "events" must be listed (but not the actual event, just the name of the variable, ie "Prop1, events")
linkTrackEvents . Besides placing your events in s.events
, you must also put them in this variable. You can usually just trick it s.linkTrackEvents=s.events;
and call it a day.
Example:
s.prop1='foobar';
s.events='event1';
s.linkTrackVars='prop1,events';
s.linkTrackEvents='event1';
See the online documentation for AA link tracking for details:
http://microsite.omniture.com/t2/help/en_US/sc/implement/link_variables.html
Note:
A back, there actually was a bug with the DTM and setting variables in the custom code section for calls s.tl
inside a rule. Basically the DTM was overwriting linkTrackVars
and linkTrackEvents
even if you don't insert anything into the inline fields, so there was no way to override or add to them. In short, it was not possible to set variables in the custom code section for calls s.tl
. Since then, Adobe has recognized and fixed this bug.
However, there is still an error with the correct configuration of the DTM events and variables in the custom code sections of your main tool and rule configuration. For reasons not clear to me, the DTM creates a separate AA object when a rule is run. It captures all the variables that you set inside inline fields in the main configuration of the tool, but it does not account for everything you set in custom codeblocks in the main configuration area. Adobe needs to fix this by specifying an existing AA object instead of creating a new instance of the object.
In the meantime, if this is your situation, the only workaround is to disable AA for your rule and instead create a new script in the Javascript / Third Party Tags section of the edit. Inside the script, set all the AA variables you want to keep track of, including linkTrackVars
and linkTrackEvents
, and then call s.t()
or s.tl()
as per the AA documentation. In other words, you need to bypass the built-in AA stuff DTM and just install and run AA manually.
If you are relying on Data Elements to pop variables in inline fields (like %foobar%
), you can instead use _satellite.getVar('foobar')
in custom code to reference the data item.
source to share