> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/faq/abconsent-cmp-is-compatible-with-taggr.md).

# Abconsent CMP is compatible with Taggr ?

#### Abconsent & Server-Side: Yes, compatible with Taggr… but even better with Sirdata

✅ **Seamless Compatibility**\
Sirdata’s TCF CMP is fully compatible with **Taggr**, including in **server-side** environments.

No complex setup required: **Taggr automatically retrieves the TCF signals (TC String)** generated by our CMP, ensuring smooth and compliant integration from the first page load.

***

🚀 **What if you switched to Sirdata’s Server-Side solution?**\
Our turnkey **GTM Server-Side** setup isn’t just compatible —\
it goes **above and beyond** to meet today’s privacy and performance challenges.

With the **Sirdata server-side container**, you get:

🔓 **Advanced adblock resistance**, to ensure signal delivery even in restricted environments.\
📈 **Smart data enrichment**, always in full compliance with user consent.\
🪪 **Full transparency**, with native support for the TCF framework on the server side.\
⚡ **Boosted performance**, thanks to a streamlined and optimized architecture.

***

#### In short:

✅ Yes, your Abconsent CMP works perfectly with **Taggr**.\
🚀 But with **Sirdata’s server-side solution**, you unlock a more **powerful, flexible, and privacy-first** setup.


---

# 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://cmp.docs.sirdata.net/en/faq/abconsent-cmp-is-compatible-with-taggr.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.