> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/tag-manager/qualification-criteria/delete-a-qualification-criteria.md).
# Delete a Qualification Criteria
## Introduction
This document provides step-by-step instructions for deleting a Qualification Criteria.
## Procedure
**Step 1:** Select the Qualification Criteria that you want to delete.
**Step 2:** From the **Actions** drop-down menu on the top right corner, select **Delete**.
**Step 3:** Click **Yes** on the confirmatory message that appears.
**Step Result**: The Qualification Criteria is deleted successfully.
**Note:** You cannot delete a Qualification Criteria if there are any dependencies in the tag. Only after deleting the dependent categories, you can delete the Qualification Criteria successfully. Even after deleting the dependencies, if you cannot delete the Qualification Criteria, then you must Publish the relevant categories first and then perform the delete operation.
{% embed url="" %}
---
# 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.ingestlabs.com/tag-manager/qualification-criteria/delete-a-qualification-criteria.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.
