From Analytics reporting standpoint, what are the consequences of increasing the unique limit of a variable?
To assist with data processing and retrieval times, Adobe Analytics employs logic that prevents variables from receiving too many different unique values. Unique variable values collected after approximately 500,000 existing values are listed under (Low-Traffic).
If a customer is seeing the line item: "Low traffic" in the Analytics reports, they can go for either of the two options to see all the values of the variable listed under the "Low traffic" line item:
Because Data Warehouse processes each request individually based on raw data collected, uniques management doesn't apply to many dimensions on this platform. This function is not intended to change. Therefore, it is the most reliable method to obtain all traffic sources data without any unique logic applied.
The customers can reach out to customer care to increase the unique limit for any five variables.
However, increasing this limit has few consequences(mentioned below) which must be communicated to the customer before increasing this limit.
- Consequences of setting custom unique limit for a variable
Any filters or breakdowns on this variable do not return in the interface. If you are running reports with filters or breakdowns, Data Warehouse is probably the way to go. Also, you would most likely run into hash collisions. This means that two (or more) Tracking IDs could get hashed to the same value and thus, the line item in reporting would aggregate both into the same line item.