Ketch and Microsoft Ads

Restrict tracking across seven connected Microsoft products the moment someone opts out, with one honest limitation worth knowing upfront.

Microsoft Ads

About Microsoft Ads

Microsoft Ads (Bing Ads) powers advertising across the Bing network, which includes Bing, Yahoo, and AOL search, and Bing itself is the default search engine on Windows PCs and powers search behind Cortana, Siri, and Kindle. Consent Orchestration here isn't limited to one product; it extends across Microsoft's broader advertising and remarketing suite.

Ketch connects to Microsoft Ads to set consent state directly on Microsoft's own Universal Event Tracking (UET) tag, restricting cookies and data sharing based on real consent choices.

Capabilities

How Ketch works with Microsoft Ads

The Ketch Microsoft Ads integration covers Consent Orchestration.Enabling this integration orchestrates consent across seven Microsoft products at once: Microsoft Advertising, Conversion Tracking, Advertising Remarketing, Remarketing Conversion, Remarketing, Clarity, and Omnichannel.

Consent Orchestration

The Ketch tag restricts data sharing by setting UET Consent Mode through a property on the Universal Event Tracking tag (`uetq.ad_storage`), and separately restricts the storing and setting of first- and third-party cookies based on consent settings. Ketch also sets a Microsoft-recommended cookie variable (`_uetmsdns`) to 1 when someone opts out, which signals to Microsoft that this specific person has opted out so Microsoft can limit tracking and ad display accordingly. That variable lives at the session and browser level, so if cookies and cache are cleared, the preference isn't retained and needs to be set again.

With Ketch, teams can

  • Restrict UET-based tracking and cookie storage across seven Microsoft products from one consent connection
  • Apply Microsoft's own recommended opt-out signal (`_uetmsdns`) so Microsoft's systems recognize the opt-out and act on it
  • Know upfront that rights fulfillment (export or deletion) isn't available for Microsoft Ads, rather than assuming it's covered when it isn't

The gap

The problem this integration solves

Microsoft's advertising surface spans multiple named products under one umbrella, and consent has to reach all of them consistently, not just the one product a team happened to configure directly:

01. A consent choice that only reaches one Microsoft product (say, Advertising) while missing Clarity or Remarketing leaves a real gap

02. Microsoft's own recommended opt-out cookie is session-scoped, which means a cleared browser silently reverts someone to a default tracking state unless that's understood upfront

03. Teams sometimes assume every advertising integration includes rights fulfillment by default, which isn't true here and needs to be planned around rather than discovered during an audit

Why Ketch

Why teams choose Ketch for Microsoft Ads privacy compliance

Permissioning infrastructure that governs Microsoft Ads the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.

  • Covers Microsoft's full advertising surface, not just one product

    Consent reaches Advertising, Conversion Tracking, Remarketing (in three forms), Clarity, and Omnichannel from a single connection.

  • Uses Microsoft's own recommended mechanism

    The `_uetmsdns` cookie signal is the variable Microsoft itself recommends for communicating an opt-out, rather than a workaround Microsoft's systems might not fully honor.

Questions about the Microsoft Ads integration

Integrations

Pre-built APIs with 1,000+ systems, apps, and models

Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.

Browse All Integrations

See Microsoft Ads permissioning running end to end

Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Microsoft Ads yourself.

Get Started Free

Get started in less than 5 min