Microsoft Ads UET Tag and Cookie Consent: A Simple Guide
September 24, 2026
•
11 min read
Table of contents
back
to the top
Microsoft Ads UET Tag and Cookie Consent: A Simple Guide
Microsoft Ads can be a valuable channel for search, shopping, remarketing, and lead generation. But if you use Microsoft Advertising, the Universal Event Tracking tag is usually part of the setup.
The UET tag helps Microsoft Ads understand what happens after someone clicks an ad. It can track visits, conversions, revenue, form submissions, page views, and audience activity. That data can then support conversion tracking, remarketing, campaign reporting, and campaign optimisation.
But there is one important detail website owners often miss: the UET tag is not just an advertising tool. It is also a tracking technology. That means it needs to be handled properly through your cookie consent setup.
If your website uses Microsoft Ads UET without thinking about consent, the tag may run before the visitor has made a choice. It may set or access advertising cookies too early. It may send data in a way that does not reflect the visitor’s preferences. It may also weaken the quality of your campaign reporting if consent signals are missing or configured incorrectly.
This guide explains what the Microsoft Ads UET tag does, why cookie consent matters, how Microsoft UET Consent Mode works, and how CookiePal can help manage the setup more clearly.
What Is the Microsoft Ads UET Tag?
UET stands for Universal Event Tracking.
It is a tag from Microsoft Advertising that website owners add to their site to measure what users do after interacting with Microsoft Ads. Once installed, the tag can collect information about visits and actions, such as when someone views a page, submits a lead form, completes a purchase, signs up for a newsletter, or reaches a thank-you page.
For advertisers, UET is useful because it helps answer practical campaign questions:
- Which ads are driving conversions?
- Which keywords lead to sign-ups or sales?
- Which campaigns should receive more budget?
- Which visitors should be included in remarketing audiences?
- Which landing pages are performing best?
- What is the cost per conversion?
Without the UET tag, Microsoft Ads has less visibility into what happens after the click. That can make campaign optimisation harder.
But because UET supports advertising measurement and remarketing, it needs to be connected to cookie consent properly.
Why Cookie Consent Matters for Microsoft UET
The UET tag can involve cookies or similar technologies that help Microsoft recognise visits, measure conversions, and support advertising activity.
In many regions, advertising and marketing cookies are not treated the same as strictly necessary cookies. They usually require clear information and, depending on the visitor’s location and applicable rules, consent before they are used.
This means a Microsoft Ads tag should not simply be placed on every page and allowed to run without review. Website owners need to understand when the tag fires, what it stores, what data it sends, and whether it respects the visitor’s cookie choices.
A cookie banner is part of this, but it is not enough by itself. The consent banner must be connected to the tag behaviour. If a visitor rejects marketing cookies, the UET tag should not behave as if consent was granted.
CookiePal’s cookie consent management platform helps websites manage cookie banners, cookie categories, cookie auto-blocking, consent records, recurring scans, and consent-aware tracking. That gives website owners a stronger foundation for Microsoft Ads and other advertising tags.
What Is Microsoft UET Consent Mode?
Microsoft UET Consent Mode allows the UET tag to adjust cookie access based on a user’s consent status.
In simple terms, it helps Microsoft know whether advertising storage is allowed or denied for a visitor. Microsoft uses a parameter called ad_storage to control whether advertising cookies can be stored on the user’s device.
The signal can be:
grantedwhen the user has given consent for advertising storage;deniedwhen the user has not given that consent.
This does not replace your cookie banner. It relies on your consent management setup to collect the visitor’s choice and pass the correct signal to Microsoft.
Microsoft has also said advertisers should provide consent signals for users from the European Economic Area, the UK, and Switzerland. For businesses running Microsoft Ads in these regions, this makes UET Consent Mode an important part of the advertising setup, not a small optional detail.
What Happens If UET Consent Is Set Up Wrong?
A bad UET consent setup can create two problems at the same time: privacy risk and campaign measurement problems.
If the UET tag runs too early, it may set or access advertising cookies before the visitor has made a choice. The banner may appear on the website, but the tracking behaviour may already have happened in the background.
If the UET tag is blocked too aggressively, it may fail to record conversions even when the visitor has accepted marketing cookies. That can make campaigns look weaker than they are.
If consent signals are missing or misconfigured, Microsoft Ads may receive incomplete or inaccurate information. This can affect conversion tracking, remarketing audiences, bidding signals, and performance reporting.
Common signs of a problem include:
- Microsoft Ads conversions dropping unexpectedly;
- remarketing audiences becoming smaller than expected;
- form submissions appearing in the CRM but not in Microsoft Ads;
- different results between Microsoft Ads, GA4, and backend data;
- tags firing before the cookie banner is accepted;
- UET not firing even after marketing consent is granted;
- consent signals showing as missing or inconsistent.
Before blaming the ad campaign, check the consent setup.
Microsoft UET and Google Tag Manager
Many websites install Microsoft UET through Google Tag Manager.
That can be a good approach because GTM gives teams a central place to manage marketing tags. But it can also create confusion if consent is not planned properly.
The UET tag should not fire in the same way for every visitor regardless of consent. Your GTM setup needs to work with your cookie banner and consent categories. The default state should be set correctly before tags run, and the consent state should update after the visitor makes a choice.
For example:
- before consent, Microsoft UET should not store advertising cookies if marketing consent has not been granted;
- after marketing consent is accepted, UET should be allowed to work normally;
- after marketing consent is rejected, UET should respect the denied state;
- if preferences are changed later, the tag behaviour should update accordingly.
This is why consent management and tag management need to be connected. A banner on the page and a GTM container in the background are not enough if they do not communicate properly.
Where Microsoft UET Fits in Your Cookie Categories
For most websites, Microsoft UET belongs in the marketing or advertising category.
That is because it supports advertising measurement, conversion tracking, and remarketing. It helps connect website behaviour to Microsoft Ads activity.
It should not usually be placed under strictly necessary cookies. A website can normally function without Microsoft Ads tracking. The business may want the data, but that does not make the cookie technically necessary for the visitor to use the site.
A clear cookie description might say:
“This cookie helps us measure whether our Microsoft Ads campaigns lead to visits, sign-ups, or purchases.”
Or:
“This cookie helps us understand and improve the performance of our Microsoft advertising campaigns.”
If UET is also used for remarketing, the description should make that clear too.
CookiePal’s cookie policy generator can help create a structured cookie policy that explains cookie purposes, providers, durations, and categories in plain language.
Do Not Forget Landing Pages
Microsoft Ads traffic often goes to landing pages rather than the main homepage.
That creates a common consent gap. The main website may have a proper cookie banner, but campaign landing pages may be built in another platform, copied from an old template, or published on a subdomain. Sometimes the Microsoft UET tag is added directly to the landing page, but the consent banner is missing or not connected.
This can create poor results. A visitor may arrive from a Microsoft ad, the UET tag may fire immediately, and the cookie banner may not control it at all.
Every campaign landing page should be checked before ad spend begins.
Review:
- whether the CookiePal banner appears;
- whether Microsoft UET is present;
- whether UET fires before consent;
- whether UET works after marketing consent is accepted;
- whether UET stays restricted when marketing consent is rejected;
- whether the cookie policy link is available;
- whether the page behaves properly on mobile.
A CookiePal compliance scanner can help identify cookies and trackers active on campaign pages, not just the main website.
Microsoft UET, Remarketing, and Consent
Remarketing is one of the main reasons advertisers use tracking tags.
With Microsoft Ads, remarketing audiences can help you reach people who visited your site, viewed specific pages, started a checkout, submitted a form, or showed interest in a product or service.
But remarketing is also one of the areas where consent matters most.
If a visitor rejects marketing cookies, they should not be treated as if they agreed to be included in advertising audiences. If your setup ignores that choice, the consent experience is not working properly.
A good setup should separate basic website functionality from advertising activity. Necessary cookies keep the site working. Marketing cookies support campaign measurement and remarketing. Users should be able to understand and control that difference.
CookiePal’s banner customisation tools can help create a clear consent banner that fits your website design while still giving visitors meaningful choices.
How to Check Your UET Consent Setup
You do not need to be a developer to run a basic check.
Start by opening your website in a private browser window. Before accepting cookies, check whether the cookie banner appears and whether Microsoft advertising cookies or UET-related requests are already active. Then reject non-essential cookies and confirm that the tag behaviour reflects that choice.
Next, clear cookies, reload the page, accept marketing cookies, and confirm that the UET tag is allowed to run. If you use GTM, test the triggers and consent conditions there as well.
You should also test a real conversion path. Submit a test form, complete a test purchase, visit a thank-you page, or trigger the conversion event that Microsoft Ads is supposed to record.
A simple checklist:
- Scan the website for Microsoft UET and related cookies.
- Confirm UET is categorised as marketing or advertising.
- Check that the banner loads before non-essential tracking.
- Test reject, accept, and manage-preferences flows.
- Confirm the
ad_storagesignal changes correctly. - Test Microsoft Ads conversion tracking after consent.
- Review landing pages and subdomains separately.
- Update the cookie policy if UET is added or changed.
- Re-test after GTM, ad account, or landing-page changes.
This should be part of your campaign launch process, not a one-time setup.
Keep Your Cookie Policy Updated
If you add Microsoft UET to your website, your cookie policy should explain it.
The policy should not just say “we use cookies for marketing”. It should explain the types of cookies used, why they are used, who provides them, how long they last where possible, and how visitors can manage their preferences.
If Microsoft UET is used for conversion tracking, say that. If it is used for remarketing, say that. If it supports campaign optimisation, say that in plain language.
Your privacy policy may also need to explain how advertising and analytics data are used more broadly. CookiePal’s privacy policy generator can help create a clearer privacy policy for websites that collect personal information through forms, ecommerce, accounts, or marketing tools.
Build Microsoft UET Into Your Consent Process
Microsoft Ads UET should not be treated as a small script you add once and forget.
It is part of your advertising measurement system, and it needs to work with your cookie consent process. That means scanning the site, categorising the tag correctly, blocking or adjusting it before consent where required, passing consent signals to Microsoft, testing conversion events, and keeping your policy updated.
The best setup is not just a working UET tag. It is a UET tag that behaves correctly depending on the visitor’s consent choice.
Start with a free CookiePal compliance scan to see what your website is currently loading. Then use CookiePal to manage your cookie banner, marketing cookie preferences, auto-blocking, consent records, cookie policy, and recurring scans as your advertising setup changes.
Microsoft Ads data is only useful if you can trust how it is collected. A proper consent setup helps protect both user privacy and campaign performance.
This article provides general information and is not legal advice. Privacy obligations depend on your website, advertising setup, data practices, audience, and applicable laws.
Explore further

LinkedIn Insight Tag and GDPR: What B2B Teams Need to Know
The LinkedIn Insight Tag is advertising tracking, even on B2B sites. Learn how GDPR applies, when the tag can run, and how to handle retargeting, GTM and landing pages.
September 24, 2026
13 min

TikTok Pixel and Cookie Consent: A Practical Setup Guide
TikTok Pixel is a marketing technology, not a necessary one. Learn where to install it, how advanced matching and Events API affect consent, and what to test.
September 17, 2026
8 min

Meta Conversions API and Consent: What Marketers Need to Get Right
Server-side tracking is still tracking. Learn how to align Meta Pixel and Conversions API with the same consent logic, minimise data, and govern CAPI events.
September 17, 2026
8 min
