How to implement Consent Mode v2 in WordPress and why it matters
How to implement Consent Mode v2 in WordPress? In practice, you set up a consent banner, connect it with Google Tag Manager or the Google tag, and check whether consent states reach GA4 and Google Ads before scripts collect full data.
Consent Mode v2 is not just a cookie message. It tells Google whether a visitor has agreed to analytics, advertising storage, advertising user data and personalisation. Without it, campaigns aimed at users in the European Economic Area may lose conversion signals and analytics becomes harder to trust.
What to prepare before configuring consent
Before installing a plugin, check which tools actually collect data on the site. Otherwise the banner may look correct while Google Analytics, an ad pixel or a chat script still loads too early.
For small WordPress sites, a solid CMP plugin such as CookieYes and a tidy Google Tag Manager setup is often enough. For larger sites, start with a quick audit of scripts and the privacy policy.
Script list
List GA4, Google Ads, Meta Pixel, chats, maps and forms. Each script should have a consent category.
Google-ready CMP
Choose a tool that supports Consent Mode v2 and updates consent after the visitor makes a choice.
Tag Manager or Google tag
One place for measurement reduces the risk that an advertising script bypasses the banner.
| Element | What to check | Why it matters |
|---|---|---|
| Consent banner | Cookie categories, accept and reject buttons | The visitor must have a real choice. |
| Google tags | Whether they wait for the user decision | Consent has to work before measurement. |
| Privacy policy | Tools and processing purposes | The page content should match the setup. |
CookieYes setup step by step
On a simple WordPress site this can be done without writing code, but the order matters. First configure the plugin, then connect Google integration, and only then test behaviour in the browser.
In the WordPress panel, go to plugins, add CookieYes and launch the setup wizard.
Separate necessary, analytics and advertising cookies. Do not put every script under one consent.
In Google integration settings, check support for the new advertising consent parameters.
If you use GTM, make tags react to consent status instead of firing every time.
Open the site as a new visitor, reject consent, accept it and check whether the states change.
How to check whether consent works correctly
The most common mistake is assuming the job is done because the banner is visible. In practice you still need to check script loading order. The default consent state should appear first, then the visitor decision, and only then full measurement.
Use Google Tag Assistant, Google Tag Manager preview and GA4 debug mode. After rejecting consent, advertising tags should not behave the same way as after acceptance.
- If consent changes only after a page reload, the setup needs work.
- If every tag fires before the visitor chooses, the banner is only visual.
- If you run Google Ads, test conversions and remarketing too.
Common mistakes and when to ask for help
Consent Mode v2 mistakes are often invisible on the page. They appear in data: fewer conversions, strange GA4 reports, missing remarketing signals or warnings in Google Ads.
If the site already has campaigns, forms and several marketing tools, treat the setup as a small technical project. In my SEO service, I also check analytics, tags and measurement basics, because it is hard to judge SEO or ads without reliable data.
Frequently asked questions
