Purpose: This page demonstrates Kukie.io's banner behaviour when a customer has enabled Data Transmission Controls or Global Consent Defaults on their Google tags. The banner is configured to appear only for visitors in the EEA. For visitors outside the EEA (e.g. the US), the banner does not appear, and Kukie automatically fires gtag('consent', 'update', 'granted') to maintain measurement.
Configuration
Site Key
1fd02818-3c7b-483b-8e61-69614e663c54
Google Tags
gtag.js + GTM
Expected Behaviour
- From the EEA: Kukie banner renders. Consent defaults to
denied. The visitor's choice updates the consent state.
- Outside the EEA (e.g. US): No banner renders. Kukie fires
gtag('consent', 'default', 'denied') followed immediately by gtag('consent', 'update', 'granted') within the 500 ms wait_for_update window. Google tags proceed with full measurement.
How to Verify
- Open this page from a non-EEA location (e.g. the US).
- Open DevTools Console. The banner should not render.
- In the Console, run:
google_tag_data.ics.entries
- All four required consent types (
ad_storage, ad_user_data, ad_personalization, analytics_storage) should be granted.
- Alternatively, append
?kukie_debug=1 to this page's URL to see a full Consent Mode Debug Report in the console.
Debug Mode
Append ?kukie_debug=1 to this page's URL to enable Kukie's Consent Mode Debug Report. The report prints to the browser console and shows:
- Detected Google tags on the page (gtag.js, GTM) and their load order relative to the Kukie script
- Timing verification: whether
gtag('consent', 'default', ...) fired before any Google tag activity
- Current runtime consent state read from
google_tag_data.ics.entries
- A clear pass/fail verdict with fix instructions for any detected issues