Gravidade: AltaResponsável: Admin CMPTempo para corrigir: 1-2 h
Cookies e trackers antes do consentimento
Corrija scripts de analytics, marketing e terceiros que se ativam antes de o visitante tomar uma decisão de consentimento.
Abrange: pre_consent_analytics_cookie, pre_consent_marketing_cookie, pre_consent_tracker
Porque isto importa
De acordo com a ePrivacy e os princípios do RGPD, armazenamento e tracking não essenciais exigem consentimento antes da ativação. Carregar scripts de analytics ou marketing antes da escolha do utilizador cria risco imediato de conformidade.
Como verificar manualmente
- Open the site in a fresh private browsing window and do not interact with the banner.
- Check the Network panel for analytics, ads, heatmap, chat, or social pixel requests before consent.
- Inspect Application > Cookies and confirm whether non-essential cookies appear pre-consent.
Causas típicas
- 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.
Correção no GTM
- Enable Google Consent Mode v2 with default denied states for ad_storage, analytics_storage, ad_user_data, and ad_personalization.
- Update tag firing rules so analytics and marketing tags only fire when consent state is granted.
- Use consent initialization events before any marketing or analytics trigger paths.
Correção em WordPress ou plugins CMP
- Install and configure CookieYes or Complianz with blocking enabled for analytics and marketing categories.
- Map services to categories and verify scripts are blocked pre-consent.
- Clear cache or CDN and retest in an incognito browser session.
Correção genérica para developers
- Block third-party script execution until consent is granted.
- Store pending scripts with a consent category marker.
- 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>Como confirmar que a correção funciona
- 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.
Próximo passo
Execute uma nova análise após o deploy para confirmar que o comportamento real em runtime mudou e não apenas o texto do banner.