> 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.md).

# Data Elements

Data Elements are the core components you define while creating the tags. Data elements act as components that intelligently fetch information from across your digital property. You can create any number of custom Data elements for a particular Data type and define the elements in the tags as per client requirements. Some of the Data types include Server Header, Server Cookie, Magic Pixel Data Layer, URL Parameter, Custom JavaScript, Custom event, and so on.

## Related Topics <a href="#relatedtopics" id="relatedtopics"></a>

The Data Elements section includes the following topics:

* [Data Elements Screen](/tag-manager/data-elements/data-elements-screen.md)
* [Add a New Data Element (Browser)](/tag-manager/data-elements/add-a-new-data-element-browser.md)
* [Add a New Data Element (Server)](/tag-manager/data-elements/add-a-new-data-element-server.md)
* [Edit a Data Element](/tag-manager/data-elements/edit-a-data-element.md)
* [Delete a Data Element](/tag-manager/data-elements/delete-a-data-element.md)
* [Restore the Changes](/tag-manager/tags/restore-the-changes.md)
* [Data Element Version](/tag-manager/data-elements/data-element-version.md)

[<br>](https://ingest-lab.netlify.app/tagmanager/tags/tagversion/)


---

# 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/data-elements.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.