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
When a struggle is found, an analyst can typically create search criteria for finding all session where that struggle (or any other behavior) occurred. Howeverm then it is typically very difficult to manually find any common factors identifying those sessions among all sessions, hence root-cause analysis and finding the cure for the problem may be a lenghty process.
There shall be a function available when search results are presented - for analyzing the result set and automatically finding any common denominators among all events, dimensions, session attributes, and other available data (excluding search criteria), and assessing if they are allowing the analyst to uniquely identify those sessions (within the same time frame) - e.g.
For the search criteria:
95% of selected sessions have the following characteristics:
- browser (session attribute): chrome
- browser version (session attribute): 65
- device type (dimension): tablet
- language (dimension): es_MX
- product (event) : car insurance
That represents 15% of all session in the timeframe (number of sessions in the search results to all session in the same timeframe)
Among remaining sessions, 3.5% had the same characteristic (percentage of sessions that had the same characteristics but were NOT part of the analyzed resultset).
How will this idea be used?
It will speed up any kind of root-cause analysis helping to find common factors among session and allowing the analyst/support to focus their investigation on common factors - very hard to be found manually without inspecting every affected session.
|What is your industry?||Non-Industry Specific|
|What is the idea priority?||Medium|
|Link to original RFE|