Microsoft Ads (Bing) Conversion Tracking with GTM: UET Tag, Consent and Revenue
Microsoft Advertising (formerly Bing Ads) is often the cheapest search traffic in an account, especially for B2B and older audiences. But many advertisers import their Google Ads campaigns, add the UET tag once, and never check whether conversions are counted correctly.
This guide walks through a clean Microsoft Ads conversion tracking setup in Google Tag Manager: the UET tag, conversion goals, revenue, consent and testing.
How Microsoft Ads tracking works
Microsoft uses one site-wide tag called UET (Universal Event Tracking). You install it once on every page. Conversions are then defined as goals in Microsoft Advertising, which match either:
- Destination URL goals: a visit to a page (for example
/thank-you/). - Event goals: a custom event your site sends (for example a
purchaseevent with revenue).
Event goals are more reliable for forms and purchases, for the same reason as in Google Ads: thank-you pages can be reloaded or visited without converting.
Step 1: Create the UET tag
In Microsoft Advertising, go to Tools → UET tag and create a tag (one per website is usually enough). Copy the tag ID.
Make sure auto-tagging of Microsoft Click ID (MSCLKID) is turned on in your account settings. You need it for offline conversions later.
Step 2: Add the UET tag in Google Tag Manager
- In GTM, create a new tag and choose Microsoft Advertising Universal Event Tracking (older containers call it “Bing Ads Universal Event Tracking”).
- Paste your UET tag ID. Tip: store it in a Constant variable so every Microsoft tag uses the same ID.
- Set the trigger to All Pages (or Initialization – All Pages if you use Consent Mode).
- Publish, and confirm the tag fires once per page.
Step 3: Create conversion goals
Go to Conversions → Conversion goals and create a goal per action:
| Action | Goal type | Notes |
|---|---|---|
| Lead form | Event (action = submit_lead_form or similar) | Count one per click for leads |
| Purchase | Event (action = purchase) with variable revenue | Count all for purchases |
| Phone click | Event (action = phone_click) | Optional micro-conversion |
Use the same event names in GTM that you define in the goals; they must match exactly.
Step 4: Send events with GTM
For each conversion, create a second Microsoft Advertising UET tag in GTM with Event tracking, or a Custom HTML tag that pushes to the UET queue:
<script>
window.uetq = window.uetq || [];
window.uetq.push('event', 'purchase', {
revenue_value: {{DLV - ecommerce.value}},
currency: {{DLV - ecommerce.currency}}
});
</script>
Fire it on the same trigger as your GA4 purchase or lead event (for example a custom purchase data layer event), not on a page view. If your store doesn’t have a clean ecommerce data layer yet, the Data Layer Spec Generator gives you the exact structure.
Step 5: Add UET Consent Mode
Microsoft has its own consent mode for UET, based on ad_storage. Microsoft requires a consent signal for visitors in the EEA, the UK and Switzerland, and it is good practice everywhere.
Set a default before the UET tag loads, then update it when the visitor chooses:
<script>
window.uetq = window.uetq || [];
window.uetq.push('consent', 'default', { ad_storage: 'denied' });
</script>
<script>
window.uetq = window.uetq || [];
window.uetq.push('consent', 'update', { ad_storage: 'granted' });
</script>
Many consent platforms (CMPs) can send this signal for you. Check that yours supports Microsoft UET, and that the default fires before any Microsoft tag. You can see how Google’s equivalent signals behave in the Consent Mode v2 sandbox.
Step 6: Enhanced conversions (optional)
Like Google, Microsoft supports enhanced conversions: sending the customer’s email or phone number with the conversion to improve matching. In UET this is set with a pid object before the conversion event:
<script>
window.uetq = window.uetq || [];
window.uetq.push('set', { pid: { em: {{DLV - customer email}}, ph: {{DLV - customer phone}} } });
</script>
Turn on enhanced conversions in your Microsoft Advertising account settings, and only send this data for visitors who have consented. Microsoft hashes the values; if you hash them yourself, normalise first (lowercase email, phone with country code). The Customer Data Hasher shows the normalised and hashed values.
Step 7: Test your setup
- Install the UET Tag Helper browser extension from Microsoft.
- Load your site and check that the UET tag fires once per page with the correct ID.
- Submit a test lead or order and confirm the custom event appears with the right action name and revenue.
- In Microsoft Advertising, the goal’s tag status should change to “Tag active” and later “Recording conversions” (this can take a few hours).
Common mistakes
- Goals imported from Google Ads but never verified. An import copies settings, not tracking. Each goal still needs a matching UET event.
- Destination URL goals on reloadable pages, which count the same lead several times.
- Revenue sent as text (“$99.00”) instead of a number (
99). - No consent default, so UET loads before the visitor has chosen.
- Event names that don’t match the goal definition exactly (
Purchasevspurchase).
Need help?
Microsoft Ads tracking is quick to set up badly and easy to forget. If you want it set up cleanly alongside Google Ads and GA4, see my Google Ads and conversion tracking services or book a free tracking audit.
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.


