# Cookie consent for WordPress websites A clear way to manage consent, measurement and third-party scripts **Coma Cookie Consent** is a WordPress plugin we built to give visitors a clear choice and site owners a practical way to manage consent, cookies and third-party scripts. **Free plugin with no licence fee** – download it, use it and adapt it for your WordPress website. - **Google Consent Mode v2** with default denied analytics and ad storage signals - **Cookie table** combining information found on the site with recognised entries - **Third-party tracker blocking** until the visitor makes a choice - **Latvian, Russian and English** with WPML or Polylang detection - **Revisit button** so visitors can change their consent settings later - **GPL-2.0 licence** – there is no monthly fee for the plugin itself You can install it yourself or ask us to handle installation, configuration and testing. Our help is a separate service – the plugin itself is free. [Download the free plugin](https://github.com/Coma-Web-Development/coma-cookie-consent) [![Coma Cookie Consent cookie notice on coma.lv](https://coma.lv/wp-content/uploads/2026/08/coma-cookie-consent.jpeg)](https://coma.lv/wp-content/uploads/2026/08/coma-cookie-consent.jpeg) ## What problem does the plugin solve? On many websites, analytics, advertising pixels, remarketing scripts and other external tools are loaded from different places. Visitors cannot easily see what is happening, while developers have to check whether the visitor’s choice really affects the scripts. Coma Cookie Consent brings this process together in one WordPress plugin. It helps display the choice, send consent signals, show detected cookies and stop recognised non-Google trackers until a choice is made, when blocking is enabled. ### Consent signals Google Consent Mode v2 sends default denied signals for analytics and ad storage, then updates them according to the visitor’s choice. ### Cookie overview The plugin checks document.cookie and loaded tracker scripts. Known cookies receive a description and duration from the built-in database, while the rest are shown as unclassified. ### Script control When enabled, recognised scripts from Meta, TikTok, LinkedIn, Hotjar, Clarity, Yandex and other services are held until the relevant choice is given. ## How does it work for visitors? 1. **The notice appears.** Visitors see that the site uses cookies. They can accept all, reject optional cookies or open the settings. 2. **Choices are split into categories.** Necessary cookies remain active. Analytics and marketing categories can be enabled or left disabled. 3. **Signals are updated.** After a choice, the plugin sends the relevant Consent Mode signals and activates recognised scripts for which the visitor has given consent. 4. **Settings can be changed later.** A floating settings button lets visitors reopen their preferences and change the choice. The administrator can set how long consent remains valid before it must be confirmed again. The default is 180 days, but this can be changed to fit the site’s policy. ## What can be configured in the admin area? - Default language and notice text in Latvian, Russian and English - Notice position, colours and the option to show the revisit settings button - Analytics and marketing category settings - Privacy policy URL for each language - Google Analytics ID and the option for the plugin to load gtag.js - Server-side consent log with time, choice, version, language and a salted hash of the IP address - Global mode or a regional mode for the EEA and the United Kingdom ## How to install it? 1. Download the plugin folder from the [GitHub repository](https://github.com/Coma-Web-Development/coma-cookie-consent) using *Code → Download ZIP*. 2. Upload the coma-cookie-consent folder to wp-content/plugins or install the ZIP file in the WordPress admin area. 3. Activate the plugin under **Plugins**. 4. Open **Settings → Cookie Consent** and fill in the language, privacy policy and consent settings. 5. Test the site in a private browser window. Check not only the notice, but also which scripts load before and after the choice. If Google Analytics or Google Tag Manager is already loaded by the theme or another plugin, do not enable an additional Analytics load in this plugin. It can result in duplicate loading. ## Important boundaries The plugin is a technical consent management tool. It does not replace a privacy and cookie policy prepared for the site, a data processing assessment or correct third-party tool configuration. - The plugin is not an IAB TCF v2.2 or Google-certified CMP. If the site needs personalised Google advertising in the EEA, separate requirements must be assessed. - Google scripts are not held in the same way as ordinary non-Google tracker scripts. They are controlled through Google Consent Mode signals. - Scripts inserted by Google Tag Manager after the page loads must be configured in GTM with the appropriate consent triggers. - The cookie table helps explain the technical situation, but it is not a complete legal audit by itself. ## Who is it useful for? - Business websites with analytics, advertising or remarketing tools - WooCommerce stores using external payment, marketing or analytics services - Multilingual WordPress sites where the notice language must follow the visitor’s current language - Agencies that need a repeatable starting point for configuring consent for clients Installing the plugin is only one part of the work. Before launch, check which scripts are on the site, what loads them and whether each category reflects the actual data processing. ## Frequently asked questions **Does the plugin block all cookies?** No. Necessary cookies remain active. When tracker blocking is enabled, the plugin holds recognised non-Google tracker scripts until the relevant consent is given. Custom scripts may need a separate integration. **Does the plugin replace a privacy policy?** No. The site still needs privacy and cookie policies that match its actual data processing. The plugin can store a link to these policies for each language. **How is the notice language selected?** The plugin checks the current Polylang language first, then the WPML language code. If neither is available or the language is not supported, it uses the plugin’s default language. **Does the plugin work with Google Tag Manager?** Yes, but tags inserted by GTM must be configured in Google Tag Manager with consent triggers. The plugin cannot safely manage every script that GTM adds after the initial HTML response. **Does the plugin make a website legally compliant automatically?** No. The result depends on the site’s cookies, tools, privacy documents, region and configuration. The plugin helps implement the technical choice and signals, but it does not replace legal assessment. **Can Coma help with installation?** Yes. We can install the plugin, check the actual scripts and cookies, configure Consent Mode and help set up consent in GTM. ## Need help with implementation? Tell us which analytics, advertising or other external tools are used on your WordPress website. We can install the plugin, test the consent flow and explain what else needs to be configured separately. [Contact us](https://coma.lv/contacts/)