Microsoft Ads GDPR compliance and consent risk
Microsoft Advertising (Bing Ads) conversion tracking and remarketing. This page combines ConsentLens detection rules with live public scan data so you can see how often Microsoft Ads appears, whether it fires before consent, and which compliance issues it tends to create.
10%
Of scanned sites
45 of 444 public sites include Microsoft Ads.
0%
Fire before consent
0 detected sites fired it before a user could consent.
2%
Seen after rejection
1 detected sites show post-rejection evidence.
HIGH
Consent risk
Marketing tracker classified from ConsentLens tracker database.
How ConsentLens detects Microsoft Ads
Domains
- bat.bing.com
- bat.r.msn.com
Globals
- window.uetq
Script patterns
- bat.js
ConsentLens combines these signals with request timing. If Microsoft Ads sends a data request during the first 500ms of page load, it is treated as a pre-consent tracking risk and connected to the relevant scan evidence.
Common compliance issues
Advertising / remarketing trackers detected
45Microsoft Ads continues tracking after consent rejection
1Example public scans detecting Microsoft Ads
| Domain | Score | Consent timing |
|---|---|---|
| yourselfirst.com | 20/100 | No early fire |
| debutinfotech.com | 20/100 | No early fire |
| jelvix.com | 39/100 | No early fire |
| madwise.si | 20/100 | No early fire |
| clinic.dmm.com | 68/100 | No early fire |
| curon.co | 20/100 | No early fire |
| utmel.com | 68/100 | No early fire |
| tekrevol.com | 20/100 | No early fire |