Microsoft Ads (Bing) Retargeting From QR Code Scans: UET Tag Setup Guide

To fire Microsoft Ads' UET tag on every QR scan, find your UET Tag ID inside Microsoft Advertising (Tools → Conversion Tracking → UET Tags), then paste it into SMLLR's Settings → Tracking Pixels, in the field literally labeled 'Microsoft Ads UET Tag ID' — either as an account-wide default or as an override on one specific QR code. Once set, SMLLR's redirect page fires the UET tag's automatic pageLoad event on every scan of that QR code, feeding Microsoft Ads retargeting the same way a website visit with the UET tag installed would. This requires the Pro plan (₹4,999/month) or above.

Inside Microsoft Advertising, UET Tags live under Tools → Conversion Tracking → UET Tags — a standard location in the Microsoft Advertising interface, not something specific to this integration. Each UET Tag has its own numeric Tag ID, visible on the tag's details page; if you don't already have a UET Tag created, Microsoft Advertising walks you through generating one from the same screen. If your account runs multiple UET Tags (common for agencies managing several clients, or businesses with more than one advertising account), make sure you're copying the ID for the specific tag whose conversion tracking and remarketing lists you want QR scans to feed.

In SMLLR, go to Settings → Tracking Pixels and paste the Tag ID into the field labeled 'Microsoft Ads UET Tag ID.' The in-product helper text describes exactly what happens next: it 'fires the UET tag's automatic page-view event on every scan for Microsoft Ads retargeting.' Set it once here and every QR code in the account inherits it by default. If a specific campaign or product line needs a different UET Tag — a separate ad account for one franchise location, for instance — open that individual QR code's settings and override just the Microsoft Ads field there, without touching the account-wide default used by everything else.

The event fires automatically on SMLLR's own redirect page, in the moment between the scan and the browser landing on the actual destination URL — there's no separate 'enable tracking' step to repeat per campaign once the Tag ID is set. It's the standard UET automatic pageLoad event, the same one a website visit fires with the tag installed directly on a page; SMLLR isn't sending anything custom or QR-specific to Microsoft's side. There's no lead-capture form or consent checkbox involved in firing it — the same distinction that applies across all of SMLLR's tracking pixels, separate from features like Meta Sync that only move consented Lead Hub contacts.

Microsoft Ads UET is one of five platforms SMLLR's Tracking Pixels feature supports — Meta Pixel, Google Ads, GA4, LinkedIn Insight Tag, and Microsoft Ads UET Tag, all configurable from the same Settings → Tracking Pixels screen, all Pro plan and above. If you're setting up more than just Microsoft Ads, QR Code Retargeting: Fire Meta Pixel, Google Ads & GA4 on Every Scan covers all five platforms together, including how Google Ads and GA4 share a single loader script. For the full support reference on the feature, see /support/tracking-pixels/what-are-tracking-pixels.

The Microsoft Ads UET Tag field, along with the other four tracking pixel platforms, is available on SMLLR's Pro plan (₹4,999/month) and above — no separate per-platform charge, and no higher tier required to also set per-QR overrides.