When I setup a rule and go to my Adobe Analytics section, and specify it to be triggered as an s.tl call, there is a problem with using the custom code section. Apparently DTM seems to be overwriting s.linkTrackVars and s.linkTrackEvents so I cannot populate any Adobe Analytics variables from there.
There was a release that went last week that addressed this issue. Essentially, the Adobe Analytics code editor in DTM previously did not set linkTrackVars / linkTrackEvents for you (so this would need to be added to the code for it to execute appropriately), but with this release, it is not longer required to specifically include this code as the editor will set this for you.If you publish your property, this fix should take affect. If you have items in your publish queue you don't wish to publish, you can always go to your property settings and enable 'Selective Publish' in order to be able to deselect items in your queue to just push a property publish.
Just let me know if this issue persists.
Thanks so much,
Oh cool, now I don't have to go test it.
I'm on the fence as to whether or not that should be mentioned in the DTM doc. On the one hand, DTM is a tag manager, so it's supposed to be tool agnostic. The docs should focus on DTM not the tools you implement through it. The tools you implement through it should have their own documentation (and Adobe Analytics does), and you can readily find that information within that documentation.
On the other hand.. Since DTM is (now) an Adobe product, it would indeed benefit Adobe to have a certain level of "catering" to their own tools within it (Adobe Analytics, Target, etc.), including mentioning tips/caveats about their own tools within it. IMO it would be helpful if Adobe added ability for us to add comments to the DTM/Adobe Analytics/etc. online docs. This is a feature no online documentation should be without, and Adobe does indeed do this for *some* of their docs (e.g. the APIs on developer.omniture.com). That way people like you and I could easily go to the rules doc pages and put this caveat in there for others!
That would be awesome Rudi 🙂
If it in any way helps, yesterday I submitted it on ideas.omniture.com
I'd like to reopen this matter, so seems that the behaviour of s.tl() calls on Direct Call Rules still being strange. If I want to use UI interface + Custom Code (is more clean gather on UI a general evars/props/events/predefinedVars), 'events' and eVars are automatically added on s.licktrackvars, so if on custom code I add another extra, for instance a prop, simply it is added on array, so far everything correct.
The problem is when s.linktrackevents comes to action, if I'm having an event set up on UI, and then I want to add another on Custom Code, s.linktrackevents were overwritten. It isn't a huge issue, so through s.apl pluggin I can fix it, but would be good if you can clarify the exacte steps to do for that these are clear for everyone.
Also I'd like to execute s.linktrackevents/vars on console, since now appears None (althrough DTM debugger printing it).
I hope get an answer from you,
[img]Screen Shot 2014-11-23 at 23.30.06.png[/img]
[img]Screen Shot 2014-11-23 at 23.30.21.png[/img]
This bug has supposedly been fixed in April 3rd, 2014 release
Hi - I have the same issue. I can't set analytics custom code using s.tl() call.
I setup a test page with same exact custom page code for analytics.
. Any solutions to get around this?
I reached out directly in December to try and get more info to troubleshoot this issue, but didn't hear back. If possible, could you provide the following info if this issue still persists?
Thanks so much,