Usercentrics Smart Data Protector
Consent Autoblocker Test Page
This page deliberately loads a range of third-party resources: tracking scripts, CDN libraries, video and map embeds. Both test variants are built identically apart from the Usercentrics snippet in the head. Use the browser devtools network tab to compare which requests actually go out.
<script id="usercentrics-cmp" src="https://web.cmp.usercentrics.eu/ui/loader.js" data-settings-id="pUqNOMzoCEPZ57" async></script> <script type="application/javascript" src="https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js"></script>
1. YouTube video (iframe embed)
Standard YouTube embed via youtube.com. A working autoblocker replaces the
iframe with a placeholder before it loads, or strips its src attribute.
2. Further iframe embeds
A Vimeo player and a Google Maps embed as additional blocking candidates.
3. Embedded third-party scripts
These resources are embedded in the <head> or at the end of the
<body> – some as a plain <script src> tag, others as
an inline snippet that only injects its loader at runtime via
createElement('script').
| Service | Host | Embedding method | Global |
|---|---|---|---|
| Google Fonts | fonts.googleapis.com | <link rel="stylesheet"> in head | – |
| Google Analytics 4 | www.googletagmanager.com | <script src> in head | gtag |
| Google Tag Manager | www.googletagmanager.com | Inline snippet, runtime injection | dataLayer |
| Meta Pixel | connect.facebook.net | Inline snippet, runtime injection | fbq |
| Hotjar | static.hotjar.com | Inline snippet, runtime injection | hj |
| Microsoft Clarity | www.clarity.ms | Inline snippet, runtime injection | clarity |
| jQuery (CDN) | code.jquery.com | <script src> in body | jQuery |
| Lodash (cdnjs) | cdnjs.cloudflare.com | <script src> in body | _ |
| LinkedIn Insight Tag | snap.licdn.com | Inline snippet, runtime injection | _linkedin_data_partner_ids |
| Tracking pixel | www.facebook.com | <img> (noscript pixel) | – |
4. Runtime injection tests
Only after a click is another third-party script or YouTube iframe inserted into the DOM via JavaScript. This verifies whether the autoblocker still catches resources after the initial page load, typically through a MutationObserver.
5. Tracking pixels & third-party images
A counting pixel and an external image – typical content-blocking candidates.