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

# Download tracker and vendor discovery

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

Once a tracker and vendor discovery is generated on a domain your organization can download the discovery's components (vendors and trackers) onto your local machine in a variety of formats. In this article, we will cover the following:

* [Download tracker and vendor discovery](#download-tracker-and-vendor-discovery)
* [Vendors result glossary](#vendors-result-glossary)
* [Trackers result glossary](#trackers-result-glossary)

{% hint style="info" %}
[Click here](broken://pages/fCOAyBlzA3EtzISLflLJ) for information on downloading the cookie policy for a domain. 
{% endhint %}

***

### Download tracker and vendor discovery

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

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

From the top panel, use the **Pick a report** drop-down menu to select the discovery you wish to download.

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

Click the **download** icon and select the compliance report component and format in the subsequent modal. The specified file will be downloaded onto your local machine.

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

### Vendors result glossary

Refer to the table below for more information on the data included in a downloaded vendors component of a discovery.

{% hint style="warning" %}
**Note**: The difference between a vendor and initiator is that:

* **Vendor** - requests a tracker to be launched. They have  has access to the data and are responsible of the data treatment
* **Initiator** - the party that is technically called by the **Vendor** to launch the tracker
  {% endhint %}

<table><thead><tr><th width="229.4500732421875">Field</th><th>Description</th></tr></thead><tbody><tr><td>Date</td><td>Date the compliance report was generated for which the vendor was found on the domain</td></tr><tr><td>Vendor</td><td>Name of vendor within Didomi database<br><br><mark style="background-color:$warning;"><strong>Note</strong>: If vendor is not present in the Didomi database, the field will be empty.</mark></td></tr><tr><td>Page URL</td><td>URL where the vendor was found on your domain</td></tr><tr><td>Request URL</td><td>URL that triggered the vendor</td></tr><tr><td>Is tag</td><td>Is the vendor considered a tag (request was made to a JavaScript file)?</td></tr><tr><td>Tag type</td><td>File type that was requested</td></tr><tr><td>TCF id</td><td>IAB TCF vendor ID (if vendor is a part of the IAB TCF)</td></tr><tr><td>Initiator URL</td><td>URL of the initiator </td></tr><tr><td>Initiator vendor</td><td>Name of the initiator</td></tr><tr><td>Processing rule</td><td>The legal bases used by vendor</td></tr><tr><td>Initiator processing rule</td><td>The legal bases used by the initiator</td></tr></tbody></table>

### Trackers result glossary

Refer to the table below for more information on the data included in a downloaded trackers component of a discovery.

{% hint style="warning" %}
**Note**: The difference between a vendor and initiator is that:

* **Vendor** - requests a tracker to be launched. They have  has access to the data and are responsible of the data treatment
* **Initiator** - the party that is technically called by the **Vendor** to launch the tracker
  {% endhint %}

<table><thead><tr><th width="246.95001220703125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Initiator Vendor</td><td>Name of the initiator that launched the tracker</td></tr><tr><td>Initiator URL</td><td>URL of the initiator of the tracker</td></tr><tr><td>Vendor</td><td>Name of the vendor that requested the tracker be launched</td></tr><tr><td>Page URL</td><td>URL where the tracker was found on your domain</td></tr><tr><td>Cookie domain</td><td>Domain of the tracker</td></tr><tr><td>Cookie name</td><td>Name of the tracker</td></tr><tr><td>Lifetime (in seconds)</td><td>Lifetime of the tracker before it expires in seconds</td></tr><tr><td>Sample</td><td>A sample of data within the tracker</td></tr><tr><td>Party</td><td>Trackers can be categorized into 1st-party or 3rd-party depending on which entity has triggered the dropping of the tracker. If the website itself is dropping a tracker then it will be counted as a 1st-party tracker. A tracker dropped by a vendor will be counted as a 3rd-party tracker.<br><br><mark style="background-color:$warning;"><strong>Note</strong>: Cookies can be created by a vendor (initiator) but still be dropped by the website itself (e.g. tag managers). In this case, the tracker is considered a 1st-party tracker.</mark> </td></tr><tr><td>Type</td><td><p>Indicates whether the track is a:</p><p></p><ul><li><strong>Cookie</strong> - Small block of data placed on the end-user's device while. Cookies will expire based on their settings. </li><li><strong>Pixel</strong> - an HTML code snippet which is loaded when an end-user visits a website or opens an email. Pixels are useful for tracking end-user behavior and conversions.</li><li><strong>Web storage</strong> - Enables a party to access a local storage object and store data in the browser with no expiration date. Data stored in the browser will persist even after the browser window has been closed.</li><li><strong>Indexed DB</strong> - Client-side storage mechanism within web browsers, designed to allow web applications to store large amounts of structured data locally on the user's device for offline functionality and performance enhancements</li></ul></td></tr><tr><td>Purposes</td><td>Purpose names for purposes mapped to the tracker in the tracker policy for the domain</td></tr><tr><td>Exemptions</td><td>Indicates if the tracker is configured as consent-exempt in the tracker policy for the domain:<br><br><strong>Yes</strong> | <strong>No</strong></td></tr></tbody></table>


---

# 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-results/download-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.