Bing Ads Conversion Tracking Setup 2026 Microsoft UET Tag, GTM, Consent Mode & Server-Side

Quick Answer

Bing Ads conversion tracking (now Microsoft Advertising) works through the UET tag, Microsoft’s Universal Event Tracking script. Create a UET tag and conversion goals in Microsoft Advertising, then install the tag through Google Tag Manager: one base tag on every page and one custom event tag for each conversion, such as a lead or purchase, with its value. Send consent signals for visitors from the EEA, UK and Switzerland. For better accuracy, add server-side tracking with a server GTM container and the Microsoft UET Conversions API, using the same event ID on both sides. Finally, test everything with the UET Tag Helper and GTM Preview.

Key Takeaways

• One base tag, many goals: the UET base tag loads on every page, and each conversion goal reads from it.
• Custom events beat thank-you URLs: event goals fire on the real action, even when there is no separate thank-you page.
• Consent is required: since May 5, 2025 Microsoft expects UET consent signals for visitors from the EEA, UK and Switzerland.
• Server-side is now possible: Microsoft published its UET Conversions API documentation in 2026, but access is per account, so check before you plan around it.
• Deduplicate with an event ID: when the browser and server both send a conversion, the same event ID stops Microsoft counting it twice.
• Test before you trust: the UET Tag Helper and GTM Preview show whether the right event fires with the right value.

Introduction: Your Bing Ads Budget Is Working Blind

Microsoft Advertising often brings cheaper clicks than Google Ads, from an audience that is older, more desktop-heavy and often ready to buy. Many accounts still treat it as an afterthought.

Then the numbers come in. Microsoft Ads shows ten conversions. The CRM shows thirty leads from Bing. Or the opposite: Microsoft reports conversions that never reached the sales team.

If Microsoft Ads cannot see your real conversions, it cannot bid for more of them.

Smart bidding strategies like Maximize conversions and Target CPA learn from the conversion data you send. When that data is missing, duplicated or attached to the wrong action, you pay for clicks the algorithm cannot judge.

In this guide I will show you the three-milestone process I use for Microsoft Ads tracking: audit and tracking map, implementation through Google Tag Manager and server-side tracking, and QA with a clean handover.

Why Bing Ads Tracking Breaks

What Is the Microsoft UET Tag?

The UET tag (Universal Event Tracking) is a small script from Microsoft Advertising that records what visitors do on your website after they click your ads. It powers conversion tracking, remarketing audiences and automated bidding.

Think of it like a receptionist at your front door. The base tag notes every visitor who walks in. Custom events are the receptionist writing down “this visitor booked a call” or “this visitor bought something worth $120”. Microsoft Ads reads that notebook to decide who to show your ads to next.

A conversion goal is the rule in Microsoft Ads that decides which of those notes count as a conversion. The tag collects; the goal counts.

Prerequisites & Setup Checklist

• Microsoft Advertising: Standard or Super Admin access to the ad account, so you can create UET tags and conversion goals.
• Google Tag Manager: publish rights on the Web container, plus a Server container for the server-side part.
• Server hosting: a tagging server on Stape Global or Stape Europe.
• Consent banner: a cookie banner that can send consent choices to Google Tag Manager.
• Browser tools: Chrome with the Microsoft UET Tag Helper extension.
• A conversion list: which actions count as leads or sales, and what each one is worth.

For a quick first look at what your site loads today, run it through my free tracking audit tool.

Video Tutorial Walkthrough

Prefer to watch? In this short video I explain the three milestones I follow to fix Bing Ads conversion tracking: audit, implementation with GTM and server-side tracking, and QA.

Step-by-Step Implementation Guide

The work follows three milestones. Milestone 1 is the audit and tracking map (Phase 1). Milestone 2 is implementation (Phases 2 to 6). Milestone 3 is QA and handover (Phase 7).

Phase 1: Audit the Account and Build a Tracking Map

1. In Microsoft Advertising, open Conversions → UET tag and check each tag’s status. Note which tag ID the account uses.
2. Open Conversions → Conversion goals and list every goal, its type, its status and whether it is included in the Conversions column.
3. On the website, open the UET Tag Helper on key pages: home, a landing page, the form page and the thank-you or checkout page.
4. Look for duplicate UET tags, for example one hard-coded in the theme and another in GTM.
5. Write the tracking map: each conversion, how it is triggered, its value, and which goal should count it.

