LogoLogo
Analytics HelperSirdata APISemantic APIA propos de Sirdata
English
English
  • Sirdata CMP
  • INSTALL
    • Web & Mobile web
    • AMP
    • Via a Tag Manager
      • Loading via Google Tag Manager
    • In a CMS
      • Loading in Shopify
      • Loading in Wordpress
      • Loading in Prestashop
      • Loading in Magento
      • Loading in Drupal
    • Cache Systems Exclusion
      • Autoptimize WordPress Plugin
      • Cloudflare WordPress Plugin
      • LiteSpeed WordPress Plugin
      • NitroPack WordPress Plugin
      • SG Optimizer WordPress Plugin
      • WP Super Cache WordPress Plugin
      • W3 Total Cache WordPress Plugin
      • WP Meteor Plugin for Wordpress
      • WP Rocket WordPress Plugin
  • CONSENT TRANSMISSION STANDARDS
    • Introduction
    • Google Consent Mode
      • Mandatory Prerequisite
      • Activation of Advanced Google Consent Mode
        • Via the Sirdata CMP
        • Via Google Tag Manager
      • Activation of Basic Google Consent Mode
        • Via the Sirdata CMP
        • Via Google Tag Manager
      • Activation via Sirdata CMP
      • Activation via Google Tag Manager
    • Microsoft UET Consent Mode
    • Microsoft Clarity Consent
  • CMP API
    • How it works
    • Examples
    • Working with iframes
  • Advanced features
    • Passive mode
    • Set language per user
    • Manually display the CMP
  • Script management
    • Remote Tags Management without a Tag Manager
    • Remote Tags Management with a Tag Manager
    • Tag Management with Google Tag Manager
    • Local script Management
    • Advanced configuration
    • Examples
    • Share the TC String
    • Tag Management setup service
  • Analytics
    • Google Analytics
  • F.A.Q.
    • Integration
      • Is Abconsent compatible with Stape?
      • Is ABConsent compatible with Addingwell?
    • Google Consent Mode V2
      • Google Consent Mode V2 utility
      • News Google Consent Mode V2
      • Advanced mode or basic mode
    • Packaging
      • Cookies management
      • Tags packaging
    • Cookie settings
    • Button operation
    • Button color
    • A/B test
    • Mobile, tablets ...
    • Multi-sites
    • Mobile display
    • Private browsing
    • AMP consent
    • AMP consent button
    • Tags conditionning
    • Google Ads
    • Error 6.1 Google
    • Google PageSpeed
    • Refusal & Targeted ads
    • Mozilla and adblocks
    • Wordpress, Joomla, etc ...
    • Shopify
    • Pricing
      • The Two Types of Licenses
      • What happens when I reach the limit of my monthly plan?
      • Do you offer a trial period?
      • What are the accepted payment methods?
      • Do you offer packages for very high volumes of hits?
      • Are unused hits carried over to the next month?
      • What is considered a Hit?
      • Can I change plans?
    • Content Security Policy (CSP)
    • Google
      • Problem gclid google
      • Google extensions
    • How to Verify the Integration of My CMP?
    • How to Identify the Cookies Present on Your Website?
    • Abconsent CMP is compatible with Taggr ?
  • CMP Services
    • CMP Configuration
    • CMP Integration
    • Tag Conditioning
    • Compliance audit
    • Extra-vendorlist
    • Video-Wall
    • Inventory Partners
    • Consulting
  • Links
    • Configure your CMP
    • Sirdata API
    • Semantic API
    • About Sirdata
    • Analytics Helper
Propulsé par GitBook
Sur cette page

Cet article vous a-t-il été utile ?

  1. F.A.Q.
  2. Google Consent Mode V2

News Google Consent Mode V2

What’s New in Google Consent Mode V2?

PrécédentGoogle Consent Mode V2 utilitySuivantAdvanced mode or basic mode

Dernière mise à jour il y a 3 mois

Cet article vous a-t-il été utile ?

Google Consent Mode V2: More Than Just an Update!

🚀 New Signals for Enhanced Control

Google Consent Mode V2 introduces two powerful signals that refine how your data is used for advertising:

  • ad_user_data: This signal is the master control for personalized advertising. Granting consent allows Google to use your data for a wide range of ad personalization purposes, including targeting, frequency capping, measurement, and reporting. Denying consent restricts Google to using your data for non-personalized ads and aggregated reporting.

  • ad_personalization: This signal provides granular control over individualized ad personalization. Granting consent allows Google to tailor ads specifically to your interests and past behavior. Denying consent prevents Google from using your data to create a personalized ad profile, but they may still use aggregated data for broader audience targeting and conversion measurement.

🎯 Subtle Yet Powerful Impact

While ad_user_data and ad_personalization don't directly block or allow tags like ad_storage and analytics_storage, they play a vital role in informing Google's ad systems about user consent. These signals significantly influence how Google processes data for advertising, impacting everything from ad targeting and measurement to conversion modeling.

🌟 Why These Signals Matter

These new signals offer several key benefits:

  • Granular Privacy Control: Users have more precise control over how their data is used for advertising.

  • Improved Conversion Measurement: Even when users decline personalized ads, Google can leverage aggregated, non-personalized data to estimate conversions, providing valuable insights for your marketing campaigns.

  • Enhanced Compliance: These signals help ensure your advertising practices align with user privacy preferences and evolving regulations.

🔗 Dive Deeper

For a comprehensive understanding of Google Consent Mode V2 and its intricacies, consult the . Understanding the interplay of all consent signals is crucial for maximizing both user privacy and marketing effectiveness.

Consulter la documentation officielle de Google