Version 1.0.2 · WordPress 6.0+ · PHP 7.4+
Omea Consent documentation
Omea Consent is a free cookie consent plugin for WordPress. The scripts you add wait for consent in their category, Google Consent Mode v2 is always on, every choice is logged as proof of consent, and a cloud scan checks from the outside that nothing slips through.
Getting started
Install, activate and get the basics right.
Guides
Step-by-step how-tos for each feature.
- Add tracking scripts to WordPress that wait for consentPaste Google Analytics, Meta Pixel or any tracking snippet into Omea Consent › Scripts and it stays blocked until the visitor consents to its category.
- How to set up Google Consent Mode v2 on WordPressSet up Google Consent Mode v2 on WordPress with the free Omea Consent plugin: denied defaults before any Google tag, updates on every choice, no code.
- Consent Mode advanced vs basic: which should you use?Google Consent Mode advanced vs basic: what each sends before consent, how modelling differs, and how to switch in Omea Consent (advanced is the default).
- What is Google Consent Mode v2? A plain-English guideGoogle Consent Mode v2 explained: the four consent signals, what changed in v2, who needs it, and how a cookie banner sends it to GA4, Google Ads and GTM.
- Google Tag Manager consent mode on WordPressRun Google Tag Manager on WordPress with Consent Mode v2: load GTM after the first consent or right away, and keep non-Google tags compliant.
- GDPR cookie consent banner requirements: a checklistThe eight things a GDPR cookie consent banner must get right – prior consent, a real reject button, proof and easy withdrawal – and how to meet them.
- Stop WordPress setting cookies before consent (auto-blocking)Turn on Omea Consent's auto-blocking to hold Google Analytics, Meta Pixel, Hotjar and embeds from your theme or plugins until the visitor consents.
- Block YouTube embeds until cookie consent in WordPressHold YouTube, Vimeo and Google Maps embeds until the visitor accepts Marketing cookies, using Omea Consent's auto-blocking – no shortcode changes needed.
- How to scan your WordPress site for cookies (free)Run a free cloud cookie scan of your WordPress site: what is set before any choice, after Reject all and after Accept all, and pages without the banner.
- Auto-updating cookie policy and cookie table for WordPressGenerate a cookie policy page from your cookie scan, add the Cookie table block or shortcode, and keep the cookie list up to date automatically.
- Cookie consent records: how to prove consent (GDPR)Keep proof of cookie consent under GDPR art. 7(1) with Omea Consent's free consent log: what is stored, search by consent ID, CSV export and retention.
- Microsoft Clarity consent mode on WordPressSend Microsoft Clarity the consentv2 signal from your WordPress cookie banner so it keeps working for EEA, UK and Swiss visitors. Automatic in Omea.
- Microsoft UET consent mode for WordPress sitesSend Microsoft Advertising UET consent mode (ad_storage) from your WordPress cookie banner – also for UET tags loaded through GTM or another plugin.
- HubSpot cookie banner on WordPress: use one bannerStop showing two cookie banners on a WordPress site with HubSpot. Omea Consent hides HubSpot's banner and sends the choice to HubSpot's consent API.
- Translate your cookie banner with WPML or PolylangTranslate every Omea Consent banner and preferences text with Polylang or WPML String Translation – and why switching language never asks visitors again.
- Cookie consent categories explained: necessary to marketingThe four cookie consent categories – Necessary, Functional, Statistics and Marketing – what belongs in each, and how they map to Consent Mode.
- Add a “Cookie settings” link so visitors can change consentLet visitors change or withdraw cookie consent from your footer or menu: link to #omea-consent-preferences, add an attribute, or call a function.
- Customise the cookie banner: layout, colours and textsChange the Omea Consent banner's position, theme, colours and texts in WordPress, with a live preview – plus how long a choice is remembered.
Troubleshooting
When something doesn't work as expected.
- How to check Google Consent Mode v2 is workingCheck Google Consent Mode v2 on your WordPress site in two minutes: read the gcs and gcd parameters, use Tag Assistant, and spot the usual setup mistakes.
- Cookie banner not showing in WordPress? 7 fixesOmea Consent banner not appearing? Check for a saved choice, hidden roles, another banner plugin, script-delay settings and pages WordPress doesn't serve.
- Tracking scripts not running after consent: how to fix itAnalytics or a pixel not firing after visitors accept cookies? Check the script's category, location, Enabled switch and snippet in Omea Consent.
- Why the cookie banner asks visitors againOmea Consent asks again when a choice expires (180 days by default) or when the banner texts change. Here's what counts as a change and how to control it.
FAQ
Short answers to common questions.
- Omea Consent FAQ: free cookie consent plugin for WordPressAnswers about Omea Consent: is it really free, what Pro adds, what data leaves your site, caching, WooCommerce, languages and requirements.
- Which cookies does Omea Consent set?Every cookie and storage key Omea Consent uses – omea_consent_state, omea_consent_id and the WP Consent API cookies – with purpose and lifetime.
- WP Consent API explained: what it does and whyWhat the WordPress Consent API is, how plugins use wp_has_consent() to respect the cookie banner, and how Omea Consent passes every choice to it.