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.
Submit ideas for other Watson Customer Engagement Products:
• Watson Campaign Automation
• Watson Commerce
• Watson Supply Chain
Challenge: Internal customers are sometimes mislead that a session may contain more hits than the actual session contained as Tealeaf Replay from search auto-merges sessions within a time period. Our website gets a lot of visits in a day per user, so auto-merge can be confusing. Also, Tealeaf does this without being asked (adding more data than what was requested).
Idea: Have session-merge be a FEATURE (you choose to use it), rather than automatic and un-disclosed (there is no notice that a merge has taken place). Something in the top of the session that says "Merge?" The info-hover ? would say this is to merge other sessions from that device/browser (visitor ID) across the day. When the session IS merged, have a bright indicator saying the session is MERGED status.
Results are the session would NOT be automatically merged, unless a user explicitly asks for it.
How will this idea be used?
This will reduce confusion of the replay. Right now there is a inconsistence admins have to train/explain:
1. If I do a replay from Session Search, then I get a MERGED session.
2. However, if from that session I create a "Link to Session Replay", then if a hand-off person replays that link, referencing "Hit #XX" that hit number on the linked session may be off as the Link Replay is NOT MERGED. Linked sessions are not automatically merged.
|What is your industry?||Banking|
|What is the idea priority?||Low|
|Link to original RFE|