Complianz and Site Kit: Consent Mode v2 via the WP Consent API
Complianz shows a banner and Site Kit loads GA4, yet a scan finds no Consent Mode. How the WP Consent API links the two, and how to check every step.
Lukas Kontur · · 10 min read
Your WordPress site uses Complianz for the cookie banner and Site Kit by Google for Google Analytics 4 (GA4). The banner works, but a scan reports Google services found, but no Consent Mode detected, or Google Ads says consent mode is missing. In this setup, three plugins have to work together, and if one link is missing, Google never hears what the visitor chose. This guide explains the chain, how to find the broken link and how to fix it.
The symptoms
- A scan report shows Google services found, but no Consent Mode detected: GA4 or Google Ads requests were seen, but no Consent Mode signal.
- In Tag Assistant, the Consent tab is empty.
- In Site Kit, the consent mode switch is off, or it shows a prompt to install another plugin.
- After you switched consent mode on, visitor numbers from Europe dropped in your GA4 reports.
This is common. In our scan of 97,304 EU websites, 13.7% of sites using Google services showed no Consent Mode implementation (full study). That number covers all setups, not Complianz or Site Kit in particular.
How the three plugins fit together
Google Consent Mode is a short status message that a website sends to Google: first a default ("nothing allowed yet"), then an update after the visitor clicks your banner. Google tags then behave according to that status (Google: consent mode overview). With Complianz and Site Kit, the message is passed along like this:
| Plugin | Its job in the chain |
|---|---|
| Complianz | Shows the banner and stores the visitor's choice. |
| WP Consent API | Passes that choice on to other plugins in a standard format. |
| Site Kit by Google | Adds the Google tag, the consent default and the update. |
The WP Consent API plugin is the messenger in the middle. Its own description says it "standardizes the communication of accepted consent categories between plugins" and that "the plugin itself will not handle consent" (WordPress.org: WP Consent API). It lists both Complianz and Site Kit as supported plugins. Complianz says that once the WP Consent API is installed, it "will handle the consent" for plugins that support it (Complianz: WP Consent API).
Site Kit documents what it does once consent mode is on (Site Kit: consent mode):
- It adds the consent code with default settings to your pages.
- By default, it does not track visitors from the European Economic Area, Switzerland and the United Kingdom in Google Analytics and Google Ads until they consent through your consent plugin.
- By default, it updates consent for the "statistics" and "marketing" categories of the WP Consent API.
This explains the drop in visitor numbers: visitors who deny or never answer are no longer counted in the normal way.
How to check it yourself
You need Chrome and about ten minutes.
- Open your home page and press Ctrl + U (on a Mac, Cmd + Option + U) to view the page source.
- Press Ctrl + F and search for
Consent Mode snippet added by Site Kit. Site Kit says the commentGoogle tag (gtag.js) Consent Mode snippet added by Site Kitshows that its consent code is on the page. - In the same source, search for
googletagmanager.comand note every match. Each one is a Google tag. - Open a new private window (three-dot menu, "New Incognito window") and go to tagassistant.google.com.
- Click Add domain, enter your site's address and click Connect. Your site opens in a new window. Do not click the banner yet.
- Back in Tag Assistant, select the earliest Consent event in the Summary, then open the Consent tab. Google says this tab "is empty when consent mode is not implemented on the page" (Google: troubleshoot consent mode). If it is filled, the On-page Default column should show "Denied" for
ad_storage,analytics_storage,ad_user_dataandad_personalization. - In your site's window, click Deny. Check the latest Consent event: On-page Update should still say "Denied".
- Open a second private window, connect again, and this time click Accept. On-page Update should switch to "Granted".
Now read the result:
- No Site Kit comment in the source: consent mode is not active in Site Kit. Start with causes 1 and 2 below.
- The comment is there, but the Consent tab is empty or the default comes late: another Google tag runs first. Look at what you counted in step 3, then cause 3.
- Default is "Denied", but Accept never changes it to "Granted": the visitor's choice does not reach Site Kit. See cause 4.
Why it happens
In the order we see them most often:
- Consent mode is switched off in Site Kit. It is not on by default. The switch only appears when the Analytics module is connected in Site Kit, or when you use Google Ads through it (Site Kit: consent mode).
- The WP Consent API plugin is missing. Site Kit needs it plus a consent plugin. Without the messenger, Complianz and Site Kit cannot talk to each other. Complianz marks this plugin as "MANDATORY" in its own Site Kit guide (Complianz: Consent Mode v2 with Site Kit).
- GA4 is loaded by something other than Site Kit. If Site Kit finds an existing GA4 snippet, it switches its own Place Google Analytics code setting off "to avoid duplication" (Site Kit: managing placed code). Then the GA4 tag on your page comes from your theme, a header and footer plugin, another analytics plugin or Google Tag Manager, and it may run before any consent default is set.
- Complianz does not know about Site Kit. Complianz's guide has you switch on its Google Site Kit integration and answer the statistics questions in the Wizard. If these are not set up, the choice may not be passed on.
- The consent code is delayed or cached. Google says the default must be set "before any tags or other code uses or updates consent", and advises: "Don't set default consent states asynchronously" (Google: troubleshoot consent mode). A "delay JavaScript" feature in a speed plugin, or a cached page from before you made the change, can break that order.
The fix
Work through the steps in order and test after each one, in a new private window.
Step 1: install the WP Consent API
- In WordPress, go to Plugins, Add New Plugin and search for "WP Consent API".
- Install and activate it. Site Kit can also do this for you: below its consent mode switch it shows an Install button when the plugin is missing.
Step 2: switch on consent mode in Site Kit
- Go to Site Kit, Settings, Admin Settings.
- Switch consent mode on.
- If there is no consent mode switch, connect Analytics in Site Kit first.
Step 3: keep one GA4 tag, placed by Site Kit
- Go to Site Kit, Settings, Connected Services, Analytics, Edit.
- Check whether Place Google Analytics code is on.
- If it is off, find the other GA4 snippet. Site Kit suggests checking your theme settings and templates, header and footer plugins, and other Google Analytics plugins.
- Remove that other snippet, or ask whoever maintains your site to do it.
- Switch Place Google Analytics code on, and save.
If your Google tags run through Google Tag Manager instead, this guide's setup does not cover them. Use a consent template in GTM, as explained in our GTM Consent Mode v2 guide.
Step 4: connect Complianz to Site Kit
These steps follow Complianz's guide linked above:
- Go to Complianz, Integrations, Plugins, make sure the Google Site Kit integration is on, and click Save.
- Go to Wizard, Consent, Statistics. For "Do you compile statistics of this website?" choose Yes, with Google Analytics.
- Answer the follow-up questions about your Google Analytics settings and click Save and Continue. Which answers fit your site is a legal question, not a technical one.
According to Complianz, with Site Kit "you can only use Advanced Consent Mode" (Complianz: Consent Mode for 7.0). Google tags then load with the page and adapt to the consent status. So requests to Google before a click are expected in this setup, but no _ga cookie should be written until the visitor accepts.
Step 5: make sure only one plugin sends the consent default
The two vendors' guides differ here. Site Kit says that with its consent mode on, you do not need your consent plugin's own Consent Mode feature, and that using it "could cause possible conflicts with Site Kit". Complianz's Site Kit guide has you answer "Yes" to "Do you want to enable Google Consent Mode V2?" in its statistics settings. Complianz also says the steps in its general Consent Mode v2 guide "require Complianz Premium" (Complianz: Consent Mode v2 guide), so your Wizard may not show every question.
Do not guess. Test it:
- Set the Complianz Consent Mode V2 question to one answer, "Yes" or "No", and save.
- Repeat steps 4 to 8 of the check above.
- If Tag Assistant shows a clean "Denied" default and a correct update after Accept, keep that answer.
- If the default is missing, shows "Granted", or values change back and forth, try the other answer.
Step 6: clear caches and exclude the consent code from delays
- Clear your caching plugin, your host's cache and Cloudflare if you use it.
- If your speed plugin has a "delay JavaScript" or "defer" feature, exclude Site Kit's consent code and the Complianz scripts from it. Your speed plugin's documentation explains how.
- Check the page source again for the Site Kit comment.
How to verify the fix
Use a new private window for each run:
- Page source: the Site Kit consent comment is there, and only one GA4 tag is left.
- No click: in Tag Assistant, On-page Default shows "Denied" for the four signals. In DevTools (F12), Application, Cookies, there is no
_gacookie. - Deny, then reload, then a second page: still no
_ga, and On-page Update does not switch to "Granted". - Accept: On-page Update shows "Granted",
_gaappears, and GA4's real-time report shows your visit.
Re-run this after every Complianz, Site Kit or theme update.
Related reading: GA4 and Google Ads on WooCommerce: Consent Mode v2 step by step, Complianz not blocking GA4 or Meta Pixel and Pre-consent tracking explained.
Check your site in 1 minute
Our free scan loads your site in a clean browser and records whether a Consent Mode default is sent before Google tags run. No signup needed. Run a free scan.
Get alerted when it breaks
A plugin update, a new theme or a speed setting can quietly break the chain between Complianz and Site Kit. With monitoring, we re-scan your site on a schedule and email you when Consent Mode disappears or tracking changes. The free plan includes one monitored site with a weekly re-scan and email alerts. Create an account and add your site.
On WordPress, our free WordPress plugin also re-scans your site automatically after plugin and theme updates.
Last updated: