> 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/whitelist-tracker-and-vendor-discovery.md).

# Whitelist tracker and vendor discovery

The Didomi tracker and vendor discovery utilizes [a bot ](https://docs.didomi.io/tracker-and-vendor-discovery/introduction.md#bot-navigation)to scan your configured domains and extract the information relevant to your compliance with frameworks such as GDPR, IAB TCF, GPP, and GPC.  However, if your domain is equipped with bot security tools (e.g. [CAPTCHA](https://www.cloudflare.com/learning/bots/how-captchas-work/)) the Didomi bot will receive an error when attempting to access your domain and will need to be added to your domain's whitelist so that it can successfully scrape pages for compliance data.

{% hint style="info" %}
A whitelist refers to a registry of entities that are permitted to access/interact with your domain.&#x20;
{% endhint %}

When the Didomi bot is scraping a domain, it will send a **user agent (UA)** containing the string `Didomi/`.

{% code overflow="wrap" %}

```
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Didomi/1.0
```

{% endcode %}

If your organization utilizes a bot protection solution, whitelist the user agent (UA) sent out by the Didomi bot by allowing user agents that contain the `Didomi/` string.

The full user agent (UA) can change regularly except for the `Didomi/` string.&#x20;

{% hint style="warning" %}
**Note**: For organizations who have subscribed to the Didomi Advanced Compliance Monitoring module, you can define a custom user agent (UA) that will be used by the Didomi bot.
{% 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 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/whitelist-tracker-and-vendor-discovery.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.
