> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/tracker-and-vendor-discovery/tracker-and-vendor-discovery-results/tracker-and-vendor-discovery-results-overview.md). # Tracker and vendor discovery results overview {% hint style="success" %} **Access Type:** Compliance Report - Viewer or Editor {% endhint %} The Didomi tracker and vendor discovery is an audit tool that enables your organization to review the compliance of your domain in regards to GDPR regulations. It offers insight into how your website behaves when accessed, as well as validation that vendors and trackers are also being triggered as expected. In this article, we provide an overview of the data included in the following tabs of the tracker and vendor discovery results: * [Didomi rating](#didomi-rating) * [Trackers](#trackers) * [Vendors](#vendors) * [Compliance issues](#compliance-issues) Navigate to the results of a tracker and vendor discovery by clicking **Tracker and Vendor Discovery** on the left-hand panel and selecting **Details** inline with a domain on the subsequent page.

{% hint style="warning" %} **Note**: Additional information is included in the scan results for organizations who have Advanced Compliance Monitoring (ACM). [Click here](/advanced-compliance-monitoring-acm/acm-report-domains.md) for more information. {% endhint %} *** ### Didomi rating The Didomi rating is a custom assessment made by Didomi that evaluates the domain based on a variety of factors such as: * trackers have a reasonable lifetime * presence of a CMP * presence of a privacy policy * privacy policy is linked on all pages * privacy policy provides an opt-out mechanism * Vendors use the HTTPS protocol The above factors are given a specific weight in the calculation and produces a score from 0% to 100%.

{% hint style="warning" %} **Note**: The factors used to calculate the Didomi rating can be edited for tracker and vendor discoveries (XL Scan). {% endhint %} ### Trackers Click the **Trackers** tab to review data on the trackers discovered on the domain for the tracker and vendor discovery.

The data on the trackers tab can be filtered by the following parameters:

Filter	Description
Vendor	Requests a tracker to be launched. They have access to the data and are responsible of the data treatment.
Type	There are four types of trackers: Cookie - Small block of data placed on the end-user's device while. Cookies will expire based on their settings. Pixel - an HTML code snippet which is loaded when an end-user visits a website or opens an email. Pixels are useful for tracking end-user behavior and conversions. Web storage - Enables a party to access a local storage object and store data in the browser with no expiration date. Data stored in the browser will persist even after the browser window has been closed. Indexed DB - Client-side storage mechanism within web browsers, designed to allow web applications to store large amounts of structured data locally on the end-user's device for offline functionality and performance enhancements
Host/domain	Domain of the tracker
1st/3rd-party	Trackers can be categorized into 1st-party or 3rd-party depending on which entity has triggered the dropping of the tracker. If the website itself is dropping a tracker then it will be counted as a 1st-party tracker. A tracker dropped by a vendor will be counted as a 3rd-party tracker. Note: Cookies can be created by a vendor (initiator) but still be dropped by the website itself (e.g. tag managers). In this case, the tracker is considered a 1st-party tracker.
User behavior	Click here for more information on how the user behavior is calculated. Note: Only available for Tracker and Vendor Discovery - XL Scans
Actions	Actions taken that resulted in tracker being dropped Note: Only available for Tracker and Vendor Discovery - XL Scans

For each tracker dropped on the domain in the discovery Didomi will provide the following information:

Field	Description
Tracker name	Name of the tracker as found on the domain. Click the tracker name to view additional information for the tracker.
Vendor	Name of the initiator that launched the tracker
Type	Indicates whether the tracker is a cookie, pixel, web storage, or Indexed DB. See filter table above for more information.
Host/domain	Domain of the tracker
1st/3rd party	Indicates whether the tracker is categorized as a 1st-party or 3rd-party tracker. See filter table above for more information.
User behavior	Click here for more information on how the user behavior is calculated. Note: Only available for Tracker and Vendor Discovery - XL Scans
Actions	Actions taken that resulted in tracker being dropped Note: Only available for Tracker and Vendor Discovery - XL Scans

### Vendors Click the **Vendors** tab to review data on the vendors discovered on the domain for the tracker and vendor discovery.

The data on the vendors tab can be filtered by the following parameters: {% hint style="warning" %} **Note**: Only available for Tracker and Vendor Discovery - XL Scans {% endhint %}

