Omea Consent · Guides

Microsoft UET consent mode for WordPress sites

Send Microsoft Advertising UET consent mode (ad_storage) from your WordPress cookie banner – also for UET tags loaded through GTM or another plugin.

Updated · Omea Consent 1.0.2

On this page
  1. What Omea Consent sends to UET
  2. Turn it on or off
  3. With Omea Consent Pro
  4. Withdrawing consent

Microsoft Advertising’s Universal Event Tracking (UET) tag supports a consent mode much like Google’s: the page tells UET whether ad_storage is granted, and UET only uses cookies when it is. Omea Consent sends that signal from your cookie banner automatically.

  1. Before a choice, Omea sets the UET default to denied:

    window.uetq = window.uetq || [];
    window.uetq.push('consent', 'default', { ad_storage: 'denied' });
    
  2. On every choice, it sends an update where ad_storage follows the Marketing category – granted if the visitor accepted Marketing, denied if not.

It works for UET tags from anywhere – Google Tag Manager, another plugin, your theme or Omea’s Scripts. See Microsoft’s UET consent mode guide for how UET behaves with each state.

Turn it on or off

The signal is on by default. You’ll find it under Omea Consent › Settings › Advanced as Microsoft consent signals – the same switch also sends Microsoft Clarity’s consent.

Pro’s Microsoft Advertising (UET) integration adds the UET tag for you from its UET tag ID – no code. You choose how it loads:

  • After Marketing consent (recommended) – the tag doesn’t load until the visitor accepts Marketing.
  • Own consent mode – the tag loads straight away with UET’s consent mode holding cookies and events until the visitor agrees. When Microsoft consent signals are on, the updates come from them.

The trade-offs are explained in Own consent mode for Meta, TikTok and UET.

If a visitor withdraws Marketing, Omea reloads the page and deletes UET’s _uet… cookies along with the other marketing cookies.