My free measurement plan generator helps you write this map in a few minutes.

Phase 2: Create the UET Tag and Conversion Goals

1. If the account has no tag, go to Conversions → UET tag → Create, name it after the website, and copy the Tag ID.
2. Go to Conversions → Conversion goals → Create and choose Website.
3. Pick the goal category, such as Purchase or Submit lead form, and choose Event as the goal type.
4. Set the event condition. I match on Action equals a clear name, for example submit_lead_form or purchase.
5. Set the revenue: a fixed value for leads, or “may vary” for purchases so the tag can pass the real order value.
6. Choose the Count (unique for leads, all for purchases), the conversion window (up to 90 days), and select your UET tag.

Phase 3: Install the UET Base Tag in Google Tag Manager

1. Remove any hard-coded UET script you found in Phase 1, so the tag loads only once.
2. In your Web container, go to Tags → New and choose the Microsoft Advertising Universal Event Tracking tag type.
3. Paste your UET Tag ID.
4. Set the trigger to All Pages and name it UET – Base – All Pages.
5. Save, then test in Preview mode before you publish.

Phase 4: Track Leads and Purchases with Custom Events

1. Create a trigger that fires only on a successful conversion, for example a generate_lead or purchase data layer event. Avoid plain button clicks, which fire even when the form fails.
2. Create a new tag with the same Microsoft Advertising Universal Event Tracking type and choose a custom conversion event.
3. Set the Event Action to exactly the name in your goal, for example submit_lead_form.
4. For purchases, map the revenue and currency from Data Layer Variables such as ecommerce.value and ecommerce.currency.
5. Attach the trigger, name the tag UET – Lead or UET – Purchase, and test.

If your forms are hard to track, my free form tracking listener generator and free data layer generator create the listener code for you.

Phase 5: Send Consent Signals to UET

Microsoft Advertising asked advertisers to send consent signals with UET by May 5, 2025 for visitors from the EEA, the UK and Switzerland. UET reads one setting, ad_storage, which is either granted or denied.

1. In GTM, create a Custom HTML tag with the first part of the code below, wrapped in <script> tags, on the Consent Initialization – All Pages trigger.
2. Call the update function when the visitor accepts or rejects marketing cookies. Many consent platforms can do this for you through a built-in Microsoft UET integration.
3. Check in Preview mode that the default fires before the UET base tag.

// 1. Consent default: fire this before the UET base tag
//    (in GTM, use a Custom HTML tag on the Consent Initialization – All Pages trigger)
window.uetq = window.uetq || [];
window.uetq.push('consent', 'default', {
  'ad_storage': 'denied'
});

// 2. Consent update: call this when the visitor accepts or rejects marketing cookies
function updateUetConsent(granted) {
  window.uetq = window.uetq || [];
  window.uetq.push('consent', 'update', {
    'ad_storage': granted ? 'granted' : 'denied'
  });
}

Use only one consent method. If your consent platform already sends UET consent, do not add this code as well. Test your banner with my free Consent Mode checker.

Phase 6: Add Server-Side Tracking for Microsoft Ads

Browser tags lose data to ad blockers and to Safari’s limits on cookies. A server GTM container on your own subdomain sends events from a server you control. For Microsoft Ads, the server sends conversions through the UET Conversions API.

Check access first. Microsoft published the Conversions API documentation in 2026, but access is enabled per account. You get the authorization token in the UET tag settings under the Use Conversions API option. If you do not see it, ask your Microsoft account manager or support.

1. Create a Server container in GTM and host it on Stape with a custom subdomain such as sgtm.yourdomain.com.
2. Send web events to the server container through your GA4 tag or a data tag.
3. In the Server container, add the Microsoft UET Conversion API tag from the template gallery.
4. Enter the UET Tag ID, the authorization token and your Microsoft customer ID.
5. Pass at least one identifier, such as the Microsoft click ID (msclkid), hashed email or hashed phone, and pass the visitor’s consent state.
6. Add the same event ID to the web UET tag and the server tag, so Microsoft keeps one conversion when both arrive.

