@Gigazelle So DTM load page rules do not work with legacy s_code.js
implementation period? Strange this isn't mentioned in any of the
reference videos, they make it sound like s_code implementation through
DTM is completely optional. Or when you say page event image requests,
are you referring to grabbing values from Adobe variables like evars? My
current situation is that data elements pulling in evar values are
working fine with old s_code.js for my staging library (by setting path
Rahsing wrote... Hi, You can reference adobe variables thru data
elements by specifying the data element being referenced under the 'Set
As' option. For eg:- if you're trying to capture the page name, you can
create a JS object to capture this by document.title and then reference
this particular element (The syntax is %%). You could try
the data element method to see if your page load rule works too. Here's
some documentation for your reference. Let me know if this helps Rahul
My question is how...
Thanks for the reply Carey. From the look s of it, the is loaded at the bottom of the page,
so it's not in the header at all. Could this be the issue? Can we move
the s_code script line up to the header without any issue?
This is a two part question:1.I'm unable to get pageload actions to fire
through DTM. Page event works fine - does exactly what I expect it to
do. But I'm not able to get pageload to work at all. Here is my current
setup http://screencast.com/t/S17YM2Eo3TCWhen I use the debugger
extension in chrome I can see that the rule is firing
http://screencast.com/t/r3u7UBVIwhqHowever, evar53 is not set when I
check in omnibug. And like I said, when I do this through an event rule
instead, evar53 shows up ...
We are currently implementing DTM. We want to use it to implement new
variables going forward. However, there are a number of variables like
eVars and props that are currently being set on the page itself, hard
coded before the image request is sent. Ideally we would like to add DTM
to the site while still capturing these variable (making the full
migration and implement them all through DTM would be a very big
undertaking at this stage).The issue is that DTM does not include any of
I quickly ran in to the problem when trying to set up DTM that page load
rules did not work when I have the s_code present on the page (and
"s_code present" selected in DTM). I've been in touch with Adobes
support for weeks now and they have not been able to figure it out
(event rules work fine). I set up a test page with essentially just the
s_code and DTM and nothing
you check with a tool like Omnibug and DTM debugger you'll...
We've sat our laptops side by side and compared that we have the same
report (I'm using his saved project) - same segmenets, same timeframe,
same mertrics. Everything matches up perfectly, except his bounces are
15-20% higher than mine (it varies a bit but always in that range). Any
idea of what might be going on?
https://twitter.com/AdobeMktgCare/status/570944574979485696 Could this
cause browser specific numbers to drop? Chrome, Safari looks normal but
Firefox and IE took a big dip. Is this an issue on our side our Adobe's?