> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/assets-library/trackers-page/managing-trackers/trackers-deletion-rules.md).

# Trackers deletion rules

This guide explains how the tracker deletion system works in AB Tasty and helps you understand the risks involved when removing a tracker and our safeguards.

{% hint style="success" %}
Trackers help you measure the performance of your campaigns. You can view and manage them from **Library > Trackers**.\
\
[Read our dedicated article to learn more about trackers](/assets-library/trackers-page.md).

\
To learn how to delete trackers, read our [Managing trackers ](/assets-library/trackers-page/managing-trackers.md#h_01j0jwvm2fvzaqmbrnrn5sbt90)article.
{% endhint %}

When you delete a tracker, AB Tasty checks whether it’s used in any campaigns and displays a warning to help you avoid disrupting your setup or losing valuable data.

This article explains our safeguard system, which alerts you when the tracker you want to delete is currently in use, helping you avoid accidentally disrupting your campaigns or losing valuable data.

Tracker usage is grouped into three risk levels:

### Tracker used in a Live campaign ( :warning: High risk)

You cannot delete a tracker if it’s used in a campaign with the **Live** status.

To delete the tracker, you must either:

* Change the campaign status (e.g. to **Paused** or **Ended**)
* Remove the tracker from the campaign’s goal list

This restriction prevents you from disrupting active experiments or losing live performance data.

***

### Tracker used in other campaign states (⚠ Medium risk)

You can delete a tracker that’s used in campaigns with one of the following statuses:

* **In QA**
* **Ready**
* **Scheduled**
* **Paused**
* **Analysis**
* **Ended**

You’ll receive a warning indicating that the tracker is still in use.

{% hint style="warning" %}
We recommend reviewing its usage before deletion. These campaigns may still rely on the tracker, and removing it could affect recent or upcoming analyses.
{% endhint %}

***

### Tracker used in draft or archived campaigns ( :white\_check\_mark: Low risk)

You can safely delete a tracker if it’s only used in campaigns with the **Draft** or **Archived** status:

* **Draft**: The campaign hasn’t started yet
* **Archived**: The campaign is finished and no longer active

{% hint style="success" %}
Deleting the tracker won’t affect any live or historical data.
{% 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.abtasty.com/assets-library/trackers-page/managing-trackers/trackers-deletion-rules.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.