> 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.md).

# Tracker and vendor discovery results

Data privacy regulations like the General Data Protection Regulation (GDPR) and US-state based regulations impact the way websites and apps are managed by enforcing your organization's obligations to ensure an end-user's consent is appropriately collected, documented, and respected.

The Didomi tracker and vendor discovery is an audit tool that enables your organization to review the compliance of your domain in regards to these regulations. It offers insight into how your website behaves when accessed, as well as validation that vendors and trackers are also being triggered as expected.

{% hint style="warning" %}
**Note**: The Didomi tracker and vendor discovery is intended to be a guide for your organization that should be used in consultation with your DPO and legal team. It is not to be considered as a substitute for legal advice or compliance validator. 
{% endhint %}

Be aware that the Didomi bot used in the tracker and vendor discovery can also give rise to false positives/negatives. As such, the only way to ensure your website's compliance is by validating that all requirements are met jointly with your DPO. 


---

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