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

Capture DOM both when events occur AND just after

At present, an event captures the DOM either at the time the event occurs, or a delay can be added to capture it after the event occurred, but in some cases we really would like both. Sometimes things change on the page without any clicks or form changes, so it is only when the 'Click' event on an element that has appeared since the last DOM capture that replay will show it, but if the click changes something on the page we would have to wait for another event with DOM Capture to see what the result was, or try to delay the click. Ideally, we would want to see what was clicked and what the result of the click was. This also goes for form changes - if I enter a value and it fails validation, displaying an error message, in Replay I typically have to go to the next replayable event to see the error message being displayed. With DOM Diff, if there are no changes to capture then there shouldn't be any extra message, but if there are changes, capture them and send so that Replay can show the page as it was when the event occurred and then as a next step what it looked like after the event.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Feb 13 2019
  • Under Consideration
How will this idea be used?

This will make the replays easier to understand about what is happening in the page with regards to the user interactions. It will also benefit many sellers who demo Tealeaf, as it will be easier it is for potential customers to understand what is happening in the demo they are seeing.

What is your industry? Computer Services
What is the idea priority? Medium
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    PRESTON HARRIS commented
    16 Feb 18:46

    Thanks for the submission.  This ties into a new feature we are developing to deal with lazy loading and dynamic updates to the DOM.  With this new feature, you should be able to configure a click as a capture point, then configure another event (with screen view filter) that monitors the DOM for a CSS change.  If a change is detected, another capture point will trigger.  This ability would work well with LOAD + Lazy Load, CLICK + (whatever), CHANGE + (whatever).  I will review your use case with the dev team to see if what we are developing will cover what you are looking for.