When a report has many unique values, Adobe provides functionality to ensure that the most important values appear in your report. Unique variable values collected after approximately 500,000 existing values are listed under a dimension item labeled Low-Traffic.
How Low-Traffic works
Reporting is not affected if the variable does not reach 500,000 unique values in a given month.
When a variable reaches 500,000 unique values, data begins to be bucketed under Low-Traffic. Each value beyond this threshold goes through the following logic:
If a value is already seen in reports, add to that value as usual.
If a value is not yet seen in reports, it initially is bucketed in the Low-Traffic dimension item.
If a value that is bucketed under Low-Traffic receives an influx of traffic (typically instances in the double digits in a single day), it starts being recognized as its own dimension item. Instances collected before meeting the threshold remain under Low-Traffic. The exact threshold has many dependencies, such as the number of servers processing data for the report suite and the amount of time between each dimension item instance.
If a report suite reaches more than 1,000,000 unique values, more aggressive filtering is applied. Unique values require instances in the triple digits in a single day before being recognized as its own dimension item.
This logic allows Adobe to optimize reporting capabilities while still allowing your organization to report on crucial dimension items collected later in the month. For example, your organization runs a site with millions of articles and a new article became popular towards the end of the month (after exceeding both unique thresholds). You could still analyze the performance of that article without it being bucketed under Low-Traffic. This logic is not intended to un-bucket everything that gets a certain number of page views per day or per month.
The Page dimension uses several backend columns that all count towards unique thresholds, including pagename, page_url, first_hit_pagename, first_hit_page_url, visit_pagename, visit_page_url, and click_context. These backend columns can cause Low-Traffic logic to apply well before the number of unique Page dimension items in Workspace reaches 500,000.
Changing unique limit thresholds
Threshold limits are 500,000 and 1 million unique values by default. These limits can be changed on a per-variable basis. Contact Adobe Customer Care or your organization’s account manager to request this change. When requesting a change, include:
The report suite ID
The variable you would like to increase the threshold for
Both the first and second threshold desired
Changes to thresholds can impact report performance. Adobe highly recommends using good judgment when requesting an increase to unique values in a variable. Only increase unique limits for variables that are critical to your organization’s reporting needs.
Low-traffic thresholds are not visible in the Analytics UI. Contact Adobe Customer Care if you would like more information on existing thresholds.
Low-traffic using components and other capabilities
Different capabilities treat low-traffic values in different ways.
Data Warehouse: There is no limit to the number of unique values in Data Warehouse reports. Its unique architecture allows the reporting of any number of unique values.
In some limited scenarios, low-traffic values can still appear. Examples include list vars, list props, merchandising eVars, and marketing channel detail dimensions.
Segmentation: If the segment criteria includes a variable with a high number of unique values, values captured under low-traffic are not included.
Classifications: Classification reports are also subject to unique limits. If a classification’s parent variable value is included under low-traffic, the value is not classified.
Low-traffic classification values obtained through the importer can be viewed in Data Warehouse.
Low-traffic classification values obtained through the rule builder cannot be viewed in Data Warehouse.