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

# Configure tracker and vendor discovery (Classic scan)

{% hint style="success" %}
**Access Type**: Compliance Report - Editor
{% endhint %}

The Didomi tracker and vendor discovery (classic scan) is a tool that enables your organization to receive a compliance evaluation for up to 10 pages of a given domain from a Didomi perspective. In this article, we will cover how to configure a tracker and vendor discovery utilizing a classic scan for a domain.

Click **Tracker and Vendor Discovery** on the left-hand panel and select **Add Domain** on the subsequent page.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FT4nExLPlxTgTCfLQzXVl%2FScreenshot_2026-07-17_at_1_42_32%E2%80%AFPM.jpg?alt=media&amp;token=3b625c8b-a8e1-451c-a951-b6cdb99b38d8" alt="" width="563"><figcaption></figcaption></figure>

Select **Classic Scan** in the next modal.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FK2v26f6jcVyT7RiIbhGo%2FScreenshot%202026-07-01%20at%208.36.15%E2%80%AFAM.png?alt=media&amp;token=e6a79e65-1a2c-41ae-8327-9b064e251a32" alt="" width="375"><figcaption></figcaption></figure>

Use the provided fields to input the following information:

<table><thead><tr><th width="223.666748046875">Field</th><th>Description</th></tr></thead><tbody><tr><td>Give this domain a recognisable name</td><td>Internal name used to identify the domain</td></tr><tr><td>Target domain</td><td>URL of the domain that will be scrapped by the Didomi bot for the compliance report<br><br><strong>Example</strong>: <code>https://demosite.com</code></td></tr><tr><td>Launched from</td><td>Select country from which the Didomi bot scans. <br><br>Since the Didomi bot mimics an end-user's behavior (including the location from which the end-user accesses a domain), this field enables the Didomi bot to experience the CMP behavior targeted at end-users in a specific country. </td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FeBZKJMzaGXA9o7L2Wh4C%2FScreenshot%202026-07-01%20at%202.30.33%E2%80%AFPM.png?alt=media&amp;token=9b15b722-0c18-4276-9fed-c8f2893e87bd" alt="" width="563"><figcaption></figcaption></figure>

Next, use the provided **Behavior** cards to select how the collected data from the classic scan is interpreted. The default scenario for the scan will depend on the behavior selected:

{% hint style="info" %}
The behavior of the classic scan cannot be edited once the domain is saved. &#x20;
{% endhint %}

<table><thead><tr><th width="105.4166259765625">Behavior</th><th width="126.1165771484375">Scenario</th><th>Description</th></tr></thead><tbody><tr><td>Opt-in</td><td>Accept all</td><td>For regulations where consent is required before tracking and is a best fit for compliance concerns regarding European countries and any opt-in consent implementation.<br><br>Trackers that are fired before the end-user grants consent are treated as violations. </td></tr><tr><td>Opt-out</td><td>No actions</td><td><p>For regulations where tracking is enabled by default and end-users have to explicitly opt-out of tracking. A best for compliance concerns regarding U.S. privacy laws  and any opt-out consent implementations.</p><p></p><p>Trackers that persist after an end-user has opted out or when a GPC signal is present are treated as violations.</p></td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FDhyyWnpEVWs3UsFYN7Zt%2FScreenshot%202026-10-15%20at%2011.11.35%E2%80%AFAM.png?alt=media&amp;token=479375f8-1f0d-4b99-b108-ed4f72db1b02" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Additional bot scenarios and configurations are available with the Didomi [Advanced Compliance Monitoring (ACM) module](https://docs.didomi.io/advanced-compliance-monitoring-acm/introduction.md).
{% endhint %}

If required, expand the **Advanced** tab for the following configurations.

<table><thead><tr><th width="237.7332763671875">Field</th><th></th></tr></thead><tbody><tr><td>URL filter</td><td>Enables your organization to direct the bot to scrape only URLs that contain a specific string. For example, if your organization only wants to evaluate compliance on its product pages (all of which contain <code>/products/</code> in the URL, input the string into the field and the Didomi bot will limit its scraping to URLs that contain <code>/products/</code> <br><br><mark style="background-color:$warning;"><strong>Note</strong>: To use regular expression (regex) in the URL filter field, enable <strong>The URL filter is a RegEx</strong> checkbox.</mark> <a href="https://docs.didomi.io/get-started/general/regular-expression-regex.md"><mark style="background-color:$warning;">Click here</mark></a> <mark style="background-color:$warning;">for an overview on how to use regular expression.</mark> </td></tr><tr><td>N. of pages</td><td>Number of pages that the Didomi bot should scan. The maximum number of pages for tracker and vendor discovery (Classic scan) is 10 pages.</td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FfpgTF11hz0GibClnlAUn%2FScreenshot%202026-05-21%20at%206.29.06%E2%80%AFAM.png?alt=media&amp;token=f94add1c-c450-463d-8ec5-fbcde2b59780" alt="" width="563"><figcaption></figcaption></figure>

Confirm that you own the domain or acting on behalf of the domain owner to run the vendor and tracker discovery and click **Save & Run** when finished.&#x20;

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FlnOoK7mINVK2CzTlghiD%2FScreenshot%202025-10-24%20at%203.49.22%E2%80%AFPM.png?alt=media&amp;token=cd178806-cc73-44f0-ab7d-f0a56994e59a" alt="" width="563"><figcaption></figcaption></figure>

Once successfully added, Didomi will begin generating a vendor and tracker discover immediately. Your organization can always manually [re-initiate a discovery](https://docs.didomi.io/tracker-and-vendor-discovery/tracker-and-vendor-discovery-domains/request-tracker-and-vendor-discovery.md).&#x20;


---

# 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/configure-tracker-and-vendor-discovery-classic-scan.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.
