> 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/data-elements/delete-a-data-element.md).
# Delete a Data Element
## Introduction
This document outlines the step-by-step procedure for deleting a particular Data Element.
## Procedure
To delete a Data Element in Ingest Labs, perform the following steps:
**Step 1:** Select the Data Element 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 Data Element is deleted successfully.
**Note 1:** You cannot delete a Data Element if there are any dependencies in the tag. Only after deleting the dependent categories, you can delete the Data Element successfully.
**Note 2:** Even after deleting the dependencies, if you cannot delete the Data Element, 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ingestlabs.com/tag-manager/data-elements/delete-a-data-element.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.