Set up your bannerConfigure Your ToolsAdvertising

Microsoft Advertising (UET)

How to configure Microsoft Advertising (UET) at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics, Receive personalised marketing offers, Customise online ads

Overview

This guide explains how to implement different privacy configurations for Microsoft Advertising and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. This guide covers the Microsoft Advertising Universal Event Tracking (UET) tag on a website, used for conversion tracking (Bing Conversion) and remarketing (Bing Remarketing, Bing Remarketing Conversion), with UET Consent Mode.

Out of scope. Customer Match list uploads (separate data processing terms in which Microsoft is processor); Microsoft Clarity (separate guide).

What the service does in this scope. The UET tag sends page and event data to Microsoft Advertising to attribute conversions to ads and to build remarketing audiences. It uses the first-party cookies _uetsid (session ID) and _uetvid (visitor ID) and Microsoft's third-party MUID cookie. Consent is passed through the ad_storage property.

Legal role. Under the Microsoft Advertising terms, advertiser and Microsoft are independent controllers for processing other than Customer Match uploads. Microsoft requires advertisers to have a valid basis, such as notice and consent, to collect personal information on their sites.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskUET loads after consent and is used for conversion tracking only; no remarketing lists; enhanced conversions off.
Configuration B — Higher riskAs A, plus remarketing / dynamic remarketing audiences and enhanced conversions (hashed customer data).

No configuration without prior consent. Microsoft enforces UET Consent Mode for the EEA, UK and Switzerland; if ad_storage is not set, UET defaults to granted outside those regions. With ad_storage: denied, UET still sends requests without cookies. Microsoft does not document this as a consent-free configuration, so in both configurations Consenter blocks the tag until consent and sets ad_storage explicitly.

ActionConfiguration A — Medium riskConfiguration B — Higher risk
Tag loadingBlocked until consentBlocked until consent
ad_storage default / updatedenied by default; granted after consentdenied by default; granted after consent
Remarketing audiencesNot usedUsed
Enhanced conversionsOffOn
Consenter Manager entriesOne entry (Microsoft as Individual Controller)One entry (Microsoft as Individual Controller)

Step 1 — Configure Microsoft Advertising

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics; Receive personalised marketing offers; Customise online ads
2Consent defaultwindow.uetq.push('consent', 'default', {'ad_storage': 'denied'}) before the UET tagdenieddenied
3Consent updatewindow.uetq.push('consent', 'update', {'ad_storage': 'granted'}) from the Consenter callback, on every pageAfter consentAfter consent
4Tag loadingConsenter script blockingBlocked until consentBlocked until consent
5Remarketing / dynamic remarketingMicrosoft Advertising > Audiences (remarketing lists linked to the UET tag)No lists createdLists created
6Enhanced conversionsUET tag settings / conversion goal settingsOffOn
7Cookie lifetimes and Microsoft retentionNot configurable in the accountFixedFixed

Configuration A — Medium risk

  • Intended use: measure which Microsoft ads lead to conversions.
  • Resulting processing: page and conversion events with _uetsid, _uetvid and MUID after consent.
  • Why medium risk: cross-site Microsoft identifier, but no audience building by the operator.

Configuration B — Higher risk

  • Intended use: conversion tracking plus retargeting of visitors with Microsoft ads.
  • Resulting processing: as A, plus inclusion in remarketing lists and, with enhanced conversions, hashed customer data such as email addresses.
  • Why higher risk: visitor behaviour is used to target ads across Microsoft's network; direct identifiers (hashed) are transmitted.

Step 2 — Map the configuration in the Consenter Manager

Processing location (applies to all entries). EU advertisers contract with Microsoft Ireland Operations Limited; Microsoft Corporation is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential processing and access location.

Configuration A — Medium risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesSupport marketing analyticsConversion attribution.
Tracking methodThird party tracking (crosssession, cross-website)MUID recognises browsers across Microsoft sites; _uetvid persists across sessions.
IdentifierDevice identifiers, IP addressUET cookies.
Data categoriesBrowsing and interaction data, Device identifiers, Device characteristics, IP address, Privacy choices, e-commerce Activity (if revenue is sent)The ad_storage consent state is transmitted with each UET request.
Legal role of data recipientIndividual ControllerIndependent controllers.
Personalisation modelNo personalisationNo audiences built.
Maximum storage durationNot documentedCookie lifetimes per Microsoft's UET cookie list; Microsoft's server-side retention is not documented.
Processing locationEU contracting entity; United States as potential processing and access locationSee note above.

Configuration B — Higher risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesSupport marketing analytics, Receive personalised marketing offers, Customise online adsRemarketing.
Tracking methodThird party tracking (crosssession, cross-website)As A.
IdentifierDevice identifiers, IP address, Direct identifierEnhanced conversions send hashed customer data.
Data categoriesBrowsing and interaction data, Device identifiers, Device characteristics, IP address, Privacy choices, e-commerce Activity, direct identifier, Users' profilesRemarketing lists are behavioural profiles.
Legal role of data recipientIndividual Controller—
Personalisation modelProfile basedAds selected on the basis of individual site behaviour.
Maximum storage durationNot documented—
Processing locationAs ASee note above.

Privacy-policy follow-up

  • Microsoft as independent controller; conversion tracking and, for B, remarketing and enhanced conversions; UET cookies and MUID; consent under ePrivacy / TDDDG and the GDPR legal basis stated separately; US transfer and potential access by US authorities.

Verification checklist

  • Before consent: no request to bat.bing.com; no _uetsid, _uetvid, MUID.
  • After consent: requests carry the granted consent state (UET Tag Helper).
  • A: no remarketing lists linked to the tag; enhanced conversions off.
  • Withdrawal: ad_storage updated to denied on all subsequent pages.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page