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
At present in order to index "visible text in response" captured by DOM Capture or DOM Diffs, you need to use the VDOMHit pipeline agent. However, this causes an inaccuracy in the replay, as these are shown in replay as their own hits. So if we have a single DOM capture and 10 DOM Diffs in a single UIC transmission, it breaks these all into their own hit numbers in Replay.
As such, we would ask for an enhancement to the Indexing agent so that it can natively detect DOM hits and index their visible text on the page. We badly need this.
How will this idea be used?
Use of the VDomHit pipeline agent causes a lot of concern with our technical developers as they take Tealeaf replay as the absolute truth, and they assume our Tealeaf UIC is spamming the website with a massive amount of data calls (reducing performance of the site). Also, this clutters up the replay, as these cannot be removed from visibility - and is still a "hack" to get the Indexer to read the UIC RequestBody data.
Due to the above, we cannot use the VDOMHit agent as it creates inaccuracies in the replay. However we NEED to be able to search the visible text in the page of DOM and Diff captures - no other tool other than Tealeaf can do this!
|What is your industry?||Banking|
|What is the idea priority?||Urgent|
|Link to original RFE|