Fully supported Adobe Analytics features/components
| Adobe Analytics Feature | Notes on CJA support |
|---|---|
| Anomaly detection | Full support |
| Asset transfer | Full support |
| Attribution IQ | Full support |
| Bot detection | 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. |
| Migrating projects, filters, and calculated metrics from Adobe Analytics to Customer Journey Analytics | Full support. |
| Mobile scorecard/Dashboards | Full support |
| Panels | Full support for the following panels: Blank panel, Attribution, Freeform, Quick insights, and Next or previous item. |
| PDF export | Full Support |
| Project curation | Full Support |
| Project linking | Full Support |
| Product templates | Includes Pre-built templates and Company templates. |
| 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. |
| Streaming Media Collection | Streaming 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. |
| Summary-level data sources | Full support |
| Virtual report suites | Full Support. Now called Data views. |
| Virtual report suite component curation | Full Support. Now part of Data views. |
| Device, Browser, Referrer, Technology dimensions | Supported for both Analytics source connector-based datasets and for datasets generated by the WebSDK. 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. For adding device and browser lookups to your Web SDK datastream, refer to this documentation |
Supported in a new way
| Feature | Notes |
|---|---|
| Advertising Cloud | You can collect historical data for AMO IDs and EF IDs for use in Customer Journey Analytics. |
| Alerts |
The process of using alerts in Customer Journey Analytics is nearly identical to using alerts in Adobe Analytics. However, due to the timing of data collection in Customer Journey Analytics, hourly alerts are not available. In Customer Journey Analytics, alerts can be configured for daily, weekly, or monthly. |
| Analytics for Target (A4T) | The integration between Adobe Customer Journey Analytics and Target provides powerful analysis and timesaving tools for your optimization program. |
| 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. |
| 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. |
| Data Warehouse reporting | Customer Journey Analytics Full Table Export is the evolution of Data Warehouse reports in Adobe Analytics, with many new, often-requested features that are not available in Data Warehouse today. |
| 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 | Full support |
| Graph-based stitching | Through Graph-based Stitching, you can harness the power of the identity graph in Adobe Experience Platform Identity Service to elevate datasets to their preferred identity. |
| Alerts | The process of using alerts in Customer Journey Analytics is nearly identical to using alerts in Adobe Analytics. However, there are important differences. |
| 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. |
| Merchandising variable persistence | Full Support via binding dimensions and binding metrics |
| 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 as well as derived fields 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 Workspace visualizations are supported except for the Map visualization. |
| Cross-device/cross-channel stitching | Supported for event datasets containing identity information. See Stitching. |