Consent State Pings

What Are Consent State Pings?

In a world with cookie banners and consent management, Consent State Pings determine how complete your conversion data is in Google Ads. Without correctly implemented pings, Google lacks the signals for Conversion Modeling, which degrades your Smart Bidding strategies. Clean integration with your consent management system is therefore mandatory for accurate tracking.

What Are Consent State Pings?

Consent State Pings transmit a user’s current cookie consent status to Google to enable privacy-compliant tracking. With every page view, the Google tag sends a ping with information about whether the user has accepted or declined cookies for advertising and analytics. Google then automatically adjusts its tracking behavior accordingly.

Consent State Pings are signals that your Google tag sends to Google on every page view to communicate the user’s current consent status. The ping contains information about whether the user has accepted or declined cookies for advertising (ad_storage) and analytics (analytics_storage). Google adjusts its tracking behavior accordingly.

Within Google Consent Mode, two types of Consent State Pings are distinguished: the default ping on page load (before the user makes a decision) and the update ping after active consent or rejection. The default ping should be set to “denied” until the user actively consents. After consent, an update ping sends the new status “granted” and Google activates full tracking.

For correct implementation, ensure that your consent management platform supports Consent Mode and triggers the pings correctly. Faulty implementations lead to inaccurate data: if the status is incorrectly set to “granted,” you violate GDPR. If it remains permanently on “denied,” you lose measurement data. Verify the implementation via Google Tag Assistant and make sure Cookieless Pings are sent correctly in the rejection case.