Watson Marketing Ideas

Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Tealeaf, Universal Behavior Exchange, Watson Customer Experience Analytics, Watson Marketing Insights, Watson Content Hub, 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 IBM experts on the Watson Marketing and Commerce Community

Submit ideas for other Watson Customer Engagement Products:

•  Watson Campaign Automation
Watson Commerce
Watson Supply Chain

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit TEALEAF-I-265 Replay: UI Changes To Timeline|Replay|Raw Data.

Improve Connection between Replay / Raw Data / Timeline for Replay Merged

Currently, there is no connection between the three tabs for replay.  You practically have to remember or copy the url and hunt for it in order to move between the three views.  We need a way to connect the visual page and components with what is in raw data and the events in timeline.  The replay flow in On-Prem was great! There was one set of numbers with the UI listed. The viewable pages were there and you could toggle to Request or Response.  The events were listed below. It avoided the need to bounce between three separate views.

For TL SaaS, the numbering scheme on all three tabs do not match up with the others.  It makes it difficult to identify where one is at from one tab to the next.  We need a way where we can relate all three tabs so that we can see the replay with it's different components and toggle or somehow match up with the Req/Rsp/Json section of raw data and be able to see what events fired on what page.

Relating these three sections together would dramatically reduce the time spent triaging a customer session.

At the least, we need to be able to match up the replay pages on the replay tab with that same page in Raw Data.  We need to be able to quickly identify what api's etc go with the respective front end page.

Right now, there is a lot of copying and pasting and searching to find out where you're at.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 9 2018
  • Delivered
How will this idea be used?

We spend a lot of time figuring out where we're at in replay and where that is at in Raw Data.  We spend as much or more time navigating between the three tabs as we do actually analyzing the data.  It shouldn't be that difficult to figure out where you're at in a session and how raw data and replay and events are related together.  This idea would be used to spend more time on analysis and less time on figuring out what number on each tab matches up.

What is your industry? Telecommunications
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Admin
    Whit Blodgett commented
    November 05, 2018 16:52

    Thank you for your submission, with the coming November release you will see that when toggling between tabs in replay, you will see the corresponding section that you were looking at. This is phase 1 of 2, further enhancement to come in our December release. Thanks!