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

# Edit tracker and vendor discovery

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

The Didomi tracker and vendor discovery is a tool that enables your organization to receive a GDPR compliance evaluation of a given domain from a Didomi perspective. In this article, we will cover how to edit an existing tracker and vendor discovery for a domain.

{% 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 %}

Click **Tracker and Vendor Discovery** on the left-hand panel and select the ellipsis inline with a domain on the subsequent page.

Click **Edit this domain** from the drop-down menu.

<figure><img src="/files/GCAkwczPigT5p58o2to9" alt="" width="563"><figcaption></figcaption></figure>

Apply any edits to the tracker and vendor discovery configuration. Click the links below for more information on how to configure the tracker and vendor discovery by scan type.

* [Configure tracker and vendor discovery (Classic scan)](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-domains/configure-tracker-and-vendor-discovery-classic-scan.md)
* [Configure tracker and vendor discovery (XL scan)](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-domains/configure-tracker-and-vendor-discovery-xl-scan.md)

When finished, select one of the following options:

<table data-header-hidden><thead><tr><th width="191"></th><th></th></tr></thead><tbody><tr><td>Save</td><td>Saves the edits to the scan configuration but does not immediately trigger a scan. The next scan in accordance with the discovery frequency configuration will include these edits.</td></tr><tr><td>Save &#x26; Run</td><td>Saves the edits to the scan configuration and immediately triggers a scan of the domain.</td></tr><tr><td>Save &#x26; Run Discovery</td><td>Saves the edits to the scan configuration and immediately triggers a discovery for the domain.</td></tr></tbody></table>

<figure><img src="/files/HiIyJnRXeD7FgAeWVhFO" alt="" width="563"><figcaption></figcaption></figure>


---

# 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-domains/edit-tracker-and-vendor-discovery.md?ask=<question>&goal=<endgoal>
```

`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.