> 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/microsoft-uet-consent-mode.md).

# Microsoft UET Consent Mode

**Microsoft Consent Mode is now mandatory for several reasons.** With the introduction of new regulations such as the **DSA (Digital Services Act)** and **DMA (Digital Markets Act),** the need for strict consent management has increased. **Microsoft Advertising,** as an EU-designated **"access controller"** alongside other gatekeepers, must comply with these requirements. As a result, Microsoft requires advertisers operating in the **European Economic Area (EEA), the United Kingdom, and Switzerland** to use the **UET (Universal Event Tracking) tag** to transmit user consent signals.

Failing to comply with this requirement can lead to significant consequences: key functionalities, such as **conversion tracking,** may be suspended, and collected data could be incomplete or inaccurate. Without user consent transmission to **UET**, advertisers risk losing valuable data, which may impact their ability to optimize campaigns, create relevant audience segments, and leverage automated bidding.

**To enable Microsoft UET Consent Mode, simply add Microsoft Advertising to your list of partners, or manually activate the Microsoft UET Consent Mode compatibility option. Enabling one will automatically activate the other.**

<figure><img src="/files/GORP8riiMIuAFsIEVlsj" alt=""><figcaption><p>Add new partner</p></figcaption></figure>

<figure><img src="/files/GB1HiriWsqHkUtCP9Ol1" alt=""><figcaption><p>Select Microsoft Advertising</p></figcaption></figure>

<figure><img src="/files/dCYTD3pDuEpPUlkI0fXo" alt=""><figcaption><p>Consent Mode Microsoft</p></figcaption></figure>

If the Transparency & Consent Framework (TCF) is enabled in your setup (which is the default setting), the [Advanced Microsoft UET Consent Mode](https://help.ads.microsoft.com/#apex/ads/en/60186/1) will be loaded. Otherwise, the [Basic Microsoft UET Consent Mode](https://help.ads.microsoft.com/#apex/ads/en/60119/1) will be used.

In short, as soon as you activate the option or select Microsoft Advertising as a partner, **Microsoft UET Consent Mode** is automatically applied!

{% hint style="info" %}
If you disable **TCF support**, the **CMP** will automatically switch to the **basic mode** of **Microsoft UET Consent Mode**.
{% endhint %}

{% hint style="danger" %}
**Note:** This mode **does not cover** **Microsoft Clarity** activities! Please refer to [this page](/en/consent-transmission-standards/microsoft-clarity-consent.md) for consent management for this service.
{% endhint %}


---

# 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://cmp.docs.sirdata.net/en/consent-transmission-standards/microsoft-uet-consent-mode.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.
