> 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/faq/integration/abconsent-est-il-compatible-avec-stape.md).

# ABConsent est-il compatible avec Stape ?

### CMP ABConsent & Server-Side : Oui, compatible avec Stape… mais encore mieux avec Sirdata

#### ✅ Compatibilité assurée

La CMP TCF **ABConsent** de Sirdata est **totalement compatible avec Stape**, y compris dans un déploiement **server-side**.\
Les signaux de consentement (TC String) sont accessibles et exploitables depuis vos containers Stape, **sans configuration complexe**.

***

#### 🚀 Mais pourquoi se contenter de la compatibilité ?

Le **server-side by Sirdata**, via notre **container GTM clé-en-main**, offre bien plus qu’un simple relais technique.

**Avec le GTM Server-Side Sirdata, vous profitez de :**

* 🔓 **Un désadblocking avancé** pour contourner les restrictions des navigateurs et extensions.
* 📈 **Un enrichissement contextuel** des appels server-side dans le respect du consentement.
* 🪪 **Une transparence native** grâce à une intégration directe avec notre CMP TCF.
* ⚡ **Des performances optimisées**, sans latence ni surcharge côté client.

***

**En résumé :**\
✅ Oui, Sirdata est compatible avec Stape.\
🚀 Mais notre **stack server-side intégrée** (CMP + GTM SS) vous garantit **plus de contrôle, de performance et de conformité**.


---

# 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/faq/integration/abconsent-est-il-compatible-avec-stape.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.