Matthew,I'm not aware of any issue like this, but I've asked a member of
our team to reach out to you to get some more information that will help
us investigate.Thanks,Shawn
George,Can you please elaborate on what kind of problems you're having?
I'm not aware of any widespread problems with this, but I'd be happy to
look into it more if you can provide some additional
details.Thanks!-Shawn
I'm reading the original question again and I think I misunderstood what
was being asked. So, first, if you are trying to reference the element
being targeted by the event based rule, the 'this' object will refer to
that element. You can then get what you need in a variety of ways. If
you want any of the attributes that are already Javascript properties,
such as 'href', you can simply reference 'this.href' to get that value.
To put that value in an event, you could put %this.href% and it will
re...
Marco,Because of the way the different pieces of code are scoped in the
engine, the exact scenario you describe isn't possible. However, you
could do something like this:1) Create the data element(s) you want.
Instead of referencing the target object directly, reference a copy of
it (let's use "myTarget" in this example). We'll want to scope myTarget
at the global level so it can be accessed anywhere. So, your data
element might return something like "window.myTarget.href" if you wanted
to retur...
Craig,Yes, non-visible elements in DTM still trigger "enters viewport",
as we don't look to see if something's visible. You can use CSS
selectors to help narrow the focus of what the engine matches against
though. See my earlier reply for details.Best,Shawn
Taylor,It shouldn't take a few hours to update, but it can take up to an
hour for changes to appear in the production library when publishing to
Akamai because their servers around the world need time to clear the
cached copy of your previous library. We are continually working on ways
to optimize this timeframe and hope to decrease it in the near future.
If you are consistently seeing that it is taking in excess of an hour
for your updates to show up, please contact Adobe ClientCare and open a
...
Tim,DTM doesn't do anything that would reset/re-initialize contextData,
and Appmeasurement still supports it as far as I know.This is a
situation where it would be helpful for us to get some additional
information so we can investigate further and see what might be going
on. Can you please e-mail Adobe ClientCare (clientcare@adobe.com) with
as much detail as possible, including the URL(s) where you are testing,
the company/property/rule(s) involved, etc?Best,Shawn
Marco,Is 's2' the name of the object being used in your on-page
implementation? If not, then this won't work.When you check the "Adobe
Analytics page code is already present" checkbox, DTM will not a) load
s_code (which means it won't create any new s objects), or b) call s.t()
for the page view. Thus, if you've specified 's2' as the object name,
but your current on-page implementation uses 's' (or some other object
name), then DTM is trying to call s2.tl() which refers to an invalid
object, and...
Frank,I don't know for sure which property/rule you are working with,
but I think I was able to find it. It looks like you aren't setting
anything for Analytics aside from the lines in the Custom Code. I'm not
sure if it's still present, but there used to be an odd quirk with
Custom Code that required you to set at least one variable through the
UI as well, otherwise it wouldn't send any of that data through.I would
try setting Page URL to "%document.location.pathname%" (without the
quotes) just...
We are looking at some ways of making this a built-in feature in the
engine. There are a few things that make this tricky to implement in a
way that works for everyone.However, in the meantime, you can create a
function similar to the following:function getAnalyticsAccount() {
for(var toolid in _satellite.tools) {
if(_satellite.tools[toolid].settings.engine == "sc") { return
_satellite.tools[toolid].settings.account; } } }And then in your s_code
you can use it like this:var s_account = getAnalyt...
You would simply use 'this' in custom code to reference the object that
was targeted by the rule. So, for example, if you wanted to get the
title attribute of the link referenced in your example above, you could
use custom code like:var linkTitle = this.getAttribute("title");Hope
this helps!-Shawn
Ryan,All of the rules run in-browser, so yes, it would return the code
client-side. However, I would ask you to reconsider the idea that it
would be bad for performance. If you use our default option of
non-sequential HTML/Javascript to inject the tag, then it will run in
parallel with the rest of the page and will not cause any slowdown
whatsoever in the page load or user experience.Regarding cookies, since
the code is running on your website, the cookie will be set on your
domain when the rule...
Craig,It's possible to do this using the CSS selector syntax in an
event-based rule. Set the event type to "element exists", and then use a
selector like this:div.hiddendiv[style*='display:block']What this
example does is looks for a div with a class of 'hiddendiv', and makes
sure that the style includes "display:block". You may have to tweak this
approach depending on how your site developers are hiding/showing the
elements, but something similar to this should accomplish what you
need.Hope thi...
Stew,Unfortunately IP address is not exposed directly in the browser via
HTML/Javascript for security reasons. The only way that DTM could use IP
address is if your site actually set the user's IP address in a
Javascript variable on every page, or if you used an AJAX call to an
outside server to get this information. The latter of these is not the
preferred option given that it adds additional latency to the processing
of your DTM rules (because it has to wait for the remote server to
respond), ...
Lukas,As this sounds like a potential bug, I would reach out to Adobe
ClientCare via phone or live chat. They'll be able to get the details of
which site you're trying to work with, and help you find a workable
solution.Best,Shawn
All Analytics tools will fire on every page regardless, at least for a
basic page view call, even if you haven't configured any rules. (Just
the same as it would if you did a base Analytics implementation without
TMS and didn't set any page-level variables but only had the s.t()
call.)If you want to suppress a particular tool from loading on certain
pages, you would want to use the Customize Page Code option in the
respective tool settings. In there, you would write some conditions in
Javascript...
David,Did you have the script set to Javascript instead of HTML? If so,
that might be why: the code you pasted above includes HTML elements so
it would cause the Javascript parser to throw up an error.That said,
simply pasting your old code into DTM may work, but it's not the best
way to make use of DTM's capabilities. Ideally you would be identifying
groups of pages or scenarios where a set of variables (like the ones
above) would be set, create a rule for that page group/scenario, and
then use...
Jens,The main reason we haven't put a lot of documentation around the
data layer is because we don't require any specific standard or format.
Anything that's in the DOM (HTML, CSS, or Javascript) can be referenced
in DTM and used to populate data elements.For example, let's say you had
a Javascript object defined on the page that was populated by Adobe
Experience Manager or whatever content management system you happen to
be using:var pageData = { "pageName" : "Creating a data layer in DTM",
"pa...
Michael,DTM's "cookie lifetime" setting affects the s.cookieLifeTime
variable that would otherwise be set in the s_code/AppMeasurement file.
If it is set to "default" in the tool configuration, then we don't pass
a value and rely on whatever the s_code/AppMeasurement defaults to
(which I believe is actually 5 years, or at least it used to be). If
it's set to something other than default, we pass that value to the
s.cookieLifeTime variable. We don't directly control the cookies or
their expiratio...
Data elements are locally scoped, which means that you would need to
prefix this with "window." to access the right object.If you update your
code to the following, it should work:if(window.location.pathname){
return window.location.pathname;}else return '';-Shawn
Garry,Setting s.linkTrackVars or s.linkTrackEvents can be accomplished
via the "Custom Page Code" editor in the Adobe Analytics section of a
rule. Keep in mind that the Custom Page Code editor has its own
Javascript scope, so you need to make sure that the 's' object is
available to your code before trying to access it.Here's how I would do
what you're trying to
do:[img]Dynamic_Tag_Management__by_Adobe.png[/img]Hope this
helps!Best,Shawn
Garry,To modify s.linkTrackVars or s.linkTrackEvents in DTM, you can do
this via the "Custom Code" editor in the Adobe Analytics section of your
rule. You'll need to keep in mind that the Custom Code editor has its
own scope in Javascript, so you'll need to make sure it has the right
reference to your s object.Here's how I'd do what you're trying to
do:[img]Dynamic_Tag_Management__by_Adobe.png[/img]Hope this
helps!Best,Shawn
Garry,Setting s.linkTrackVars or s.linkTrackEvents can be accomplished
via the "Custom Page Code" editor in the Adobe Analytics section of a
rule. Keep in mind that the Custom Page Code editor has its own
Javascript scope, so you need to make sure that the 's' object is
available to your code before trying to access it.Here's how I would do
what you're trying to
do:[img]Dynamic_Tag_Management__by_Adobe.png[/img]Hope this
helps!Best,Shawn