Filter	Description
TCF/Non-TCF	Filters list of vendors into either: Vendors who belong to the IAB Transparency and Consent Framework (TCF) Vendors who do not belong to the IAB Transparency and Consent Framework (TCF)
Processing rule	The legal bases used by vendor
User behavior	Click here for more information on how the user behavior is calculated. Note: Only available for Tracker and Vendor Discovery - XL Scans
Actions	Filters list of vendors by the action executed by the Didomi bot when the vendor was triggered. Note: Only available for Tracker and Vendor Discovery - XL Scans

For each vendor discovered on the domain in the discovery Didomi will provide the following information:

Field	Description
Name	Name of the vendor
Country	Country where the vendor has its headquarters
TCF ID	If vendor is a member of the IAB TCF then Didomi will display the vendor's IAB TCF ID.
Processing rule	Legal base used by the vendor
Requests for tags	Number of requests that the vendor has performed
User behavior	Click here for more information on how the user behavior is calculated. Note: Only available for Tracker and Vendor Discovery - XL Scans
Ran scenarios	Scenario utilized by the Didomi bot when the vendor was discovered. Note: Only available for Tracker and Vendor Discovery - XL Scans
Actions	Actions taken that resulted in tracker being dropped Note: Only available for Tracker and Vendor Discovery - XL Scans

Additional information for a particular vendor can be viewed by clicking the name of the vendor from the list. A subsequent modal will provide the following information for the vendor: * Whether vendor is a member of the IAB TCF * Privacy policy * Domains owned by the vendor according to the Didomi database * Trackers dropped by the vendor on your domain * Vendors who requested this particular vendor * Vendors who were initiated by this particular vendor

In addition to the table view of vendors found on the domain, Didomi also provides an interactive graph that visualizes how vendors are being requested on the domain. Select any vendor on the graph to highlight how it is called on your domain and which vendors it subsequently calls on your domain.

### Compliance issues For every tracker and vendor discovery generated on a domain Didomi will catalogue any potential problems as it pertains to GDPR compliance in the **Compliance issues** tab of the discovery. These issues and recommendations are based on Didomi's extensive knowledge of the data privacy landscape but should **not** be taken as legal advice. Rather, use the catalogued issues and recommendations as a starting point with your Data Protection Officer (DPO) before taking any action. Click the **Compliance issues** tab to review the issues catalogued for the discovery. {% hint style="info" %} Expand the accordion for certain compliance issues for more detailed information. {% endhint %}

Review the table for the issues and recommendations Didomi can raise within a discovery: {% hint style="warning" %} **Note**: Only available for Tracker and Vendor Discovery - XL Scans {% endhint %}

Issues	Description
The Privacy Policy is not accessible from every page of the website	Didomi bot was unable to access your organization's privacy policy on at least one page for the domain. Note: This issue does not mean the privacy policy does not exist on the page but that the bot was unable to detect it during the scraping session. This issue can arise from how your privacy policy is worded.
No CMP was detected on the website	Didomi bot did not encounter a consent management platform (CMP) to provide end-user consent.
The privacy policy does not seem to provide a way to opt out	Didomi bot was unable to find a link/button in the privacy policy that allows an end-user to manage their consent preferences.
The consent notice doesn’t provide information about purposes and vendors	Didomi bot unable to find information about vendors and purposes your organization uses to process end-user data in the consent notice.
Number of trackers that have lifetime longer than 13 months which is not recommended by GDPR	Didomi bot discovered cookies dropped on domain with lifetimes exceeding 13 months. Ask the vendor dropping the cookies to reduce the lifetime of the cookie to to delete it completely. Click here to learn more.
Number of vendors or initiators that are unknown to our database, review them to be sure they are legit	Vendor or initiator found on domain is not known in the Didomi database. Avoid this issue in future discoveries by manually matching the vendor. Click here for more information.
A Cookie Policy wasn’t found	Didomi bot unable to find cookie policy on domain.
Number of trackers dropped despite user not making a choice	Didomi bot discovered trackers on domain when the end-user did not make a consent decision. Note: Only available for Tracker and Vendor Discovery - XL Scans
Number of trackers dropped despite user refusing consent	Didomi bot discovered trackers on domain when the end-user explicitly refused consent. Note: Only available for Tracker and Vendor Discovery - XL Scans

{% hint style="info" %} There are additional issues and recommendations Didomi can surface for organizations utilizing Advanced Compliance Monitoring (ACM). [Click here](/advanced-compliance-monitoring-acm/acm-report-results/compliance-issues-acm.md) for more information. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.didomi.io/tracker-and-vendor-discovery/tracker-and-vendor-discovery-results/tracker-and-vendor-discovery-results-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.