> 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/regulations-manager/frameworks/microsoft-consent-mode.md).

# Microsoft Consent Mode

Microsoft Consent Mode is a framework that ensures Microsoft Advertising Universal Event Tracking (UET) tags comply with an end-user's consent choices. When a website visitor indicates their consent choices, Didomi will transmit those decisions and adjust the behavior of your organization's UET tags.&#x20;

* [Consent parameter](#consent-parameter)
* [Microsoft Consent Mode products](#microsoft-consent-mode-products)
* [Basic vs Advanced consent mode](#basic-vs-advanced-consent-mode)

{% hint style="info" %}
[Click here](https://www.didomi.io/blog/microsoft-universal-event-tracking-uet-consent-mode) to learn more about Microsoft Consent Mode on the Didomi blog.&#x20;
{% endhint %}

***

### Consent parameter

Microsoft Advertising is installed on your website via a Universal Event Tracking (UET) tag. Microsoft Consent Mode is set via the `ad_storage` property in the UET tag. The value of this property determines how the UET tag will behave.

<table><thead><tr><th width="160">ad_storage value</th><th>Description</th></tr></thead><tbody><tr><td><code>granted</code></td><td>First and third-party cookies may be read and written for the UET tag. </td></tr><tr><td><code>denied</code></td><td>First-party cookies are not read nor written for the UET tag and third-party cookies are not written. Third-party cookies are read-only for fraud and spam purposes—not for advertising purposes.</td></tr></tbody></table>

### Microsoft Consent Mode products

While Microsoft Consent Mode is supported for Microsoft Advertising, Microsoft Invest, Microsoft Curate, and Microsoft Monetize, be advised that Didomi only supports Microsoft Consent Mode for Microsoft Advertising, including Bing Ads and Microsoft Clarity (which is implemented via the Universal Event Tracking (UET) tag and the other products are implemented via Universal, segment, and conversion pixels).

### Basic vs Advanced consent mode

Microsoft Consent Mode supports two different modes that your organization can use to guide implementation ([basic](/regulations-manager/frameworks/microsoft-consent-mode/microsoft-consent-mode-basic.md) or [advanced](/regulations-manager/frameworks/microsoft-consent-mode/microsoft-consent-mode-advanced.md)). The major difference between these two modes is how end-user consent impacts when and if your UET tags are loaded and the data transmitted to Microsoft Advertising.

<table><thead><tr><th width="180">Feature</th><th width="242">Basic consent mode</th><th>Advanced consent mode</th></tr></thead><tbody><tr><td>Tag loading</td><td>Blocked until the end-user grants consent</td><td>Loads immediately with consent state set to <code>denied</code> by default before the end-user makes a choice</td></tr><tr><td>Data collection</td><td>No data is sent before the end-user grants consent</td><td>If consent is <code>denied</code>, only anonymized data is collected and later aggregated prior to modeling</td></tr><tr><td>Consent status</td><td>Set after end-user grants consent</td><td>Defaults to <code>denied</code> before end-user makes a choice, updates based on end-user choice</td></tr><tr><td>Data modeling</td><td>Generic modeling</td><td>More precise modeling tailored to the advertiser</td></tr></tbody></table>


---

# 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/regulations-manager/frameworks/microsoft-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.
