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

# Tags

Tags are a collection of data elements, providers, qualification criteria, and privacy settings. Tags are used to build simplified data points and analyze and monitor the data in real-time to ease the marketing processes. You can use the code snippet or MediaPixel to configure the data, send data to providers, and simplify the marketing processes. The two types of Tag Management Solutions are Server-side Tagging solution and Browser/Client-side Tagging solution.

### Server-side Tagging <a href="#server-sidetagging" id="server-sidetagging"></a>

In Server-side Tagging, the events are sent to Ingest Labs and based on the events and configuration of tags, the respective tags are triggered. Server-side tagging includes the marketing needs of the server-side ecosystem. You can collect the data in a first-party consented manner for better control over data collection and transfer the high-performance tag management and streaming to the customer. All integrations are performed using MagicPixel UI platform.

### Client-side Tagging <a href="#client-sidetagging" id="client-sidetagging"></a>

In Client-side tagging, events are not sent to the server and all tasks are performed on the client directly. The tags are triggered on the browser or client website and not sent to the server. Ingest Labs collects the tag information and reports triggered through the SDK on the client website. However, the actual tags are triggered on the client.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2F0Oah4oDJelTTQWVlqgs8%2Fimage.png?alt=media&amp;token=60df4a6e-c5df-4ce8-ad5b-57914ed76fe7" alt=""><figcaption></figcaption></figure>

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

The Tags section includes the following topics:

* [Tags Screen](https://ingest-lab.netlify.app/tagmanager/tags/tagsscreen/)
* [Configuration of Tags](https://ingest-lab.netlify.app/tagmanager/tags/configurationoftags/)
* [Add a New Tag (Browser)](https://ingest-lab.netlify.app/tagmanager/tags/addanewtagbrowser/)
* [Add a New Tag (Server)](https://ingest-lab.netlify.app/tagmanager/tags/addanewtagserver/)
* [Edit a Tag](https://ingest-lab.netlify.app/tagmanager/tags/editatag/)
* [Disable a Tag](/tag-manager/tags/disable-a-tag.md)
* [Restore the Changes](/tag-manager/tags/restore-the-changes.md)
* [Tag Version](/tag-manager/tags/tag-version.md)

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


---

# 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/tags.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.