Path Duplicate Consolidation FAQ

Cookie Consent has made enhancements to the Categorizations and Scan Results interfaces that consolidate cookies known as path duplicates. Consolidating path duplicates streamlines your experience when managing cookies and provides clearer insight into the tracking technology deployed on your domains.

What is a path duplicate?

Path duplicates are cookies with same name, host, and secure flag values, but different path values.

Cookie uniqueness is based on a combination of Name + Host + Secure + Path. Some cookies are set uniquely on each path, in which the path is identical to the page of the domain on which it’s set. These cookies can only be set and accessed within the page path on which they’re specified. For example, you would not see cookies with path = products/data-discovery on the products/cookie-consent page. However, each cookie, because of the path value, is unique, even if the name, host, and secure flag is the same. These are commonly referred to as path duplicates within OneTrust.

How does this affect my cookie count?

Although there are unique records for each cookie in the database table, OneTrust consolidates path duplicates into one cookie in the Categorizations tab and on the Preference Center. The reason you see a noticeable difference in the count between website scan results and cookie categorization pages is because of this front-end consolidation.

What's changing in Cookie Consent?

OneTrust has implemented changes to the backend and UI that will consolidate these path duplicates and store the records in separate tables. You will now only see one instance of a cookie (even if path duplicates were found by the scanner).



Before path duplicate consolidation.



After path duplicate consolidation.