Verify GA4 is receiving consent signals
A five-minute check with Google's free Tag Assistant.
Google's Tag Assistant shows exactly which consent signals your site sends. These steps follow Google's own consent-debugging guide.
Check the default (before consent)
- Open Tag Assistant at tagassistant.google.com and enter your website URL. Use a private window so you are a new visitor.
- In the Summary, select the earliest Consent event.
- In the API Call section, check
ad_storage,ad_personalization,ad_user_dataandanalytics_storage. All four should bedenied— that is KukiBot's default.
Check the update (after consent)
- Click Accept all on your KukiBot banner.
- In the Summary, select the most recent Consent event.
- The same four signals should now be
granted. You can also open your tag's Consent tab and compare the On-page Default and On-page Update columns.
Repeat in a new private window with Reject all — everything should stay denied.
Using Google Tag Manager?
Do the same checks, then open the Tags tab in the Summary and click a tag to see whether it fired according to the consent state.
If the default is missing or arrives late
- Make sure the KukiBot script is in the
<head>above your GA4 / GTM snippet. See correct setup order. - Check the
data-site-idin the script matches the site in your dashboard. - If you previously accepted on that browser, KukiBot applies your stored choice instead — test in a private window.
ℹ️Source for the Tag Assistant steps: Google's consent mode debugging guide.