domComplete attribute - corresponding measure UEM

Hi - I forwarded this to the doc team to make sure this is all documented.

Here is a first response from the team - I hope this gives you a start:

Document Load Time (or also named DOM Load Time in the create measure dialog) is the representation of the "DOM Ready" or "DOM Interactive" event. Depending on the browser version this is based on the DOM Ready Event or if this event is not available, we calculate for old browsers with tricks like "scrolling is available". DOM Load Time is nearly equivalent with the W3C Navigation Timing: Document Interactive. But Document Interactive is only available for the newest browser versions supporting the W3C Navigation Timings. The W3C Document Interactive is the better and more accurate measure representing that the DOM is fully loaded and processed. 

Load Time or also named Total Time is the complete action response time. It's by default named Load Time because most web admins and app owners thinks in Page Loads but of course this Total Time represents also the complete duration of an ajax action

Still confused. See the data I captured from home page. Dom Load and Document Interactive does n't seem to match. I would have preferred a 

domComplete under the W3C Navigation timings Landmark....

I used a BT for the above...

Hi Jibi,

you are right - we do not provide a measure for domComplete. What are you trying to measure? We found that the User Action Response time is usually the measure that has an immediate impact on the user experience. The response time is calculated differently for Page Loads and AJAX Actions. Here is a summary what it does:

User Experience Management#UserActions

Best regards,

Dominik

Dominik,

The requirement was for me to gather historical data for browsers. We have some synthetic monitoring for IE9 and that uses document complete among others.

Any specific reason of not provising domComplete even though you have that data from the w3c apis?

Klaus, Dominik - Can you please review the BT below? Basically I want to plot response times by IE11, IE10 etc

Below BT was how I originally started with and which you don't recommend.

The second one would have given me more clarity if there was an issue on a type of page say home page or product page. 

Please help. I would like to move forward with this today.

Also (for the below) why is that some of the BTs have a filter called 'Page Action Request'. Need to know what exactly is the difference between 'Real User Actions' and 'Real User Page Actions'. 

My 'User Action response time' BT also has the 'Page Action Request'. May be this is needed and I can just have the BT which filters and shows the homepage etc.

Klaus and Dominik are travelling in the moment - thats why I dont know how fast you can expect a response from them.

As for Page Action vs. User Action. This is just a historcial leftover. What we call User Action now used to be called Page Actions. So - it is the same but we still  have some "leftovers" in some of our measure names

I will use Real User Page Action as my template. Both of them use a filter called 'No Artifical Request'. But you edit details, and you will see that there are some changes.