There is an inconsistency in the numbering of data presented to the user.
* During the replay, numbers represent ScreenViews in a session.
* In Event Tester and in the RAW data view (esp. with Akamai Connector enabled) - numbers represent network level hits.
* In the Session Timeline there are no numbers at all.
There is no way for a user to link the above numbers (e.g finding out in the event tester that an event is firing on Hit number 28, does not let the user investigate the relevant screen view).
My suggestion is that in all above places, we'll be presenting BOTH - the Hit number AND the number of the last registered Screen View - so the user will be able to easily correlate on/after which ScreenView a particular hit was captured.
What is your industry? | Non-Industry Specific |
What is the idea priority? | Medium |
The attached spreadsheet shows how complex the numbering scheme is. There has to be a better way.
I have had similar problems with the lack of coordination in numbering. The worst of this happens when trying to provide training for the customer. Very difficult and frustrating.