Identify Low-Traffic Values in Adobe Analytics Without Raising a Customer Care Ticket

[#1]

Running into Low-Traffic values often serves as a roadblock for organizations looking to understand their data. While contacting Adobe Customer Care to change the threshold on a per-variable basis can fix this issue, Data Warehouse can also serve as a solution. When a report has many unique values, Adobe provides functionality to ensure that the most critical values appear in your data. After approximately 500,000 existing values are collected, a dimension item labeled Low-Traffic groups unique variable values. Running into Low-Traffic values can often serve as a roadblock for organizations looking to understand their data, as shown in the screenshot below:

While organizations can contact Adobe Customer Care to change the threshold on a per-variable basis, they may only need this data to glean a quick insight and do not want to move forward with this change request. In this scenario, organizations should leverage Data Warehouse to understand Low-Traffic values, as there is no limit to the number of unique values in Data Warehouse reports. However, remember that Low-Traffic values can still appear using Data Warehouse in specific scenarios. Low-Traffic values may still occur for list vars, list props, merchandising eVars, and marketing channel detail dimensions.

Identify Low-Traffic Values in Data Warehouse

1. Navigate to Adobe Analytics > Tools > Data Warehouse.
2. Create a name for the report under "Request Name."
3. Using either the custom or preset date range option, select the date range you used in Workspace to identify the Low-Traffic dimension item. 
4. As the screenshot above includes a segment, you will want to do the same in Data Warehouse if applicable to your use case. Under "Available Segments," search for the segment used in your Freeform table. You can skip this step if you see the Low-Traffic dimension item without including a segment.
5. Navigate to "Breakdowns" on the left side of the screen. This section is where you will select the dimension item to measure. In this case, we will choose Page URL as our dimension, as shown below:

     6. Navigate to "Metrics" below "Breakdowns." This section is where you will select the metric needed to measure the dimension item. In this case, we will choose Page URL instances as our metric, as shown below:

    7. Enter the email address where you'd like to send the report and hit "Request this Report."

Once you receive the Data Warehouse report via email, you can view all Page URLs for the given date range without any Low-Traffic dimension values.

[#2]

Yes, this is a very good point. 

'Low Traffic' is a mechanism in Reporting and Workspaces to improve performance, but the data is still fully available for export.

However, one point that needs to be added to the above blog, is that depending on how much data you have, the exported file can actually be too large to open in Excel (max rows exceeded).

So users may actually have to use segments to reduce the number of rows to make this file usable... or if they have access to a SQL program (MySQL or MSSQL, maybe even MS Access?, etc) this file can be imported into a temp DB table which won't have any length restrictions.

[#3]

Good point @Jennifer_Dungan .  I've also run into issues where the report was too large to email, even for smaller periods of time and subsets of data.  You can use FTP to work around this, but luckily CJA doesn't run into Low Traffic issues.  A Count Distinct calculated metric was able to get the essence of what I was wanting.

[#4]

We have a large volume site, a really large volume site. Many variables blow through the default limit in a day or two. While the data warehouse is an option, it practically limits who can pull the information to analysts. Sometimes you just gota increase the limits. Hopefully, advances in technology and lower prices will mitigate the issue. More squirrels to turn the wheels faster. 

[#5]

I just faced this issue. I tried with this solution with data warehouse. Thank you for this solution.