> 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/en/consent-transmission-standards/facebook-consent-mode.md).

# Facebook Consent Mode

## Facebook Consent Mode (Meta)

The integration of **Facebook Consent Mode** by Sirdata allows you to automatically synchronize your users' consent status with Meta's advertising tools (Facebook & Instagram).

### Overview

This feature transmits consent signals ("revoke" or "grant") to Facebook pixels and tags without requiring manual modifications to your source code or GTM tags.

#### Key Benefits:

* **Simplified Compliance:** Adhere to Meta's policies and GDPR requirements without heavy technical intervention.
* **Automation:** The CMP natively manages the transmission of signals as soon as it loads.
* **Performance:** Ensures your advertising campaigns receive the appropriate signals to optimize tracking.

### Configuration

To activate this option, follow these steps within your interface:

1. Access your **CMP configurations** management.
2. Access to **Add-on** section
3. Go to the **Other partners** (Autres partenaires) section.
4. Locate the **Facebook Consent Mode** block.
5. Activate the option by clicking the **Toggle** switch.
6. **Save** your configuration.

> For Facebook Consent Mode to function correctly, the ABconsent CMP must imperatively be loaded **before** your Facebook scripts or tags on your website.

### Technical Operation

Once the option is activated, the ABconsent CMP communicates directly with the Facebook Pixel. If the user denies consent, refusal signals are transmitted instantly to limit data collection in accordance with the user's choices. Conversely, if consent is granted, "grant" signals authorize standard advertising tracking.

### In the United States

On the U.S. banner (CCPA), the same option does not pause the pixel: it passes the visitor's opt-out through Meta's **Limited Data Use** option. If you also use the Conversions API, see [Limited Data Use (United States)](/en/consent-transmission-standards/facebook-consent-mode/meta-limited-data-use-us.md).

***

*Last updated: December 2025*


---

# 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/en/consent-transmission-standards/facebook-consent-mode.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.