https://merck.com
Scanned Apr 15, 2026 · 34.5s
Your website score is
Grade
BannerConsent Banner
Yes
Regulatory Compliance
Multi-regulation overview — click any regulation for details
Technical scan only. A passing score does not equal legal compliance. Consult qualified legal counsel for your jurisdiction.
Tag Leak detected 7 user data leaks before consent on merck.com, including Advertising Tracker.
Security Headers
5/6 presentStrict-Transport-Security
max-age=31536000
Content-Security-Policy
script-src 'self' 'unsafe-inline' 'unsafe-eval' https: blob:; style-src 'self' 'unsafe-inline' https:; frame-src 'self' https:; frame-ancestors 'self'; img-src 'self' https: data:; media-src 'self' https: data: blob:; object-src 'none'; font-src 'self' https: data:; default-src 'self' https: wss:; base-uri 'none';
X-Frame-Options
DENY
X-Content-Type-Options
nosniff
Referrer-Policy
no-referrer-when-downgrade
Permissions-Policy
Add a Permissions-Policy header to restrict browser features like camera, microphone, and geolocation
Google Consent Mode
Not DetectedGoogle Consent Mode v2 was not found on this page. GCM v2 allows Google's tags to adjust their behavior based on user consent, and is required for compliant advertising measurement in the EU. Without it, your Google Ads and GA4 conversions may be impacted after consent is declined.
GTM container detected (GTM-M74WZDM) but no consent mode initialisation found. Add gtag('consent', 'default', ...) before your GTM snippet.
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
908ms pre-consent
Google Tag Manager(GTM-M74WZDM)
Loaded 908ms after page load — before the consent banner was detected (banner appeared at 7579ms). Per a 2022 German court ruling, GTM itself transmits the user's IP to Google pre-consent.
Consent Mode V2: Not Detected
Google Consent Mode was not detected on this site.
Consent Record Audit
Issues detectedConsent record stored after interaction
GDPR Art. 7(1)Found: OptanonConsent (OneTrust)
Record contains timestamp
Art. 7(1)Timestamp field detected
Record contains consent state
Art. 7(1)Accept/reject state detected
Record contains consent categories
Art. 7(1)Consent categories (analytics, marketing, etc.) not found in record
Consent withdrawal mechanism accessible
GDPR Art. 7(3)No way for users to withdraw consent found on page
No cookie settings link, footer link, or floating consent button was detected. GDPR requires users to withdraw consent as easily as they gave it.
Why this matters
Under GDPR Article 7, controllers must be able to demonstrate that consent was given (Art. 7(1)) and ensure users can withdraw consent at any time, as easily as giving it (Art. 7(3)). Sites with no consent record or no withdrawal mechanism cannot legally rely on consent as a lawful basis.
Tracker categories detected
Critical2
advertising tracker at metrics.brightcove.com loaded before consent
No recognizable consent withdrawal mechanism detected — GDPR Article 7(3) requires users can withdraw consent as easily as giving it (cookie settings link or floating button expected)
Warnings6
Google Tag Manager2 findingsID trackedwww.googletagmanager.com
www.googletagmanager.com
Google Tag Manager (Google) loaded before consent: Loads the GTM container which may trigger other tags
GTM loaded before consent banner — IP address transmitted to Google pre-consent (container: GTM-M74WZDM)
Unknown third-party request to www.us-hh.com before consent
sessionStorage key "hexaDate" written before consent
sessionStorage key "previousPageHref" written before consent
sessionStorage key "pageviewCount" written before consent
Info6
OneTrust2 findingscdn.cookielaw.org, OptanonConsent
cdn.cookielaw.org, OptanonConsent
OneTrust (OneTrust) loaded before consent: OneTrust cookie consent management
OneTrust cookie "OptanonConsent" set before consent
Brightcove (Cdn)3 findingsplayers.brightcove.net, vjs.zencdn.net, edge.api.brightcove.com
players.brightcove.net, vjs.zencdn.net, edge.api.brightcove.com
Brightcove (cdn) loaded before consent
Brightcove (cdn) loaded before consent
Brightcove (cdn) loaded before consent
OneTrust CMP (OneTrust) loaded before consent: OneTrust geo-lookup — determines which consent banner to show based on user location
Compliant12
Meta Pixel3 findingsID trackedwww.facebook.com, connect.facebook.net, _fbp
www.facebook.com, connect.facebook.net, _fbp
Meta Pixel (Meta) loaded correctly after consent
Meta Pixel (Meta) loaded correctly after consent
Meta Pixel cookie "_fbp" set correctly after consent
Optimizely3 findingscdn.optimizely.com, logx.optimizely.com, optimizelyEndUserId
cdn.optimizely.com, logx.optimizely.com, optimizelyEndUserId
Optimizely (Optimizely) loaded correctly after consent
Optimizely (Optimizely) loaded correctly after consent
Optimizely cookie "optimizelyEndUserId" set correctly after consent
Google Ads3 findingswww.google.com, _gcl_au, _gcl_ls
www.google.com, _gcl_au, _gcl_ls
Google Ads (Google) loaded correctly after consent
Google Ads cookie "_gcl_au" set correctly after consent
Google Ads (Google) wrote "_gcl_ls" to localStorage correctly after consent
OneTrust cookie "OptanonAlertBoxClosed" set correctly after consent
Google Analytics2 findings_ga, _ga_9Z6MGXJTR9
_ga, _ga_9Z6MGXJTR9
Google Analytics cookie "_ga" set correctly after consent
Google Analytics cookie "_ga_9Z6MGXJTR9" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan merck.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com