Does the Bing UET tag fire before Accept?

Not legal advice

This guide explains how to observe the Bing UET tag in the browser, and any conversion-upload or server path, relative to Accept and Reject. It is not legal advice, not a Bing Ads or Microsoft Advertising setup tutorial, and not a GDPR, ePrivacy, CPRA, or other compliance certificate. ConsentProbe reports are technical observations of what fired. They do not say what counsel would allow. Observation is not counsel permission.

Last updated September 28, 2026. The before-Accept audit owns the general first load. The Reject leftovers guide owns a Reject failure. The pre-consent checklist owns the pass order. The marketing-pixels FAQ owns the wider pixel question. Meta Pixel, TikTok Pixel, the LinkedIn Insight Tag, the Pinterest Tag, the Snapchat Pixel, the X Pixel, and the Reddit Pixel are sibling pages. This page stays on Bing UET.

Short answer

Microsoft Advertising can show up in the browser through the Bing UET tag, and some setups also upload conversions from the server. A cookie consent audit asks whether Bing UET cookies, storage, or network requests to bat.bing or related Bing marketing hosts appeared before Accept, and whether Reject All stopped them. Conversion uploads can still leave your backend when the browser UET tag is delayed.

Treat banner text that says marketing is off as a claim. Falsify it on a clean visit. Capture bat.bing and related marketing host rows, plus the cookies those requests set, on Fresh. Repeat after Reject. Note any fan-out that continues after the click. Host names are examples of where a browser test can look. This page does not tell you which host to block.

Server conversion uploads are harder to see from DevTools alone. Look for storefront or checkout flows that still trigger uploads, and ask engineering for conversion-upload logs labeled by consent state when the browser pack is clean and Microsoft Advertising reporting still shows traffic.

Browser tag and conversion uploads

Three layers get mixed when someone says Bing is off because the UET tag waits for Accept. Separate the browser tag from the conversion upload. Write the finding as a UET request before Accept, or a bat.bing host after Reject. Leave permission with counsel.

Fresh and Reject on the storefront

These steps compare a claimed wait-for-Accept state with cookies and requests. They do not install a UET tag or open Microsoft Advertising. The before-Accept audit and the pre-consent checklist hold the general method. The Reject leftovers guide and the marketing-pixels FAQ hold a Reject failure.

1. Use a clean profile. Load the storefront once. Do not click Accept.
2. Capture cookies, storage, and Network for Bing marketing hosts, including bat.bing.
3. Screenshot the banner state. Label the pack Fresh.
4. Open a new clean profile, or clear storage. Click Reject All. Navigate once more.
5. Recapture cookies and Network. Label the pack Reject. Compare it with Fresh and, if you ran one, with an Accept control.
6. Write one finding sentence per mismatch, such as a Bing UET cookie on Fresh, or a bat.bing host after Reject.

Upload logs when the browser looks clean

A quiet browser tag and a quiet conversion-upload path are different results. Uploads can still leave from checkout, purchase, or another backend hook when the page delayed the UET tag. If the browser pack is clean and Microsoft Advertising reporting still shows events, ask engineering for upload rows tagged by consent state.

Microsoft's UET notes name a request to bat.bing when the page loads the tag. Example of a storefront clue, not a customer capture: Fresh Network shows a request to a bat.bing host before any banner click. The same host appears after Reject and one more navigation.

This page does not walk through Microsoft Advertising or Bing Ads configuration. The question to falsify is whether an upload happened on Fresh or after Reject. Those sibling pixel pages use the same browser-versus-server split. This page stays on Bing UET.

When checking Bing hosts gets slow

Checking Bing hosts across templates by hand takes a long time. ConsentProbe runs Fresh and Reject on the storefront URL. Each finding stays tied to a request, a cookie, or a screenshot.

Use the free US-baseline visit when you want the report format. Use paid EU or California scenarios when those regions are the claims. The free versus paid guide draws that line. ConsentProbe does not install or configure Bing UET or Microsoft Advertising, does not install a CMP, and does not issue a certificate.

FAQ

Limits of this page

This page tells you how to check Bing UET cookies and hosts on Fresh, how to repeat the check after Reject, and why a gated browser tag leaves conversion uploads untested. It is not legal advice, not a Bing Ads setup guide, and not a certificate. Observation is not counsel permission. ConsentProbe reports stay tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU or California legal conclusion.

Related guides

Open the before-Accept audit for the general first load, the Reject leftovers guide when Reject still tracks, the pre-consent checklist for the pass order, and the marketing-pixels FAQ for the wider pixel question. The pixel pages below are sibling checks.

• How to run a cookie audit before Accept
• Reject All Still Tracking: What to Check After You Say No
• Pre-consent audit checklist: what to verify before Accept
• Does Reject All stop marketing pixels?
• Meta Pixel and CAPI before Accept: what to check
• Does the TikTok Pixel fire before Accept?
• Does the LinkedIn Insight Tag fire before Accept?
• Does the Pinterest Tag fire before Accept?
• Does the Snapchat Pixel fire before Accept?
• Does the X (Twitter) Pixel fire before Accept?
• Does the Reddit Pixel fire before Accept?
• What belongs in a cookie consent audit evidence pack?
• What does a free US-baseline cookie audit prove vs paid EU or California scans?
• CMP claims vs runtime evidence: how do you prove the banner actually works?
• Cookie audit hub: which consent test should you run first?
• ConsentProbe methodology
• Pricing and listed regional products