Optimize Customer Journey Analytics and Analysis Workspace performance
Various factors can influence overall Customer Journey Analytics performance as well as the performance of a project within Analysis Workspace. In Workspace, you might get an error message that says
This query is too complex. Please review best practices for building Analysis Workspace queries.
These best practices discuss which factors might lead to this error and how to simplify the report/project.
Query factors query
These are the most common query factors that influence overall Customer Journey Analytics performance:
Additionally, minimize the number of year-over-year comparisons used in the project. When a year-over-year comparison is calculated, it looks across the full 13 months of data between the months of interest. This has the same impact as changing the panel date range to last 13 months.
Factors that add complexity to a filter (in descending order of impact) include:
- Operators of “contains,”, “contains any of”, “matches,” “starts with,” or “ends with”
- Sequential filtering, especially when dimension restrictions (Within/After) are used
- Number of unique dimension items within dimensions used in the filter (e.g., Page = ‘A’ when Page has 10 unique items will be faster than Page = ‘A’ when Page has 100000 unique items)
- Number of different dimensions used (e.g., Page = ‘Home’ and Page = ‘Search results’ will be faster than eVar 1 = ‘red’ and eVar 2 = ‘blue’)
- Many OR operators (instead of AND)
- Nested containers that vary in scope (e.g., “Event” inside of “Session” inside of “Person”)
While some of the complexity factors cannot be prevented, look for opportunities to reduce the complexity of your filters. In general, the more specific you can be with your filter criteria, the better. For example:
- With containers, using a single container at the top of the filter is faster than a series of nested containers.
- With operators, “equals” is faster than “contains”, and “equals any of” is faster than “contains any of”.
- With many criteria, AND operators is faster than a series of OR operators.
Look for opportunities to reduce many OR statements into a single “equals any of” statement.
Factors that add complexity to a visualization include:
- Range of data requested
- Number of filters applied; for instance, filters used as rows of a freeform table
- Use of complex filters
- Static item rows or columns in freeform tables
- Filters applied to rows in freeform tables
- Number of metrics included, especially calculated metrics that use filters
Help > Performance in Analysis Workspace
Various factors can influence the performance of a project within Analysis Workspace. It’s important to know what those contributors are before you start building a project so that you can plan and build the project in the most optimal way. This section includes a list of factors that impact performance and optimizations you can make to ensure peak performance in Analysis Workspace.
Under Analysis Workspace > Help > Performance, you can see factors that impact your project’s performance, including network, browser, and project factors. For the most accurate results, allow the project to fully load before opening the Performance page.
- The Current Project column displays the results for your current project and user environment.
- The Guideline column displays Adobe’s recommended threshold for each factor.
Additionally, you can Download as CSV the performance contents to easily share with Adobe Customer Care or your internal IT teams.
Network factors
Help > Performance network factors include:
Browser factors
Help > Performance browser factors include:
If those actions do not help, discuss hardware details with your IT team.
If those actions do not help, discuss hardware details with your IT team.
Project factors
Help > Performance project factors include:
Request factors
Help > Performance request factors
Use the following diagram and terms to learn how requests are processed and the various factors that influence processing times:
Request processing diagram
Request processing terms
The time required from when the request is initiated to when it is complete. The guideline is 15 seconds.
In the Request processing diagram above, the request time represents the full process, from Analysis Workspace request initiated to Analysis Workspace request complete.
The time required from when the request is initiated to when it is complete.
In the Request processing diagram above, the request time represents the full process, from Analysis Workspace request initiated to Analysis Workspace request complete.
Because Analysis Workspace stores only the hash for any strings that are used in any segments, each time you process a project, Lookups are performed to match the hashes with the appropriate values. The guideline is under 2 seconds.
This can be a resource-intensive process, depending on the number of values that could potentially match the hash.
In the Request processing diagram above, the lookup time is represented in the Lookups phase (at the time of Request Engine processing phase).
The total time waiting in queue before requests are processed. The guideline is 5 seconds.
In the Request processing diagram above, the queue time is represented in the Request Engine queue phase and Server queue phase.
The average amount of time it takes to process the request.
In the Request processing diagram above, the average server processing time is represented in the Server queue phase and Server processing phase. The guideline is 10 seconds
Not all requests require the same amount of time to process. Request complexity can help provide a general idea about the time required to process the request. The guideline is Medium or lower.
Possible values include:
- Low
- Medium
- High
This value is influenced by the values in the following columns:
- Month boundaries
- Columns
- Segments