# Is Abconsent compatible with Stape?

### CMP TCF & Server-Side: Yes, compatible with Stape… but even better with Sirdata

#### ✅ Full compatibility

**ABConsent**, the TCF CMP by Sirdata, is **fully compatible with Stape**, including in **server-side** environments.\
Consent signals (TC String) are accessible and can be used within your Stape containers **without any extra setup**.

***

#### 🚀 But why settle for compatibility?

Sirdata’s **server-side GTM container** goes far beyond simple integration.

**With Sirdata’s GTM Server-Side solution, you benefit from:**

* 🔓 **Advanced adblock resistance** to ensure signal delivery even in restricted environments.
* 📈 **Smart data enrichment** (geo, device context...) in full compliance with consent.
* 🪪 **Built-in transparency** through native integration with our TCF CMP.
* ⚡ **Optimized performance**, with reduced client-side load and improved reliability.

***

**In short:**\
✅ Yes, Sirdata works with Stape.\
🚀 But with our **fully integrated server-side stack** (CMP + GTM SS), you gain **better control, performance, and privacy compliance**.


---

# 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/integration/is-abconsent-compatible-with-stape.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.