> 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-domains/request-tracker-and-vendor-discovery.md).
# Request tracker and vendor discovery
{% hint style="success" %}
**Access Type**: Compliance Report - Editor
{% endhint %}
Didomi automatically generates a tracker and vendor discovery for a domain when:
* the discovery is initially configured
* your organization chooses to **Save and Run** after editing the discovery.
In addition to the above scenarios, your organization can manually initiate a Didomi bot scraping session to generate a tracker and vendor discovery.
{% hint style="info" %}
The following is applicable to both [tracker and vendor discovery (classic scan)](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-domains/configure-tracker-and-vendor-discovery-classic-scan.md) and [tracker and vendor discovery (XL scan)](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-domains/configure-tracker-and-vendor-discovery-xl-scan.md).
{% endhint %}
To manually request a discovery for a domain, click **Tracker and Vendor Discovery** on the left-hand panel. Navigate to a domain on the subsequent list and click the **ellipsis** inline with the domain name.
Select **Request new report** from the drop-down menu.
Confirm the decision to request a new tracker and vendor discovery in the subsequent modal and click **Confirm the request**.
{% hint style="info" %}
**XL scan**
A subsequent modal will relay the number of XL scans contracted for by your organization, the number of XL scans used, and remaining. Click **Proceed with Scan**.
{% endhint %}
The Didomi bot will perform a scraping session on the designated domain and generate the tracker and vendor discovery when finished.
---
# 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/tracker-and-vendor-discovery-domains/request-tracker-and-vendor-discovery.md?ask=&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.
