For a particular server call we are manually constructing the image
request string. Have a couple questions on the query parameters."t" -
this is supposed to be a UNIX or ISO-8601 format timestamp. The calls I
normally see have a format of "31/4/2017 7:34:30 3 240". Can I use a
format of "2017-05-31T11:54:32.090Z" instead? That is the result when I
use the toISOString() JavaScript function, which is nice and simple."g"
- is this required? I haven't included it in my testing, and the data is
show...
One of the biggest concerns IT departments have in regards to DTM is the
option to include custom JavaScript. This is a very valid concern as one
line of bad code could potentially break the entire page, or
inadvertantly interfere with important functions. Right now anybody with
User access can include custom code with any rule, and as soon as that
rule is saved it immediately goes "live" on the staging site. To
minimize this it would be great if only designated users had access to
the Custom Co...
You can also try the free DTM plugin developed by Adam Haining. It opens
up a separate window with a full easy to read list of all of the rules,
data elements, and _satellite.notify() comments. It gives you a complete
list of all of the Properties Data Elements, the value for each if one
is set, as well as its Type. Very handy tool! This plugin is MUCH easier
to use and read than the Adobe DTM Switch plugin which utilizes the
Console.Plugin How to PageTo use it create a browser shortcut and chan...
DTM fires the s.t() call by default when you use the Analytics tool. So
check to make sure you are not still firing the s.t() call separately
within the page code. There are definitely use cases where you would
suppress that default s.t() call within the Analytics Tool, such as for
an Angular application; but for most cases it's easiest and best to rely
on that call instead of a "hard coded" s.t() call.
The second server call you show looks to be a Download link, indicating
Analytics thinks you are downloading a certain type of file. If this is
the case, try going into the Analytics Tool>Link Tracking section and
either un-checking "Track download links", or if you do have download
links you want tracked then find which file extension is triggering the
call and remove it from the list.
I was guessing that your page may be using some form of Ajax to return
the Search results, as that is fairly common. If so then you may be able
to use $( document ).ajaxComplete(function(){}) to watch for that. I
don't know if there is a specific code to watch for a datalayer value to
change; as an alternative you could put in some code using setInterval()
to check that value every X seconds/milliseconds after the "search"
button is clicked, and if it changes then fire the Direct Call rule and
t...
In some similar scenarios, which in our case used Ajax to make the
search updates, I've used DTM to include some jQuery to watch for the
Ajax Success/Complete event. When that happens and the correct criteria
is met it fires a direct call rule. Ideally you would have the
developers include that direct call in the regular search code, but as
that is not always feasible this works as a viable alternative for me.
Assuming the DTM reference in the section isn't pointing to the
staging rules, if you have the DTM Switch plugin installed make sure it
is not set to Staging. I frequently forget to turn that off after
previous testing.
Sometimes links activate so fast that the DTM rule never gets to finish,
or other code firing on that link interferes with or cuts off the DTM
code. One way I've used to identify that DTM is at least recognizing the
click, but not being allowed to finish is to put a message in the
Conditions section of the Rule. After all of the other conditons I'll
add a custom code condition like the following:_satellite.notify("DTM
Rule was triggered",1); return true;If you see that message in the
Console you...
You can place plugins specific to the s object (such as s.p_fo()) inside
the Analytics Tool>Customize Page Editor. You can then assign them to an
prop or evar within the same place. If you are also setting any of these
prop/evars within the UI Settings, you can select which option should
take precedence with the radio buttons next to "Execute" within that
section.
Another common reason I run into all the time is the link is set to
trigger other javascript, which may cut off the DTM code. There are a
couple of ways around that, but involve custom code. When I run into the
case where other javascript is stopping the DTM Event code from running,
I normally see the events Condition statement running (and passing) but
then the other javascript interferes before the Analytics/Custom Code
section of the rule can run. An easy way to see if this is what's
happenin...
Also important to know if you are using s_code (JavaScript H.*) or
appMeasurement. If you are using s_code or appMeasurement 1.3 or less,
then you will need to pass the new eVars above 75 as a Context Variable,
then use a Processing Rule to populate the eVar itself. Fortunately
passing Events101+ works the same as always.
Another common issue I've seen where AppMeasurement library loads
multiple times on a page is the presence of iFrames, where the iFrame
contains another separate page. The page within that iFrame has
appMeasurement and/or DTM loading also, so you end up with two instances
on the same overall page.
We have an internal site we are tracking, which is a single page which
uses Angular.js framework to change views and content. I've set up some
code within Angular to fire the s.t() call every time a "page" displays.
The s.t() call works as expected for each 'page' rendered by the Angular
code. What I'm running into though is on the initial load of the URL, we
are getting two s.t() calls: 1 - A 'generic' call which has no pageName
specific data, since that is set within the Angular display code. ...
Using console.log() for testing can be a more efficient method, since
you don't have to worry about any the code being interrupted while the
browser waits on the alert popup.
We are in the process of developing a Google Glass app for internal
employees, and I've been asked about tracking with Adobe Analytics. Has
anyone had success, or even tried, doing this?
