# 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: 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:

```
GET https://cmp.docs.sirdata.net/en/faq/abconsent-cmp-is-compatible-with-taggr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.