> 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/introduction.md).

# Introduction

{% hint style="warning" %}
**Note**: The Didomi tracker and vendor discovery is intended to be a guide for your organization that should be used in consultation with your DPO and legal team. It is not to be considered as a substitute for legal advice. 
{% endhint %}

The Didomi tracker and vendor discovery is a tool that enables your organization to receive a compliance evaluation of a given domain from a Didomi perspective. Leveraging our extensive knowledge of the privacy and compliance space, Didomi will furnish your organization with a Didomi rating and recommendations on how to increase your rating for the domain.

In this article, we provide a brief overview of the methodology Didomi utilizes to generate a tracker and vendor discovery for any given domain.

* [Bot navigation](#bot-navigation)
* [Data analysis](#data-analysis)
* [Generate tracker and vendor discovery](#generate-tracker-and-vendor-discovery)

{% hint style="info" %}
For more detailed compliance findings, please consider the Didomi [Advanced Compliance Monitoring module](/advanced-compliance-monitoring-acm/introduction.md). Contact your organization's account manager for more information. 
{% endhint %}

***

### Bot navigation

The Didomi bot will visit the configured domains to perform a *scraping session* in accordance with the configured parameters for each domain. During the scraping session, the Didomi bot will collect information about the trackers dropped and vendors triggered on the specific domain.

{% hint style="info" %}
[Click here](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-domains/request-tracker-and-vendor-discovery.md) for more information on how to reinitiate a scraping session and generate a new tracking and vendor discovery by the Didomi bot for a given domain.
{% endhint %}

### Data analysis

Once the Didomi bot has finished scrapping a domain, Didomi will analyze the collected data and convert the information into a human-readable format. By analyzing the dropped trackers and triggered vendors, Didomi will calculate any potential compliance issues that may be present on the domain. 

<table data-header-hidden><thead><tr><th width="214.7000732421875"></th><th></th></tr></thead><tbody><tr><td>Trackers</td><td>In addition to tracker information recorded, Didomi will also categorize the trackers into three distinct groups (cookies, pixels or local storage) and parse first-party trackers from third-party trackers. </td></tr><tr><td>Vendors</td><td>Didomi evaluates each vendor triggered on the domain.</td></tr></tbody></table>

### Generate tracker and vendor discovery

The analyzed data will be used to generate a tracker and vendor discovery for the domain after Didomi performs the following steps:

* Data aggregation
* Mapping of trackers to initiators
* Calculation of number of requests to/from each vendor
* Computation of recommendations&#x20;
* Calculation of Didomi rating

[Click here](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-results/tracker-and-vendor-discovery-results-overview.md) for an in-depth review on the data included in a tracking and vendor discovery for a domain.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/tracker-and-vendor-discovery/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.