Server-side tracking does not track visitors who declined consent. It makes the data you are allowed to collect arrive more reliably. See my server-side tracking service if you want this built for you.

Phase 7: Test with UET Tag Helper and Hand Over

1. Open GTM Preview, complete a test conversion, and confirm the base tag and the custom event tag both fired.
2. Open the UET Tag Helper on the same page. It should show your Tag ID once and the custom event with the right action and value.
3. In Microsoft Advertising, check the UET tag status and the conversion goal status. Verification can take up to 24 hours.
4. For server events, check the server container Preview and confirm the Conversions API tag returned success.
5. Write a short handover note: the tracking map, every tag and trigger, the goal settings and how to test again.

The Full Data Flow at a Glance

Testing & Validation Workflow

1. UET Tag Helper. One tag ID per page, no errors.
2. GTM Preview. The base tag on every page, the event tag only on real conversions.
3. Consent. With the banner rejected, confirm ad_storage is denied.
4. Values. Confirm the revenue and currency on a real test purchase.
5. Server Preview. The Conversions API tag returns success with an event ID.
6. Microsoft Ads. Goal status shows as recording conversions after a day or two.
7. CRM check. After a week, compare Microsoft conversions with real leads or orders from Bing traffic.

Troubleshooting Common Mistakes

Mistake 1: The goal says “No recent conversions”

The Problem: the tag is active, but the goal records nothing.

The Cause: the Event Action in GTM does not match the goal condition exactly, for example submit_lead versus submit_lead_form.

The Solution: copy the action name from the goal and paste it into the tag. Matching is exact.

Mistake 2: Conversions are doubled

The Problem: Microsoft reports about twice as many leads as the CRM.

The Cause: two UET tags on the page, or browser and server events without a shared event ID.

The Solution: keep one base tag and add the same event ID to the web and server conversions.

Mistake 3: Conversions fire on failed form submits

The Problem: conversions appear, but many have no matching lead.

The Cause: the trigger is a button click, not a successful submission.

The Solution: trigger on a success event from the form or a thank-you state.

Mistake 4: Purchase revenue is always the same

The Problem: every order shows the default value.

The Cause: the goal uses a fixed value, or the revenue field in the tag is empty.

The Solution: set the goal revenue to “may vary” and map the order value from the data layer.

Mistake 5: Very little data from European visitors

The Problem: conversions from the UK and EU drop sharply.

The Cause: no consent signal, or a default that never updates after the visitor accepts.

The Solution: set the default before the base tag and call the update when the visitor chooses.

What to Set Up Next

• Track offline sales. Store the msclkid with each lead and upload closed deals. See my offline conversion tracking services.
• Fix Google Ads too. Read how to fix Google Ads conversion tracking for lead forms and calls.
• Go server-side everywhere. Follow the server-side tracking masterclass.
• Estimate what you are losing. Try the free tracking loss calculator.

If you want this done for your account, see my work as an attribution and server-side tracking specialist.

Conclusion

Microsoft Advertising can be one of your most profitable channels, but only if it can see what its clicks produce. Broken or duplicated tracking turns smart bidding into guesswork.

Your next three moves are clear. First, audit the UET tag and goals and write a tracking map. Second, install the base tag and custom event tags through GTM, with consent signals and, where your account has access, the server-side Conversions API. Third, test with the UET Tag Helper and GTM Preview and document the setup.

Clean conversions in, better bids out.

Summary by MD Niamul

Bing Ads conversion tracking in Microsoft Advertising runs on the UET tag. Start by auditing the account’s UET tag and conversion goals and writing a tracking map of each conversion, its trigger and its value. Create event-based conversion goals under Conversions, Conversion goals, then install one UET base tag on all pages through Google Tag Manager and one custom conversion tag per goal with an Event Action that matches the goal exactly. Send ad_storage consent signals, required since May 2025 for visitors from the EEA, UK and Switzerland. Where the account has access, add server-side tracking with a server GTM container on Stape and the Microsoft UET Conversion API tag, sharing one event ID to prevent double counting. Test with GTM Preview and the UET Tag Helper, then document the setup.