3 findings · 5 warnings · 1 checks passed
Vendors
zU2aduOeG6Z5tjXFIMzwnaSffUoGdvt9KB3OmYYG6tH.C711361151094G-GX9915EGRPG-LWCSWQHPBWGTM-NFX3Z2ZSUA-59409382-15208077forum24.cz1438802Violations
GCM_002Do not write analytics or advertising cookies until the visitor has made a consent choice. Load GTM/GA4 tags behind a denied consent default and let the CMP's update unblock them.
GCM_008Affected: broken
Call gtag('consent', 'update') immediately after the visitor's choice, with the correct values for both accept and reject. Do not rely on a page reload: it creates duplicate pageviews and breaks session attribution.
GCM_001Call gtag('consent', 'default') with denied values before GTM or GA4 loads, so the initial consent state is explicit.
GCM_003Make both the accept and the reject button update the consent state through the GTM Consent API or gtag('consent', 'update').
GCM_009Affected: Gemius, Google Ads, Google Analytics 4, Hotjar, Meta Pixel, Seznam Sklik, Google Universal Analytics
The affected vendors set an identifier or sent measurement that is not verifiably cookie-less before the visitor chose. Load them only after consent, or configure a documented cookie-less mode that sends no identifiers.
GCM_012Affected: Plausible Analytics
No identifier was observed, but the visitor's IP address and page context still reached a third party before consent. To be compliant under this check, load the vendor only after consent.