we're facing a strange issue with Adobe Analytics library, set as a tool, which is not loaded at run-time by the DTM library itself, as usually does.
We tried different libraries, both custom code (H.26 or H.27 versions) and automatic App Measurement, but no one was loaded in the head of page.
The obvious consequence is the "s is not defined" JS error (s is the Tracker Object) in console.
We deployed several Analytics tool libraries via DTM and this never happened.
We explored the Net console in order to find possible "Not Found" script requests but we just found the successful main DTM library one.
Any help to find possible debug options or solutions are really appreciated.
Thanks a lot
No it's not enabled but does not matter because I found out the reason why. I had a conflict with a Data Element evaluating a querystring parameter. This Data Element is based on 's' plugin and when the DTM tries to parse it, the 's' obj is probably not defined yet. I'm deep into solving it. Thanks anyway as usual ;)
That's right: when you define a data element in the interface, it gets evaluated before any of the tools, so s object does not exist yet.
If you are simply trying to set a data element to the value of a url parameter, there is an option in the Type dropdown for URL Parameter you can use.
If your data element is a Custom Script type, there are some built-in _satellite methods you can use:
_satellite.getQueryParam()
This one is case-sensitive so if you have foo=bar and you pass 'FOO' to it, it will not match.
_satellite.getQueryParamCaseInsensitive()
This one is case-insensitive so if you have foo=bar it will match on 'foo','FOO','Foo',etc..