Gravité: ÉlevéeResponsable: Admin CMPTemps de correction: 1-2 h
Cookies et traceurs avant consentement
Corrigez les scripts analytiques, marketing et tiers qui s'activent avant que le visiteur n'ait fait un choix de consentement.
Couvre: pre_consent_analytics_cookie, pre_consent_marketing_cookie, pre_consent_tracker
Pourquoi c'est important
Selon ePrivacy et les principes du RGPD, le stockage et le tracking non essentiels nécessitent un consentement avant activation. Charger des scripts analytiques ou marketing avant le choix de l'utilisateur crée un risque immédiat de conformité.
Comment vérifier manuellement
- 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.
Causes typiques
- 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.
Correction dans 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.
Correction dans WordPress ou les 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.
Correction générique côté développeur
- 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>Comment confirmer que la correction fonctionne
- 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.
Étape suivante
Relancez un scan après déploiement pour confirmer que le comportement réel a changé, et pas seulement le texte de la bannière.