The following tables list which features in Adobe Analytics are supported, partially supported or not supported in Customer Journey Analytics, and which features of Customer Journey Analytics are not supported or available in Adobe Analytics. These lists will change over time as features are added to Customer Journey Analytics.
|Adobe Analytics Feature||Notes on support|
|Anomaly detection||Full Support|
|Attribution IQ||Full Support|
|Calculated metrics||Full Support. Any existing calculated metric in the traditional Analysis Workspace is not ported to Customer Journey Analytics.|
|Calendar events||Full Support. Calendar events have been implemented as Annotations in Workspace.|
|CSV download||Full Support|
|Custom calendars||Full Support|
|Date comparisons||Full Support|
|Date ranges||All date range functionality is supported.|
|Dimensions||Full Support. Customer Journey Analytics uses XDM and supports unlimited dimensions. Customer Journey Analytics is not tied to the custom eVars or props of traditional Adobe Analytics.|
|GDPR deletion||Full Support; note that GDPR is now handled in coordination with Adobe Experience Platform. Customer Journey Analytics inherits whatever data changes Experience Platform makes to underlying datasets.|
|Lift and confidence reporting||Full Support via Experimentation panel|
|List variables/List props||Full Support. Customer Journey Analytics uses XDM and supports unlimited string arrays which can be used similarly to listVars.|
|Merchandising eVars||Full Support via binding dimensions and binding metrics|
|Metrics||Full Support; Customer Journey Analytics uses the Experience Data Model (XDM) and supports unlimited metrics and is not tied to the custom success events of Adobe Analytics. Some standard metrics have been renamed from Adobe Analytics: Visitors = People, Visits = Sessions, Hits = Events.|
|Mobile scorecard/Dashboards||Full Support|
|Panels||Blank Panel, Attribution Panel, Freeform Panel, and Quick Insights are fully supported.|
|PDF export||Full Support|
|Project curation||Full Support|
|Project linking||Full Support|
|Report time processing||Full Support; Customer Journey Analytics relies exclusively on Report Time Processing.|
|Reporting API access||Full Support; Available through the Customer Journey Analytics API.|
|Scheduled reports/projects||Full Support|
|Segments||Full Support. Now called “Filters” - note that any existing segments in traditional Analysis Workspace are not ported to Customer Journey Analytics.|
|Virtual report suites||Full Support. Now called Data Views.|
|Virtual report suite component curation||Full Support. Now part of Data Views.|
|Streaming Media Analytics||Media data are available using the Analytics source connector as part of the Media Concurrent Viewers panel and the Media Playback Time Spent panel in Workspace.|
|Audience publishing||Supported if licensed with Adobe’s Customer Data Platform or Journey Optimizer products. Audience Publishing sends audiences to Real-time Customer Profile in Experience Platform.|
|Classifications||Now called “Lookup Datasets”. Classifications used in Analytics can be imported to the Experience Platform and Customer Journey Analytics using the Analytics Classifications Source Connector. Lookup datasets can also be uploaded to Experience Platform directly and made available in Customer Journey Analytics.|
|Classification rule builder||Supported using substrings in Customer Journey Analytics. Uses string manipulations at report time rather than lookup datasets.|
|Custom session length||Session length can be configured through Session settings in a Data view. See Session settings for more information.
Handling of mobile background events is supported through the Adobe Experience Platform Mobile SDK. See Lifecycle for Edge Network for more information.
|Currency conversion||Supported as part of formatting a metric component in a data view.|
|Merchandising variable persistence||Full Support via binding dimensions and binding metrics|
|Customer attributes||Now called “Profile Datasets”, they do not get automatically imported from Experience Cloud, but must be uploaded to Experience Platform before they are available in Customer Journey Analytics.|
|Data feeds||First-generation data export of datasets is available through the Experience Platform Data Access API and through Experience Platform Destinations. These options provide event/row level export of all data collected or ingested into Experience Platform Data Lake. Post process data columns are not available because post columns are computed at query time. Export of post columns is available through reporting.|
|Entries, Exits, and Time spent dimensions and metrics||Supported (Entries and Exits are now called Session Starts and Session Ends) and are calculated in a slightly different way.|
|eVar persistence settings||eVars are no longer part of Customer Journey Analytics. However, persistence settings are now part of Data Views and are available for all dimensions. Keep in mind that persistence is based on report time processing, not data collection processing. Dimensions set within Data Views are limited to a 90-day max persistence and do not support unlimited persistence.|
|Geosegmentation dimensions||All GeoSegmentation/geography collected into Adobe Analytics flows into Customer Journey Analytics through the Analytics source connector. Implementations that do not use the Analytics source connector, but rely on the Experience Platform Web SDK for digital data collection, can use the Experience Edge Geo Lookup service.|
|IP obfuscation||For Customer Journey Analytics customers using the Analytics source connector to populate data from Adobe Analytics into Customer Journey Analytics: IP obfuscation settings applied in Adobe Analytics flow through to your Customer Journey Analytics data. You can control these settings in Adobe Analytics as needed.
For Customer Journey Analytics customers using Experience Platform Web SDK to populate data into Platform and Customer Journey Analytics directly. You can use Data Prep for Data Collection in Platform to configure rules that obfuscates the IP address based on your company’s requirements.
|Marketing channels||When using the Analytics source connector, Marketing Channels data flows into Customer Journey Analytics through that connector. Marketing Channel rules are configured in traditional Adobe Analytics and some rules are not supported. See Customer Journey Analytics Marketing Channels for more information.
For WebSDK implementations, report-time marketing channel processing rules are supported through Derived fields.
|Metric deduplication||Now configured on metrics within Data Views. Metric deduplication happens at the person or session level rather than the Dataset, Data View, or Connection level.|
|New vs. repeat session reporting||Formerly accomplished using the Visit Number dimension. New vs. Repeat sessions are supported with a 13-month lookback window.|
|Processing rules, VISTA rules, Marketing channel processing rules||Supported using Adobe Experience Platform Data Prep functionality for both WebSDK based datasets and data from the Analytics source connector.|
|Products variable||Within the Experience Platform, users can use an array of objects within a dataset schema to satisfy this use case. Within Customer Journey Analytics, customers can use any number of product variables and are not restricted to a single variable as in Adobe Analytics.|
|Project sharing||Project sharing is only supported between users of Customer Journey Analytics - there is not project sharing between Customer Journey Analytics and the traditional Analysis Workspace.|
|Report Builder||Supported with a new Office 365 plugin for Excel.|
|User permissions/Data access controls||Customer Journey Analytics distinguishes between Adobe Admin Console product admins, product profile admins, and users. Only product admins can Create/update/delete Connections, Projects, Filters, or Calculated Metrics that were created by other users, while product admins and product profile admins can edit Data Views. Additional user permissions are available for things like creating calculated metrics, filters, or annotations.|
|Visualizations||All visualizations are supported except for the Map visualization.|
|Cross-device/cross-channel stitching||Supported for datasets containing identity information directly (also known as “field-based” stitching). Graph-based stitching is not yet supported, but is planned. See Stitching.|
|Bot filtering||For Analytics source connector-based datasets, bot filtering is applied. General bot filtering logic for other datasets is not performed by the Experience Platform or Customer Journey Analytics.|
|Device, Browser, Referrer, Technology dimensions||Supported for Analytics source connector-based datasets. Refer to documentation on which Analytics variables are supported via ADC.
If you use Experience Platform Web SDK data collection, Device and dimensions based on the Device lookup are not currently supported. Future support is planned.
|Panels||Blank Panel, Attribution Panel, Freeform Panel, and Quick Insights are fully supported. The Segment Comparison and Analytics for Target (A4T) panels are not supported.|
|Processing rules||For Analytics source connector-based datasets, processing rules are still applied. Data prep capabilities in Adobe Experience Platform can also be used as a replacement for processing rules for data that is going directly to the Platform.|
|Analytics for Target (A4T)||Partial support is provided through fields in the Analytics source connector. Support for A4T-friendly names on Target Activities and Experiences is planned.|
|Alerts||Support is planned.|
|Contribution analysis||Support is planned.|
|Data Warehouse reporting||Support is planned from the Analysis Workspace interface. Adobe Experience Platform Query Service also provides an interface for these use cases in Customer Journey Analytics.|
|ID stitching using device graph||Support is planned.|
|Project templates||Support is planned.|
|Real-time reporting||Support is planned.|
|Segment IQ||Support is planned.|
|Transaction ID data sources||Support is planned.|
|Migrating projects, filters, and calculated metrics from Adobe Analytics to Customer Journey Analytics||Support is planned.|
|Summary-level data sources||Support is planned.|
|Activity Map||Support is not yet planned.|
|Advertising Cloud||Support is not yet planned.|
The following table lists features that are available in Customer Journey Analytics, but are not supported in Adobe Analytics.
|Accommodation for any kind of data||Customer Journey Analytics is combined with Experience Platform’s ability to hold all kinds of data schemas and types. Using Experience Data Model (XDM), data can be uniformly represented and organized, ready for combination and exploration. Adobe Analytics is predominantly focused on web and mobile analytics data with some capabilities to import data.|
|Unlimited customer dimensions and metrics||Customer Journey Analytics dimensions are unlimited; values can be numeric, text, objects, lists, or mixtures of all. Dimensions can be nested or hierarchical. Analytics supports up to a maximum of 75 props and 250 eVars.|
|Unlimited unique values||Customer Journey Analytics supports unlimited unique values or dimension items that can be reported on within a single dimension. Adobe Analytics is limited to 500.000 unique values. The unlimited unique values or dimensions removes reporting and analysis limitations currently existing with large-scale Analytics implementation.|
|Report-time transformations||Data views in Customer Journey Analytics allow you to further interpret data from a connection. You can alter or remove data without changing your implementation, use substrings to manipulate dimensions, create metrics from any value, or filter subevents. All of these transformations are done non-destructively. Adobe Analytics provides limited capabilities through virtual report suites and custom session length.|
|Experimentation analysis||Customer Journey Analytics can evaluate the lift and confidence of any experiment from any data source defined as part of a connection. This evaluation allows you to understand cause-and-effect relationships between customer interactions spanning any channel. Analytics is limited to experimentation analysis through A4T.|
|Cross-Device Analytics||Customer Journey Analytics supports the seamless combination of device-specific datasets from unauthenticated and authenticated sessions. Customer Journey Analytics offers to backfill historical data to known devices. In Analytics, this capability is limited to a single report suite and the use of a device graph.|
|SQL access||Using the Data Distiller option, Customer Journey Analytics can remove the limitations of data collected on Adobe’s backend processing. You can modify your data with SQL, create values and datasets unique to your business and continue to explore. Analytics does not support any kind of SQL access to its data.|
|Enhanced security and privacy options - HIPAA readiness||Customer Journey Analytics is HIPAA ready and offers additional security options for regulation compliance. Adobe Analytics is not HIPAA ready.|
|Ability to combine datasets (such as Adobe Analytics report suites)||Customer Journey Analytics allows you to combine data from multiple report suites as if they were a single report suite in Adobe Analytics.|
|Derived Fields||Derived fields allow for report-time transformations to your data. Data can be combined, corrected, or created on the fly and apply retroactively to all reporting.|