> For the complete documentation index, see [llms.txt](https://community.commandersact.com/customer-success/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/customer-success/faqs/consent-and-preference-management/about-cmp.md).

# About CMP ?

<details>

<summary>Why is integrating a consent banner important?</summary>

* **Protecting democracies** > manipulation, fake news, citizen surveillance...&#x20;
* **To protect ourselves** > discrimination: access to health and finance, ethical issues in machine learning, profiling...&#x20;
* **To frame security breaches and data leaks** > identity theft, financial loss, ...&#x20;

</details>

<details>

<summary>Impact of poor consent management for publishers?</summary>

**MAIN IMPACT**

* Lower traffic monetization (harder to sell ad spaces without user data + CPMs are lower)

**CONSEQUENCES**

* Loss of revenue for the publisher
* Encouragement of toxic practices in order to generate more traffic and/or more clicks (click-baiting races, enticing headlines, poor content quality...)

**SIDE EFFECTS**

* Decrease in available RTB inventory > increase in CPM/CPC for advertisers
* Reduce ability to allocate revenue to OOH campaigns > shift budget to other channels
* No more spending of advertising budget on (Facebook, Google, ...)

</details>

<details>

<summary>Impact of poor consent management for e-merchants?</summary>

**MAIN IMPACT**

* Lower conversion rate (it is more difficult to personalize customer journeys on site as well as off site / via ads)

**CONSEQUENCES**

* Loss of revenue for the website/e-commerce application > competitive disadvantage
* Poor marketing decisions > not able to attribute sales to the right channel

**SIDE EFFECTS**

* Decrease in available RTB inventory > increase in CPM/CPC for advertisers
* Reduce ability to allocate revenue to OOH campaigns > shift budget to other channels
* No more spending of advertising budget on (Facebook, Google, ...)

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://community.commandersact.com/customer-success/faqs/consent-and-preference-management/about-cmp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.