Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

FrederikWerner
FrederikWernerNew Participant

Provide contextual access to components in Analysis Workspace on Customer Journey AnalyticsNew

Description - Today, components in CJA are presented as a flat list, like we know it from Core Analytics: While this makes sense in Core Analytics, where components have no inherent relation to each other, components in Customer Journey Analytics come from the XDM Schema, where fields are always contextual to the Schema. For example, the standard Web SDK Field Group positions the ID and Click number of Link Clicks at "Web > Web interaction > Link Clicks > ID/Value": This context for individual components provides CJA with the potential to solve a few long-standing challenges in Analysis Workspace: For similarly named components, provide an intuitive way to explain the context (and thereby use case) of individual components As a novice user, help them to combine the right dimensions and metrics by showing that they come from the same context (in the example above: "combine the value metric with the id dimension") As an advanced user, give hints and inspiration to explore the available context for already used components (in the example above: "I'm using the Interaction Name already, maybe I can also use the Interaction Type or Interaction Region from the same XDM level?") In the UI of the component lists, a more context-rich view could be an alternative to or integrated with the existing flat list in Analysis Workspace. Inspiration could be taken from the Data Views manager, where we can explore the Schema in a contextual way: An alternative would be the tree-like view we know and love from the Schema view in AEP.   This context would be a great addition to the informational overlays and could be very helpful to make CJA more accessible and efficient.

tclevieNew Participant

Enhance Customer Journey Analytics Worspace for Cross Device AnalysisNew

Description - One main selling point of Customer Journey Analytics is the ability to do cross device analysis. However, workspace in CJA has limitations which make cross device analysis difficult and not easy. For example, a simple question such as how many people are viewing a product on a device and purchasing it on a different device is not easy to answer when you have multiple different devices. For example, we have 3 devices: desktop, mobile and app. I have to create a filter that includes every possible cross device scenario which would include: (viewed product on desktop and purchased on mobile, viewed product on desktop and purchased on app, viewed product on mobile and purchased on desktop, viewed product on mobile and purchased on app, viewed product on app and purchased on desktop, viewed product on app and purchased in mobile). That is a rather large filter to answer such a simple question.Why is this feature important to you - The current limitations are very time consuming and makes cross device analysis difficultHow would you like the feature to work - A solution to this would be if CJA workspace allowed for two layer identification, meaning that cross device could identify on the customer ID along with device ID. Another solution would be to update filters so that we can maintain an element across the filter criteria or simply put that I could state in the filter that that purchase of the product happened on a device that does not match the device at the time of product view.