Hi, I'd like to clarify expected use cases, how we should work with VPageView tracker object for transition between 2 virtual pages:
according to the example down here, the use case could be:
instantiate object:
var tracker = ADRUM.events.VPageView({url:"some url"});
start tracking (marks the starting time) .. latest version of code calls this from the constructor, so this might be optional?
tracker.start();
do the transition, page content loading etc .. use mark* setters for different phases if we need more granularity
end the tracking by
tracker.end();
send the result into AD:
ADRUM.report(tracker);
do I have to finish the whole scenario? for example what happens, if I call only start() and then send it to AD? and then later create new tracker (for the same url), call end() on it and send it again? which setters on the tracker object are 'necessary'? do I have to pass URL in the constructor (as it's in the example), or not (as it's in the middle of the page)? are the Error tracker objects also 'xhr correlated'? if so, where is this relation stored? for example if user is working in multiple tabs .. thanks for clarifying this, I haven't seen the answers in the documentation .. J.
... View more
