Vai al contenuto
Gravità: AltaResponsabile: Admin CMPTempo di correzione: 1-2 h

Cookie e tracker prima del consenso

Correggi script di analytics, marketing e terze parti che si attivano prima che il visitatore abbia fatto una scelta sul consenso.

Copre: pre_consent_analytics_cookie, pre_consent_marketing_cookie, pre_consent_tracker

Perché è importante

Secondo ePrivacy e i principi del GDPR, lo storage e il tracking non essenziali richiedono consenso prima dell'attivazione. Caricare script di analytics o marketing prima della scelta dell'utente crea un rischio immediato di conformità.

Come verificare manualmente

  1. Open the site in a fresh private browsing window and do not interact with the banner.
  2. Check the Network panel for analytics, ads, heatmap, chat, or social pixel requests before consent.
  3. Inspect Application > Cookies and confirm whether non-essential cookies appear pre-consent.

Cause tipiche

  • GTM tags fire on page view without consent conditions.
  • CMP loads after analytics tags instead of before them.
  • Scripts are embedded directly in templates and bypass CMP blocking.

Correzione in GTM

  1. Enable Google Consent Mode v2 with default denied states for ad_storage, analytics_storage, ad_user_data, and ad_personalization.
  2. Update tag firing rules so analytics and marketing tags only fire when consent state is granted.
  3. Use consent initialization events before any marketing or analytics trigger paths.

Correzione in WordPress o plugin CMP

  1. Install and configure CookieYes or Complianz with blocking enabled for analytics and marketing categories.
  2. Map services to categories and verify scripts are blocked pre-consent.
  3. Clear cache or CDN and retest in an incognito browser session.

Correzione generica lato sviluppo

  1. Block third-party script execution until consent is granted.
  2. Store pending scripts with a consent category marker.
  3. On consent grant, activate only scripts matching accepted categories.
<script
  type="text/plain"
  data-consent="analytics"
  data-src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX">
</script>

Come confermare che la correzione funziona

  • Re-run the scan in a fresh session and confirm the finding disappears.
  • Verify that no non-essential cookies are set before interaction.
  • Verify that analytics and marketing requests only begin after opt-in.

Passaggio successivo

Riesegui una scansione dopo il deploy per confermare che sia cambiato il comportamento reale a runtime, non solo il testo del banner.

Cookie e tracker prima del consenso — GDPR Fix Guide