Hi @Lee_Lemen ,
Can you please expand the use case you are trying to ?
The versatility of CJA is very well coupled with its ability for cross channel data analysis.
As an example, you got a web dataset, mobile dataset, CRM dataset, call center dataset. If you import all these datasets to a single connection and a data view, then you do cross channel analysis like of how many people started a journey in mobile and then came to web and then have to call the support to make a purchase.
So, dataview is not the capability that should be coupled with a connection, but it should be connected to some thing else. A Data View is similar to the concept of Virtual Report Suites in Adobe Analytics, where you define context-aware visit definitions, filtering and also, how the components are called. You’ll need a minimum of one Data View per Connection. However, for some use-cases, it’s great to have multiple Data Views for the same connection, with the goal of giving different insights to different teams. If you want your company to become data-driven, you should adapt how data is viewed in each team. Some examples:
UX metrics only for the UX Design team
Use the same names for KPIs and Metrics for Google Analytics as for Customer Journey Analytics so that the digital analytics team can speak 1 language only.
Data View filtered to show for instance data for one market only, or one brand, or only for Mobile Devices.
