Check if the Microsoft UET tag (Bing Ads) is visible on your website

The Microsoft UET tag has the same deceptive health signal every tag has: the base bat.js snippet is on the page, so a scan sees it, and it feels like tracking is handled. But the base tag loading and a specific conversion goal actually firing are two different things. The base tag just initializes the uetq queue and powers remarketing — a page can carry it perfectly while the purchase or signup goal it should record never fires on the real action.

Goals fail to fire for reasons that leave no visible trace. A goal was set up in Microsoft Advertising but the uetq event it listens for was never wired on the site. A consent banner blocks the tag until the visitor accepts. The tag was removed in a migration and never re-added. Or a single-page-app route change never re-triggers the event. The base tag keeps loading, the page looks normal, and the goal quietly stays dormant while budget runs.

The free check works at the visible layer: it looks for whether a Microsoft UET tag signal appears present on the public page and flags the lead and conversion actions that usually carry a UET goal for review. It does not open Microsoft Advertising or confirm a goal is recorded — it tells you the tag appears to be there and where the conversions worth confirming live.

Microsoft Advertising reaches a valuable search audience, so a conversion gap quietly wastes budget the same way a broken Google Ads tag does. Yet a visible UET tag says nothing about whether goals are counted: the base tag can be present on every page while the specific goal never fires on the real event, or fires without the value it should carry, or was never mapped as a conversion goal in the account.

From the page — and from a simple presence check — it all looks the same. A visible tag is not the same as a counted conversion, and that gap is exactly what lets a Microsoft Advertising account look tracked while its reporting quietly drifts.

The free check works at the visible layer: it looks for whether a Microsoft UET tag appears present and which conversion-worthy actions are visible on the public page, then flags them for review. It does not connect to Microsoft Advertising, read the goals, or confirm anything is counted — those need the account with UET Tag Helper. Naming that limit honestly is the point.

The usual way to verify the Microsoft UET tag is from inside the tooling: open Microsoft Advertising or run the UET Tag Helper browser extension, recreate the journey, and watch the tag and goals register — but that needs account access and walks one page at a time from the machine you are on.

TrackCanary takes the opposite approach for the first look. Paste a public URL — no login, no install, no account access — and the check reviews whether a Microsoft UET tag appears present alongside the forms, calls, and lead paths that usually carry a conversion, all in one pass. It is the fast preflight you can run on any page, including a client's, before more budget goes through it.

It does not replace Microsoft Advertising or the UET Tag Helper — those still confirm which goals fire and how they attribute. TrackCanary is the step before that: a quick, honest read of what appears visible from the public page, and a way to keep watching it so a UET tag that drops off after a change does not go unnoticed.