> 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/data-manager/tracker-policy/tracker-exemption.md).
# Tracker exemption
{% hint style="success" %}
**Access Type**: Data Manager - Editor
{% endhint %}
A tracker exemption is a setting that designates a tracker as consent-exempt (i.e. the tracker does not require consent).
Historically, your organization would manually configure tracker exemptions on a per domain basis for tracker and vendor discovery or Advanced Compliance Monitoring scans. Improvements to the Didomi platform has changed this behavior, however, and tracker exemptions are calculated in the Didomi back-end based on the legal basis of purposes assigned to a tracker.
{% hint style="info" %}
Visit the resources below for how purposes are assigned to a tracker:
* [Add tracker](/data-manager/trackers/add-tracker.md)
* [Unmatched trackers](/data-manager/trackers/unmatched-trackers.md)
{% endhint %}
The table below summarizes how Didomi calculates tracker exemptions. Trackers are only exempted when **all** assigned purposes to the tracker utilize legitimate interest (opt-out) as a legal basis.
Assigned purpose(s) legal basis
Tracker exempted
Consent
false
Legitimate Interest (Opt-Out)
true
Consent and Legitimate Interest
false
Tracker exemptions on a per domain basis can be viewed by clicking **Tracking and Vendor Discovery** or **Advanced Compliance Monitoring** on the left-hand panel.
Click the ellipsis inline with a scan and select **Manage tracker policy** from the drop-down menu.
{% hint style="warning" %}
**Note**: Be advised that the tracker policy when viewed on a domain scan is read-only. The actual configuration is performed within your organization's data manager. [Click here](/data-manager/tracker-policy/configure-tracker-policy.md) for more information.
{% endhint %}
The read-only table on the subsequent page will list the trackers discovered on the page and the following information:
* Tracker name
* 1st/3rd party
* Initiator
* Vendor
* Type
* User behavior
* Purposes
* Exemption
---
# 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/data-manager/tracker-policy/tracker-exemption.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.
