This help page contains recommended use cases for each Adobe Analytics tool. Tools should be considered in the order they are listed. If a certain tool does not meet the need, move to the next one for consideration.
For more on Adobe Analytics Product Comparisons, go here.
Adobe Analytics Reporting User Interfaces
Analysis Workspace should be the go-to user interface for all of your reporting and analysis needs. Adobe continues to invest in and release monthly updates to this product. If there is a task you cannot do in Analysis Workspace, consider the other interfaces below.**
Reports & Analytics should be used:
- By beginner users who need access to pre-built reporting that is easier to navigate.
- To access real-time data in the UI.
- To set up Calendar events.
- To set up Targets.
- To view Bot reporting.
- To access unique Video visualizations of Video Daypart and Viewer Drop-off.
- To leverage Publishing Lists in scheduled reporting .
Ad Hoc Analysis should be used:
Adobe is moving Ad Hoc Analysis to end of life on March 1, 2021. Learn more
- If tab organization of project work is desired.
- To use the Site Analysis report (3D-pathing report).
Data Workbench should be used:
- As the most flexible Analytics tool option (down to visitor-level, hit-level analysis).
- To create a multi-channel dataset of online and offline interactions from CRM to POS to Web.
- For advanced attribution (rules-based & algorithmic models).
- For predictive, statistical modeling (propensity scoring, clustering, correlations, etc.).
- For Latency analysis (time before / since an event).
- For identification and export of complex segments throughout Adobe Experience Cloud.
Importing Data into Adobe Analytics
Classifications should be used:
Data Sources should be used:
Data Connectors(formerly known as Genesis) should be used:
- When you engage with a 3rd-party provider that has built a supported connection with Adobe Analytics. Data Connectors typically incorporate summary-level data into Adobe Analytics permanently and automatically, on a recurring basis.
Data Insertion API should be used:
- When you need to upload data into Adobe Analytics, and cannot use the Adobe AppMeasurement or mobile SDK code.
Customer Attributes should be used:
- If you capture enterprise customer data in a customer relationship management (CRM) database and want to upload the data to the Experience Cloud.
- If you want to use CRM data for deeper analysis in Analytics, or as targeting criteria in Adobe Target.
Audience Analytics should be used:
- If you want to incorporate Adobe Audience Manager (AAM) audience data such as demographic information (e.g. gender or income level), psychographic information (e.g. interests and hobbies), CRM data, or ad impression data into any Analytics workflow.
- If you want uploaded CRM data to be time based, because this integration sends new information to Analytics hit by hit.
Exporting Data from Adobe Analytics
Report Builder should be used:
- If the customized layout options of Workspace are limiting (anything is possible in Report Builder, within the limits of Excel).
- To loosely tie in user inputs or offline data sources (impressions, cost) to Adobe data. More permanent solution for tying in data is Data Sources (see Importing Data to Analytics).
- To merge data together from different dimensional reports (e.g. promo impressions report joined with promo click-to-conversion report).
- For cross-report-suite views.
- If automation through scheduling is desired (XLSX, XLSM, CSV, PDF, TXT, XML, MHT).
Data Warehouse should be used:
- To access variables otherwise hidden in the UI - IP address, Experience Cloud ID, Analytics Visitor ID, Page URL)
- To access more granular data than the UI (denormalized table view)
- To download data in a format suitable for a Pivot Table input
- If the client wants to input Adobe data into a 3rd-party data visualization tool (slightly summarized, and not hit-level)
- To access all unique dimension items if you are running into “Low Traffic” in Adobe Analytics
Analytics Data Feed should be used:
- To utilize the most granular data feed we can provide (visitor ID, hit).
- If the client wants Adobe data stored in a client-side database, at the most granular level we can send.
- If the client wants to develop a Business Intelligence (BI) tool or input hit-level Adobe data into a 3rd-party tool.
Reporting APIs should be used when the other visualization options do not meet your needs. The 3 API options include:
- Fully Processed: when you want feature-rich data (including visits, visitors, and segments). This is typical Analytics UI summarized data, available within ~30-90 minutes. Can be used through Report Builder.
- Real-Time: when you want to view a few metrics and dimensions with seconds of latency. This is limited, partially processed, summarized data that is available within ~30 seconds. Includes unique algorithms of most popular, gainers, and losers. Can be used through Report Builder.
- Live Stream: when you want a stream of partially-processed hit-level Analytics data within seconds of collection. This is partially processed data, available within ~30 seconds. Available for Analytics Premium only. Requires some way to visualize the data, typically through an Engineering Services engagement.
Engineering Services should be used when:
- The other Adobe tools don’t meet your needs.
- You want a custom experience.
- You want a fully automated solution.
- You want to reach many devices.
- You have multiple data sources.
- You have complex data ETL (Extract-Transform-Load) requirements.
- You want custom branding.
- You want to visualize Analytics Live Stream.