This works for "bounce rate", but not if you are looking at bounce rate
for other associated things, like marketing channel or eVars. If the
non-interactive event fires BEFORE the pageview -- which happens to us
about 20% of the time -- the Entry is lost to the page. That causes
Entries to not be counted, and can lead to "bounce rates" (single access
rates) of greater than 100%.In 2019, we still need a non-interactive
event.
I know this issue is a bit old, but I just discovered DataSlayer, a
Chrome Plugin that works in the Chrome Developer Tools console (It shows
up as another option at the top, along with Console and Network...). It
can parse out the pixel parameters for both POST and GET requests, and
also shows cookie and data layer values.
Hi Deep,When you view one of your pages, have you looked at what is
being set in s.linkInternalFilters? You can look at the value in the
console and see if the link's domain is missing. See if it is the same
as what's in your s_code, or if the DTM version is overwriting it.
(That's what was happening to me.)Looking at what it is set fr
s.linkInternalFilters might help figure out where the problem is.
OMG, I have the same problem. SO annoying. I'm using FF46. Checked in
Chrome 50 and it does not exhibit this behavior. The menus disappear
properly when you mouse off.
Does anyone have any advice on the event-based rule using "element
exists"? I cannot get my rule to fire. If I change the event type to
mouseover, it fires no problem -- so the selector is obviously correct.
Thanks, Anna! That is exactly what I ended up doing before anyone
replied. That did the trick.I removed all code for the Link Tracking
Config in the basic s_code I am using, and set them using the settings
instead. Worked like a charm.Perhaps I'll do a bit of testing to see
what happens if I have conflicting info in the settings versus the
s_code. But considering the s_code settings were not doing anything, I'm
not sure there will be a conflict for me.
I am very new to DTM and am working on implementing Adobe Analytics in
our staging environment. I am using just the base s_code, and am
building things up a little at a time. I have some basic evars and props
working fine, but I am currently having a problem where all internal
links are being detected as external (everything is lnk_e), even though
the subdomain is identical from link to link.I have "Track Outbound
Links" checked in the Link Tracking tab, but nothing in the "Always
Track" box. Do...
In DTM, I need to keep Adobe Analytics from firing on a particular page,
but I still need the DTM code on the page. How do you do that? For
individual pageload rules, you can tick "Don't load Google Analytics on
these pages," but that is not an option for Adobe Analytics. Anyone have
an idea of how to do it?
Unlike a number of other tag management systems, DTM only has
"inclusion" conditions unless you jump through hoops and develop custom
conditions or use some funky regex. Creating a "NOT" condition is a bit
problematic. What method have people found as the best way to EXCLUDE
specific pages for certain rules. I have code I need to fire on every
page but 1. (And if I start getting into excluding from 2 or 3 pages, it
becomes even more fun!)Why doesn't DTM have a simple "exclude" option
for conditi...
Well, I thought I had already tried this option and it hadn't
worked...but now it is!You need to put the full "if" in there and return
true, not just a simple statement that evaluates as true.Thanks!!
I can't find any documentation about custom conditions ANYWHERE
(typical!), other than the question mark in the setup ("Enter a script
that must evaluate true/false to control whether this rule executes.").
What exactly does the format of this have to be? I have the following
entered:document.getElementsByClassName('errorMessageContainer').length!=0This
evaluates to TRUE, but the rule is not firing. Does this need to include
something else? I've tried various other ways and can't get anything to...
Thanks, @Mike Miller. I did actually set it up easily, creating
individual page load rules for each GA account I needed -- using
domain-based conditions. I didn't need to write any JS to set the
account dynamically.You do have to create separate rules for your
different environments (production and stage), if you have a staging GA
account.
Wow, no answers?Vennouem Vennouem, I ended up turning off the Google
Analytics Tool and creating individual page load rules for each account
-- entering the JS code provided by Google Analytics in the
JavaScript/Third Party Tags area (don't include the and
tags). You have to create a separate rule for each domain/GA
account. The bummer with this is that you will have to create separate
rules for your staging and productions environments for each domain,
creating a subdomain criteria (or something e...
I have created a property that includes multiple domains, because I need
a single set-up for Adobe Analytics. My question is, can I use the
Google Analytics "tool" if I need the different domains to go into
different GA accounts? It seems that you can't tell the tool exactly
which domain to fire on, and it will only use one account.Am I not
seeing something, or is the best workaround for this shortcoming to
create domain-driven page load rules and just loading the code provided
by Google?
I have seen this as well -- when I have Charles Debugging Proxy running.
This is a new error for me, as it has never been a problem in the past.
But when I close Charles, everything works fine.I have been having
significant problems lately in Charles with https and FF. Since the
latest versions of FF, I can't get the SSL proxying to work correctly
and sometimes sites won't even load properly. I am not having any
problems with Charles in Chrome or IE.Do you have a debugger of some
sort running?
Right now, once you add a user, you cannot edit them. You can't even see
what property they are assigned to or what type of permission they have
(unelss they are marked as admin). Right now, you only see who invited
them (not so useful) and can only revoke their permissions and re-create
them as a user.
DTM popup windows should properly size themselves for the screen
resolution or window size of the user. Just include scroll bars or
something! There are several popups when editing things (like the Regex
checker and when editing JavaScript/Third Party Tags in a rule), and the
popup window goes off the bottom of the screen for smaller screens --
meaning you can't reach the save button. You should not have to hook
your laptop up to a larger screen just to save your work.
