> 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/view-previous-tracker-and-vendor-discoveries.md).
# View previous tracker and vendor discoveries
{% hint style="success" %}
**Access Type**: Compliance Report - Viewer or Editor
{% endhint %}
A tracker and vendor discovery is generated for a domain when the domain is first configured and when manually triggered. All of these discoveries are viewable from the Didomi console. In this article, we will cover how to view previous tracker and vendor discoveries for a domain.
{% hint style="info" %}
Previous versions of a tracker and vendor discovery's components (vendors and trackers) as well as previous versions of a [domain's cookie policy](broken://pages/fCOAyBlzA3EtzISLflLJ) can also be downloaded.
{% endhint %}
Click **Tracker and Vendor Discovery** on the left-hand panel and select **Details** inline with a domain on the subsequent page.
From the top panel, use the **Pick a report** drop-down menu to select a previous version of the tracker and vendor discovery.
The discovery and download links will automatically update to reflect the selected version.
---
# 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-results/view-previous-tracker-and-vendor-discoveries.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.
