https://coca-cola.com
Scanned Apr 15, 2026 · 36.0s
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 6 user data leaks before consent on coca-cola.com, including Advertising Tracker.
Security Headers
3/6 presentStrict-Transport-Security
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
default-src * data: mediastream: blob: filesystem: about: ws: wss: 'unsafe-eval' 'wasm-unsafe-eval' 'unsafe-inline';script-src * data: mediastream: blob: filesystem: about: 'unsafe-eval' 'unsafe-inline';connect-src * data: mediastream: blob: filesystem: about: 'unsafe-eval' 'unsafe-inline';frame-src * data: mediastream: blob: filesystem: about: 'unsafe-eval' 'unsafe-inline';frame-ancestors 'self' https://food.grab.com https://food.stg-myteksi.com
X-Frame-Options
Add X-Frame-Options header to prevent clickjacking attacks
X-Content-Type-Options
nosniff
Referrer-Policy
Set a Referrer-Policy header to control how much referrer information is shared
Permissions-Policy
Add a Permissions-Policy header to restrict browser features like camera, microphone, and geolocation
Google Consent Mode
V2Consent Parameters
Issues (1)
No default consent call detected — consent mode may not be initialised correctly
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
1018ms pre-consent
Google Tag Manager(GTM-NBWPCZW)
Loaded 1018ms after page load — before the consent banner was detected (banner appeared at 7205ms). 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.
✓ gtag('consent', 'update') call detected on rejection
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 rum.hlx.page 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)
Warnings5
Google Tag Manager2 findingsID trackedwww.googletagmanager.com

www.googletagmanager.com

Google Tag Manager loads before consent — this is expected and required for GCM v2 to initialise consent defaults before any tags fire

GTM loaded before consent banner — IP address transmitted to Google pre-consent (container: GTM-NBWPCZW)
Unknown third-party request to cdn.global.gcds.coke.com before consent
Unknown third-party request to www.google.com before consent
sessionStorage key "userTimeZone" written before consent
Info4
OneTrust2 findingscdn.cookielaw.org, OptanonConsent

cdn.cookielaw.org, OptanonConsent

OneTrust (OneTrust) loaded before consent: OneTrust cookie consent management

OneTrust cookie "OptanonConsent" set before consent
Google (Cdn)2 findingswww.gstatic.com, fonts.gstatic.com
www.gstatic.com, fonts.gstatic.com
Google (cdn) loaded before consent
Google (cdn) loaded before consent
Compliant39
Microsoft Clarity3 findingsID trackedwww.clarity.ms, scripts.clarity.ms, _clck

www.clarity.ms, scripts.clarity.ms, _clck

Microsoft Clarity (Microsoft) loaded correctly after consent

Microsoft Clarity (Microsoft) loaded correctly after consent

Microsoft Clarity cookie "_clck" set correctly after consent
TikTok Pixel7 findingsID trackedanalytics.tiktok.com, analytics-ipv6.tiktokw.us, _ttp, _tt_enable_cookie, tt_sessionId, tt_appInfo, tt_pixel_session_index

analytics.tiktok.com, analytics-ipv6.tiktokw.us, _ttp, _tt_enable_cookie, tt_sessionId, tt_appInfo, tt_pixel_session_index

TikTok Pixel (TikTok) loaded correctly after consent

TikTok Pixel (TikTok) loaded correctly after consent

TikTok Pixel cookie "_ttp" set correctly after consent

TikTok Pixel cookie "_tt_enable_cookie" set correctly after consent

TikTok Pixel (TikTok) wrote "tt_sessionId" to sessionStorage correctly after consent

TikTok Pixel (TikTok) wrote "tt_appInfo" to sessionStorage correctly after consent

TikTok Pixel (TikTok) wrote "tt_pixel_session_index" to sessionStorage correctly after consent
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
Snapchat Pixel4 findingssc-static.net, tr.snapchat.com, _scid, _scid_r
sc-static.net, tr.snapchat.com, _scid, _scid_r
Snapchat Pixel (Snapchat) loaded correctly after consent
Snapchat Pixel (Snapchat) loaded correctly after consent
Snapchat Pixel cookie "_scid" set correctly after consent
Snapchat Pixel cookie "_scid_r" 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
Snapchat cookie "X-AB" set correctly after consent
Google reCAPTCHA cookie "_GRECAPTCHA" set correctly after consent

OneTrust cookie "OptanonAlertBoxClosed" set correctly after consent
Google Analytics2 findings_ga, _ga_LKYNYLPZ3Z

_ga, _ga_LKYNYLPZ3Z

Google Analytics cookie "_ga" set correctly after consent

Google Analytics cookie "_ga_LKYNYLPZ3Z" set correctly after consent
Amazon2 findingsad-id, ad-privacy
ad-id, ad-privacy
Amazon cookie "ad-id" set correctly after consent
Amazon cookie "ad-privacy" set correctly after consent
Adobe Audience Manager2 findingsdemdex, dpm

demdex, dpm

Adobe Audience Manager cookie "demdex" set correctly after consent

Adobe Audience Manager cookie "dpm" set correctly after consent
The Tradedesk2 findingsTDID, TDCPM
TDID, TDCPM
The Tradedesk cookie "TDID" set correctly after consent
The Tradedesk cookie "TDCPM" set correctly after consent

Adobe Analytics cookie "AMCV_9075A2B154DE8AF80A4C98A7%40AdobeOrg" set correctly after consent

Adobe Advertising cookie "everest_g_v2" set correctly after consent

DoubleClick/Google Marketing cookie "IDE" set correctly after consent

Quantcast cookie "mc" set correctly after consent
Weborama cookie "AFFICHE_W" set correctly after consent
Snowplow cookie "sp" set correctly after consent
TikTok2 findingsttcsid, ttcsid_CRQH5UJC77U87P3RBFU0

ttcsid, ttcsid_CRQH5UJC77U87P3RBFU0

TikTok cookie "ttcsid" set correctly after consent

TikTok cookie "ttcsid_CRQH5UJC77U87P3RBFU0" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan coca-cola.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com