I posted a different reply, but here's what you need to do:Don't define
s as window.s, it will clear anything that DTM has already done.Set
s.products as normal, and always use s, even if your global SiteCatalyst
object is something else.Add "products" to s.linkTrackVars for any
custom links. DTM won't do this for you.That's it. I'd also recommend
using data elements when possible to set the product ID / SKU, or any
other information needed in the products variable.
I see how this can be confusing, but there is a definitive answer to
this. It is actually quite simple. In both page load rules or those
configured to send a page view, you will just need to open the customize
code section of adobe analytics and set s.products. You can use a data
use s.products, even if the SiteCatalyst object is something other than
s. Also, don't set it on the windows scope. The custom code is just a
One thing to remember is that DTM is a tool to allow you to do things
faster. In this case it won't necessarily track videos for you because
there are so many different video providers, each with its own method
for tracking. If you are looking to track HTML5 videos the event based
rules can help with that. However if you are using another video service
VideoJS, Flowplayer, etc.), you can use DTM to add the API code to
listen for t...
These should work just fine out of the box. Check your s_code to see if
you have any unique configurations for these, such as using the
s.linkHandler, s.downloadLinkHandler, or s.exitLinkHandler plug-ins. If
you are, remove them just in case. If you have the link settings
configured in the s_code, it will trump any settings you have in DTM.
Otherwise DTM's settings will be applied. If you still have issues try
getting rid of your current s_code and instead pasting a brand new copy
of the AppMeas...
This article references checking the actual code file, but to make it
easier you can also look at the _satellite object in the Console if your
web browser._satellite.buildDate = the last build date of either the
production or staging library_satellite.publishDate = the last date the
production library was last publishedThese might be beneficial to pass
into a prop or an eVar to see the effects of caching with the data or
other troubleshooting purposes.
YES. In my mind the fact that this happens almost makes visitor
stitching worthless. It's great that it stitches multiple devices after
the fact, but if it can't even stitch the visit together that causes
huge problems, especially with campaigns. If I come to the site with
campaign A, add some stuff to my cart, start the checkout, and then
login during the checkout, all of that stuff that I did previously is
worthless. Thus is a MUST HAVE feature, and something that is already
expected of it.
When viewing a custom conversion / eVar report, it would be great to be
able to view what the allocation and expiration is for that variable.
Not all users have access to view this in the Admin, and even those that
do, it makes it a pain to have to memorize or refer to another location
to see what the settings are for the variable. In addition, it would be
great if there were a link to the help section next to these settings so
that users that aren't aware of what they do can self educate and