Microsoft Advertising's Universal Event Tracking (UET) tag is deployed across millions of websites to measure Bing Ads conversions and enable audience targeting for Microsoft's ad network. Despite its breadth, the UET tag is one of the most frequently miscategorized or entirely absent from consent management platform configurations. Companies that run Bing Ads campaigns often discover that their UET tag fires in reject states when Lokker validates their full tracker inventory.
Marketing and Analytics
Microsoft Advertising (formerly Bing Ads) is Microsoft's search and audience advertising platform. The UET (Universal Event Tracking) tag collects conversion events, enables remarketing audiences, and powers audience matching against Microsoft's first-party data.
Trademark
Microsoft Advertising is a trademark of Microsoft Corporation. Lokker is not affiliated with or endorsed by Microsoft Corporation.
Risk and failure modes
OneTrust, CookieBot, and other CMP platforms require teams to manually assign consent categories to detected scripts. The UET tag is often miscategorized as analytics rather than advertising, placed in the wrong consent bucket, or missed entirely during initial CMP setup.
The UET tag is an advertising and targeting pixel. Sites that categorize it under analytics may honor analytics consent while still firing the UET tag after a reject on advertising, creating a gap between the user's choice and what actually runs.
UET tags are frequently deployed through Google Tag Manager or Tealium rather than as direct page scripts. Tags deployed through a container may not be caught by the CMP's automated scanner, leaving them ungated.
The UET tag builds remarketing audiences by sending visitor data to Microsoft's ad platform. If it fires in reject or no-consent states, Microsoft receives visitor identifiers and behavior that feeds ad targeting.
Microsoft Advertising accounts often have Microsoft Clarity (session replay) enabled alongside the UET tag. If both share a script or a tag manager rule, a consent gap in the UET tag may also expose Clarity session recording.
Consent and configuration
A consent category labeled "Microsoft Advertising" in a CMP dashboard does not guarantee the UET tag is blocked in reject state. Network-layer validation is necessary to confirm the category assignment is enforced and the tag does not fire through a tag manager route that bypasses the CMP.
UET tags deployed through tag managers need consent gating applied at both the CMP level and within the tag manager container.
Advertising and targeting pixels must be confirmed to stop firing when the visitor rejects advertising cookies, not only analytics.
Microsoft Clarity, if co-deployed with UET, requires its own consent validation as a session replay tool with separate data collection scope.
GPC signals should prevent UET from setting advertising cookies in California and other states where GPC creates opt-out obligations for data sale and sharing.
Regional compliance
European DPAs have repeatedly ruled against companies that fired advertising tracking pixels before or without consent. California law as amended by the CPRA specifically addresses the sale and sharing of personal data with advertising platforms such as Microsoft Advertising, with the California Privacy Protection Agency (CPPA) enforcing these obligations. The UET tag's remarketing list function qualifies as data sharing for cross-context behavioral advertising under the CPRA, triggering opt-out and GPC obligations.
How Lokker helps
Lokker tests whether the UET tag fires in pre-consent, reject, and GPC states, identifies whether it is deployed through tag managers that bypass CMP gating, and confirms that audience list building is blocked in unauthorized states.
Consent Validator runs automated browser flows and captures whether the UET tag sends conversion or audience events in no-interaction, reject, and GPC states.
Explore Consent ValidatorPrivacy Edge detects UET tag deployments whether they are direct script embeds or loaded through tag managers, and surfaces the consent risk for each deployment route.
Explore Privacy EdgeGuardian intercepts UET requests at the network layer so audience building and conversion tracking cannot occur outside an authorized consent state, regardless of how the tag is deployed.
Explore GuardianExplore Lokker
Each product links to its full details so you can explore features, view a demo, and understand how it applies to your Microsoft Advertising deployment.
Validation
Tests UET tag firing across all consent states including reject and GPC.
Explore Consent ValidatorIntelligence
Detects UET tag deployments across the entire web estate, including tag-manager-delivered instances.
Explore Privacy EdgeEnforcement
Blocks UET network requests before audience data reaches Microsoft's ad platform.
Explore GuardianMarketing and Analytics
Before you deploy
Marketing teams often evaluate tools on performance and features. These privacy questions are worth settling before the script goes live, because fixing them after a complaint is significantly more expensive.
Is your UET tag deployed through a tag manager, and if so, does the tag manager container have consent gating that matches your CMP categories?
Have you confirmed the UET tag is categorized under advertising and targeting rather than analytics in your CMP?
Does your configuration prevent the UET tag from building remarketing audiences in reject and GPC states?
If you also use Microsoft Clarity, have you validated that both tools are gated with appropriate consent separately?
Next step
Lokker runs automated browser-level consent flows and scans the network layer to confirm whether Microsoft Advertising fires in states where it should not.