UEM: Several purepaths are not linked with a visit (DT 6.1)
As a result the visitor tagging is not working properly as well.
When I start from a visit and drill-down to the purepaths, I have got five purepaths.
However, when I search directly from the purepaths on the exact same timeframe and client-ip. I find the same purepaths and more. (In the picture below, you can see that the 3 purepaths at the top are not linked with the visit.)
This is not only a problem for this application, but for a lot (if not all) our applications with different front-end technologies.
Sometimes we only have 7 purepaths in the visit, while there are 40 in total. As a consequence some user tagging doesn't work since the measure which captures the username is evaluted to purepaths which are not connected to the visit.
We already checked the dynatrace cookie on the web-server (IIS) and X-dynaTrace request headers. They are available on all the purepaths including the ones which are not linked.
I hope there is an easy solution for this problem.
Hi Andi,
I can comment on that one.
They are using a home-grown javascript framework. At the moment only Basic XHR Detection is turned on.
The customer is willing to use the javascript ADK to some extent. Would that solve these issues?
Thanks.
KR,
Kristof
Yes using the ADK to define actions is a possible solution to solve this problem.
Hi
There might be different reasons why you dont get a User Action
a) We do not support all of your JavaScript libraries that trigger these User Actions out-of-the-box: which frameworks do you use? can you provide a list?
b) You have not enabled support for all JS libraries you use on your page in the UEM Settings in the System Profile. There is a section where you can check individual JS Libraries such as jQuery, AngularJS, ... -> please check if there is nothing missing
c) If your app is doing a lot of deplyed async activity that cannot be linked with a real User Interaction, e.g: a background polling - then we cant assign it to a User Action if it happens much later than the last User Interaction. There is one option in the UEM Settings in the System Profile that can help in some of these cases. It is called "Timed Action Support". It will also try to link PurePaths that were triggered after your JAvaScript handlers finished to the recorded User Action
If that all doesnt get you what you intend to see I suggest you open a support ticket to verify why our JS Agent doesnt capture all your User Actions and why not all PurePaths are correctly linked
Andi
