> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/fr/analyses/analyses-de-la-plateforme-de-gestion-du-consentement-cmp/metriques-cmp/recuperer-le-taux-de-consentement-par-fournisseur-url-ou-finalite.md).

# Récupérer le taux de consentement par fournisseur, URL ou finalité

Didomi propose un tableau de bord d'analyse CMP pour récupérer les taux de consentement par fournisseur, URL ou finalité. 

{% hint style="info" %}
Votre organisation peut consulter les taux de personnalisation des fournisseurs et des consentements dans le tableau de bord Domains & Apps, mais sachez que ces données sont généralement inférieures à 2%.
{% endhint %}

Quelques options disponibles pour votre organisation afin de récupérer ces données sont : 

* [Personnaliser `événements`](https://developers.didomi.io/cmp/web-sdk/reference/events#preferences-clickpurposeagree) dans le SDK web Didomi pour intégrer ces données dans votre outil d'analyse. 
* Exploiter la fonctionnalité premium d'exportation par lots et calculer ces données au sein des outils d'analyse de votre organisation


---

# 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.didomi.io/fr/analyses/analyses-de-la-plateforme-de-gestion-du-consentement-cmp/metriques-cmp/recuperer-le-taux-de-consentement-par-fournisseur-url-ou-finalite.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.