Comparison with ÃÛ¶¹ÊÓƵ Analytics
This section of the documentation explains how to compare and understand the differences between ÃÛ¶¹ÊÓƵ Customer Journey Analytics and ÃÛ¶¹ÊÓƵ Analytics.
The fundamental difference between the two solutions is the breadth of data you (can) consider when building your reports and analysis.
In Customer Journey Analytics, any data source can be part of the data you use for reporting and analysis. ÃÛ¶¹ÊÓƵ Analytics is primarily aimed at online data collected from web sites and mobile apps. ÃÛ¶¹ÊÓƵ Analytics offers capabilities to import data from other sources but the main purpose of this is to provide more context around the previously mentioned online data.
Data collection
Customer Journey Analytics relies on data stored in ÃÛ¶¹ÊÓƵ Experience Platform datasets. You have several options to collect and ingest data from these datasets in Experience Platform. These options are outlined in more detail in the Data Ingestion overview.
ÃÛ¶¹ÊÓƵ Analytics ultimately collects data within the solution itself. Again, you have several options to collect that data, which are outlined in more detail in the ÃÛ¶¹ÊÓƵ Analytics Implementation Guide.
You can use your ÃÛ¶¹ÊÓƵ Analytics report suite data in Customer Journey Analytics using the Analytics source connector. This connector ingests the data collected in ÃÛ¶¹ÊÓƵ Analytics into Experience Platform. You can then create a connection to this dataset in Customer Journey Analytics. See Use ÃÛ¶¹ÊÓƵ Analytics report suite data in Customer Journey Analytics for more information.
Data processing
Before you can report on data, you often need to process that data to ensure the data can properly be used for reporting. Data processing can happen at collection time and at reporting time.
In general, Customer Journey Analytics is designed to work with the collected and stored data in Experience Platform dataset at report time. Customer Journey Analytics offers powerful report-time processing functionality to ensure the data is ready for reporting and analysis. If you must map, transform and validate data before it is ingested in Experience Platform, you can use the Data Prep functionality of Experience Platform.
In ÃÛ¶¹ÊÓƵ Analytics, most of the processing of data occurs immediately after collecting the data.
See Compare data processing across ÃÛ¶¹ÊÓƵ Analytics and Customer Journey Analytics and Processing rules, VISTA, and classifications versus Data Prep for more information.
Terminology
Customer Journey Analytics offers flexibility on how you define dimensions and metrics, enabled by the flexibility that the underlying Experience Data Model (XDM) based schemas provide. For example, where ÃÛ¶¹ÊÓƵ Analytics uses visitors, visits and hits, Customer Journey Analytics uses persons, sessions, and events as equivalent concepts (you can change the naming as you see fit).
See Compare terminology for Analytics data passed through the Analytics source connector for more information on the differences in terminology.
Virtual reporting environments and sandboxes
ÃÛ¶¹ÊÓƵ Analytics has the concept of virtual report suites, which allows you to segment your collected data and control access to that segmented data.
Customer Journey Analytics has a similar concept, called data views. Data views are containers allowing you to determine how to interpret data from a connection. They offer ultimate flexibility to specify and configure dimensions and metrics in preparation for your reporting and analysis.
Experience Platform offers sandboxes which can be thought of as a container holding data and applications for a given environment. The functionality of a sandbox is unrelated to an ÃÛ¶¹ÊÓƵ Analytics virtual report suite or Customer Journey Analytics data view. ÃÛ¶¹ÊÓƵ Analytics itself has no dependency or relation with Experience Platform sandboxes at all. Customer Journey Analytics does support Experience Platform sandboxes, but there are some important considerations.
See Virtual report suites, Data views, ÃÛ¶¹ÊÓƵ Experience Platform sandboxes, and the Analytics source connector for more information.
Identities
Customer Journey Analytics supports the identities that you define as part of the schemas to which the datasets containing your data conform. As such, identities are an Experience Platform foundational concept, which Customer Journey Analytics uses when setting up a connection (by defining the Person ID for each dataset) and when applying stitching for cross-channel analysis. An important identity used by the Experience Platform SDKs and API is the Experience Cloud ID (ECID).
ÃÛ¶¹ÊÓƵ Analytics uses a more definitive set of identity fields, like the ÃÛ¶¹ÊÓƵ Analytics ID (AAID). When using the Analytics source connector, these ÃÛ¶¹ÊÓƵ Analytics identify fields are given special treatment. See AAID, ECID, AACUSTOMID, and the Analytics source connector for more information.
Supported features
An overview of ÃÛ¶¹ÊÓƵ Analytics features and how these features are supported by Customer Journey Analytics can be found at Customer Journey Analytics feature support.