Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Experience Analytics, Exchange, Watson Marketing Insights, Content, Web Content Manager and WebSphere Portal solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.
Connect with your peers and Acoustic experts on the Watson Marketing and Commerce Community
Submit ideas for other Acoustic Products:
• Watson Commerce
• Watson Supply Chain
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.
How will this idea be used?
A user is testing an event in the event tester.
As a result, they learn that the event was fired on hit 28. Along with that, they will also be informed that the last screen view which was registered in the session before that hit was ScreenView number 5.
Going to replay, the user will be able to jump to screen view 5 and review the moment when the event occurred.
A user is reviewing data in the RAW view.
Is identifying a network hit with a failed background AJAX call - as hit 14, fired on the 2nd screen view.
Can now switch to the Replay interface and jump directly to the 2nd screen view to review the impact of the failed AJAX call on the user experience.
|What is your industry?||Non-Industry Specific|
|What is the idea priority?||Medium|
|Link to original RFE|