> 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/trackers/delete-tracker.md).
# Delete tracker
{% hint style="success" %}
**Access Type**: Data Manager - Editor
{% endhint %}
In this article, we will cover how to delete a tracker from your organization's data manager.
Click **Data Manager** on the left-hand panel and select **Trackers** on the subsequent page.
Use the provided search field to search for the tracker. Navigate to the tracker on the list and click the **Delete** icon inline with the tracker name.
{% hint style="warning" %}
**Note**: Only trackers that your organization has added to the data manager can be deleted.
{% endhint %}
Confirm the decision to delete the tracker in the subsequent modal and click **Yes, delete**.
The tracker will be deleted from the data manager.
{% hint style="info" %}
The tracker will also be removed from any [tracker policies](/data-manager/tracker-policy.md) to which it previously belonged. If your organization has implemented a tracker policy on a property that included this tracker, you will need to re-download and update the policy on the property. [Click here](/data-manager/tracker-policy/download-tracker-policy.md) for more information.
{% endhint %}
---
# 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/trackers/delete-tracker.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.
