Test Google Consent Mode v2 configurations. Simulate different consent states and see how they affect analytics and ad tag behavior.
Consent Mode v2 does not stop Google from collecting data; it decides what shape that data takes. This tool takes the consent snippet your site runs - the gtag consent calls with their granted and denied states - and reports what each Google tag will do under every visitor choice: full collection, restricted cookieless pings, or disabled features. The result that surprises people most: with ad_storage and analytics_storage denied, the tags still fire. They send cookieless hits carrying the IP address, user agent, and page URL so Google can model conversions, so denied never means nothing is sent.
A concrete input and expected output from the current implementation.
Input
gtag('consent', 'default', {
ad_storage: 'denied',
analytics_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied'
}); Expected output
All four v2 signals are denied: full restricted mode. ad_storage denied: ad cookies are not set. Ads tags still send cookieless pings carrying the IP address, user agent, and page URL. analytics_storage denied: no analytics cookies are set; hits are sent without identifiers for behavioral modeling. ad_user_data denied: no user data is forwarded to Google for advertising. ad_personalization denied: personalized advertising and remarketing are disabled. Requests fire in all denied states; denied consent removes cookies and personalization, not traffic.
Each of the four v2 signals maps to one documented behavior, so a default of all-denied yields the restricted-mode profile: requests still go out, cookies do not. Users expect a fully silent tag and misread this as a broken setup; it is the intended design that makes conversion modeling possible.
The tool reads every consent call in the pasted snippet, default and update, and maps the four v2 signals - ad_storage, analytics_storage, ad_user_data, ad_personalization - to their states. It flags configurations that omit the two v2-only signals, since Google expects all four in a complete setup, and renders each signal as a status line describing the documented behavior of its state.
Beyond the pasted defaults, you can toggle each signal between granted and denied to model what happens when a visitor changes their choice after the page loads. Every combination produces a per-tag verdict: full collection, restricted cookieless pings, or disabled features. An update applies from the moment it fires; nothing collected earlier is retroactively reclassified, which the report states explicitly.
No. Denied consent puts tags in restricted mode: Google Ads and GA4 still receive cookieless pings with the IP address, user agent, and page URL, which feed conversion and behavioral modeling. Consent Mode removes cookies and identifiers; it never fully silences the tags. If you require no data at all, the tags must not be loaded, which is beyond what Consent Mode can do.
Yes. The banner is the interface; Consent Mode is the layer that turns the visitor's choices into signals the Google tags understand. Without it, the tags keep collecting full data no matter what the banner shows. For ad accounts serving in the EEA, Google requires consent signals, including the two v2-only signals ad_user_data and ad_personalization, so the banner and Consent Mode are complements, not alternatives.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.