Cookie Scout

By cookiescout

0+ active installationsVersion 1.0.24

Cookie banner for WordPress with GDPR consent, script blocking and Google Consent Mode v2.

Description

Cookie Scout is a WordPress cookie banner plugin that helps you collect consent, block scripts until the visitor has chosen, and connect that choice to Google Consent Mode v2. You can use the plugin locally without an account. Advanced features, including automatic scanning and consent logging, can be enabled when you connect the site to a Cookie Scout account.

Key features

  • A cookie banner that stores the visitor’s choice and lets the visitor open the choice again later.
  • Banner and consent text in six built-in languages: Danish, English, German, Spanish, Norwegian and Swedish.
  • Script blocking for statistics and marketing until consent is given. Necessary scripts, for example login and payment, can still run.
  • Iframe placeholders, including YouTube. After a valid consent saved in the browser, embeds can be shown again without asking the visitor to accept a second time.
  • Google Consent Mode v2, with the standard and advanced behaviour described in the plugin settings.
  • Optional loading of Google Tag Manager from a container ID in the format GTM-. The plugin can also detect server-side or hosted gtm.js, for example on your own domain or via Stape, and apply the same consent rules.
  • A dataLayer event named cookie_consent_update, compatible with Cookiebot, so existing Google Tag Manager triggers can be reused when you switch.
  • A basic scanner in wp-admin that fetches your site’s public HTML when an administrator starts it. Categories can be reviewed and adjusted afterwards.
  • Automatic scanning and categorisation when the site is connected to a Cookie Scout account. Cookie Scout sets the categories from the scan, and you can still adjust them.
  • Cookie policy and cookie list shortcodes, [cookie_scout_policy] and [cookie_scout_list], so the policy can follow what the scanner found (purpose, provider and expiry). You can also place [cookie_scout_consent] to let visitors open the banner again. An optional Google font can be chosen for the policy and list appearance.
  • Optional connected mode, with consent logging to your account at dashboard.cookiescout.io.
  • Fixed fallback rules for payment scripts, including ePay, Bambora and Worldline domains, categorised as necessary so checkout can work when optional cookies are rejected.

Why Cookie Scout

Cookie Scout is a Danish cookie consent product built for WordPress, for site owners and agencies whose visitors are in the EU and the EEA.

Setup is meant to stay simple. Install the plugin, open Cookie Scout in wp-admin, and complete the quick setup. You can run it locally first, then connect the site to the dashboard when you want an account, scanning and a consent log.

It costs far less than alternatives like Cookiebot. See the current price on cookiescout.io/priser.html.

If you are switching from Cookiebot, you can keep existing Google Tag Manager triggers that listen for cookie_consent_update. Install and set up Cookie Scout first, show the new banner, then turn Cookiebot off so visitors only see one banner.

WooCommerce

Cookie Scout works on a WooCommerce shop as a WordPress plugin. Put one banner in place before statistics and marketing run on product, cart and thank-you pages. Cart, checkout and login cookies can still run when they are only used to complete the purchase. Marketing pixels, including on the order confirmation page, should wait for consent.

The plugin includes fallback rules for ePay, Bambora and Worldline payment scripts, categorised as necessary, so checkout can still load when the visitor rejects optional cookies. If a marketing script is bundled with the payment module, move that marketing script so it waits for consent.

If both your theme and the plugin load the same Google Tag Manager container, shop tags can fire twice. Let only one path load the container. After you save settings, clear page cache, CDN and optimisation plugins, then test reject, accept and withdrawal in a private window.

This helps you set the shop up carefully. It is not legal advice about which cookies are strictly necessary on your shop.

Learn more about Cookie Scout at cookiescout.io.

External services

This plugin communicates with third-party services only when a feature explicitly needs it, or when an administrator has turned that feature on. Below is what is used, why, what data is involved, and when it runs.

Cookie Scout API (dashboard.cookiescout.io)

  • What it is: The Cookie Scout account and configuration service.
  • What it is used for: Optional connected mode: authenticating the site owner, loading banner and policy configuration, blocking rules, categories, and (when enabled) recording consent events from the banner to your Cookie Scout account.
  • What data is sent: API requests may include your site URL, authentication token after you connect, banner or policy fields you save from the settings screens, and consent payloads (consent identifier, category choices, banner version reference, page URL, and language) when the visitor consents and connected mode is active.
  • When it is sent: Only when a site administrator has connected the plugin to a Cookie Scout account and performs actions that require the service, or when visitors submit consent while that connected mode is active.
  • Provider: Cookie Scout — Website — Account dashboard — Terms of use — Privacy policy

Google Tag Manager and Google Tag (googletagmanager.com)

  • What it is: Google’s tag hosting and execution platform.
  • What it is used for: If an administrator enters a valid Google Tag Manager container ID (format GTM-…) in the plugin settings, the plugin can load Google Tag Manager on the public site in line with the selected Consent Mode behaviour (standard vs advanced). The browser may then load additional tags configured in that container.
  • What data is sent: The plugin requests Google’s gtm.js (and the GTM noscript iframe when applicable) from Google. Any further requests, cookies, or personal data depend entirely on what the administrator has configured inside Google Tag Manager and the tags fired from it—not on this plugin’s code paths beyond loading GTM when allowed by consent settings.
  • When it is sent: When GTM is configured in settings and, depending on mode, when consent allows statistics or marketing storage, or when advanced Consent Mode is enabled as described in the plugin UI.
  • Provider: Google Ireland Limited / Google LLC — Google Tag Manager terms — Google privacy policy

Google Fonts (fonts.googleapis.com / fonts.gstatic.com)

  • What it is: Google’s font delivery network.
  • What it is used for: If an administrator selects one of the listed Google fonts for the cookie policy / cookie list appearance, the visitor’s browser loads the corresponding stylesheet (and font files) from Google.
  • What data is sent: Standard web requests as defined by Google (typically IP address and technical headers as part of loading CSS/font assets).
  • When it is sent: Only when a Google font is chosen in settings and a page that outputs the policy or list shortcodes is viewed.
  • Provider: Google — Google Fonts privacy FAQ — Google privacy policy

Stripe (checkout.stripe.com)

  • What it is: Payment processing for Cookie Scout plans, when you use connected checkout from the plugin.
  • What it is used for: Redirecting the administrator to Stripe Checkout when purchasing or upgrading through the Cookie Scout service.
  • What data is sent: Handled by Cookie Scout’s checkout API and Stripe according to their flows; this plugin only redirects the administrator to the checkout URL returned by the service.
  • When it is sent: Only when an administrator starts checkout from the plugin while using connected mode.
  • Provider: Stripe — Stripe legal / privacy

Front-end requests to your own site (scanner / GTM detection)

  • What it is: The plugin may request your site’s public HTML using wp_remote_get() (for example the basic scanner in admin, or optional detection of an existing GTM snippet).
  • What it is used for: Analysing HTML your site already outputs; the plugin does not substitute remote CDNs for its own assets through these requests.
  • What data is sent: A normal HTTP GET to your home_url() as seen by the server (user-agent identifies the plugin).
  • When it is sent: Only when an administrator triggers the relevant tool in wp-admin.

Installation

  1. Install Cookie Scout from the Plugins screen in WordPress, or upload the plugin to /wp-content/plugins/.
  2. Activate the plugin under Plugins.
  3. Open Cookie Scout in the WordPress admin and complete the quick setup. The plugin can be used locally without an account. Advanced features can be turned on separately. The dashboard at dashboard.cookiescout.io is the customer account when you connect the site.
  4. Set up the cookie banner so statistics and marketing wait until the visitor has chosen. Necessary scripts, for example login and payment, can still run.
  5. Start the basic scanner in wp-admin. It fetches the site’s public HTML when an administrator starts it. Review the categories and adjust them if needed.
  6. Add the cookie policy and cookie list to a page with the shortcodes [cookie_scout_policy] and [cookie_scout_list], so the policy can follow what the scanner found. You can use [cookie_scout_consent] if you want a link or button that opens the banner again.
  7. If Cookie Scout should load Google Tag Manager, enter a container ID in the format GTM- in the plugin settings and choose standard or advanced Consent Mode behaviour as the plugin UI describes. If your theme already loads the same container, let only one path load it.
  8. Optional: connect the site to a Cookie Scout account when you want account features, automatic scanning and consent logging.
  9. Clear page cache, CDN and optimisation plugins after you save. Open the site in a private window and test reject, accept and withdrawal. If another cookie banner is still running as a plugin, in the theme or as a tag, turn it off so visitors only see one banner.

FAQ

Which languages are included?

The cookie banner and consent text include six built-in languages: Danish (Dansk), English, German (Deutsch), Spanish (Español), Norwegian (Norsk) and Swedish (Svenska). The Language tab offers the same six languages and lets you configure languages and shared cookie settings for multilingual sites.

Cookie Scout maps the WordPress site language to the matching banner language. Both US and UK English use English; both Norwegian Bokmål and Nynorsk use the Norwegian option. Unrecognised WordPress locales fall back to English.

These six languages apply to the banner and consent text. The administration interface is written in Danish, and the plugin package includes an English translation file. Additional administration translations are provided through WordPress.org when available.

Does the plugin require an account?

No. The plugin can be used locally without an account. Advanced features can be enabled separately. Connect the site to a Cookie Scout account when you want the dashboard, automatic scanning and a consent log.

Does Cookie Scout support Google Consent Mode v2?

Yes. Cookie Scout supports Google Consent Mode v2 on WordPress and can connect the visitor’s choice to Google tagging. In the plugin settings you can enter a Google Tag Manager container ID in the format GTM- and choose standard or advanced behaviour as the plugin UI describes. Consent Mode tells Google about a choice. It does not replace a valid cookie banner, and it is not a legal assessment of your site.

Does it work with WooCommerce?

Yes. Cookie Scout is a WordPress plugin and can show a banner on a WooCommerce shop, keep statistics and marketing waiting until consent, and still allow necessary checkout and payment scripts to run. Changelog 1.0.13 added fallback rules for ePay, Bambora and Worldline payment scripts, categorised as necessary, so checkout can work when optional cookies are rejected. Test the cart and checkout in a private window after you reject marketing cookies. You still need to judge which cookies are necessary on your own shop.

Can I switch from Cookiebot and keep my Google Tag Manager triggers?

Yes, for triggers that listen to the cookie_consent_update event. From version 1.0.4 the plugin also sends that Cookiebot-compatible dataLayer event on consent, so existing triggers can be reused. Install Cookie Scout and show the new banner first, then deactivate the Cookiebot plugin or remove the Cookiebot script. Turn off any Cookiebot tag in Google Tag Manager, clear cache, and test in a private window so only one banner is shown. Other Cookiebot events are not documented here.

How does Google Tag Manager integration work?

If you enter a valid container ID in the format GTM- in the plugin settings, Cookie Scout can load Google Tag Manager on the public site in line with the Consent Mode behaviour you select (standard or advanced). The plugin can also detect server-side or hosted gtm.js, for example on your own domain or via Stape. If the theme already loads a container, do not let the plugin load the same one a second time. Further tags, cookies and data then depend on what you have configured inside Google Tag Manager.

What happens to YouTube embeds before consent?

Scripts and iframes can be blocked until the visitor has chosen, and the plugin can show iframe placeholders, including for YouTube. From version 1.0.9, a valid consent stored in the browser is applied again on reload, so YouTube can be shown without the visitor having to accept a second time.

Does Cookie Scout make my site compliant with GDPR or cookie rules?

Cookie Scout helps you display a cookie banner, collect a choice, block scripts until that choice is made, document consent when connected mode is active, and send Consent Mode signals to Google. That can help you work towards the requirements in GDPR and cookie or ePrivacy rules. It is not legal advice and not a guarantee that your site is compliant. You remain responsible for how the banner, blocking and cookie policy are set up on your site.

Where is consent stored?

Without an account, the visitor’s choice is stored in the browser, so the banner can remember it on a later visit. When the site is connected to a Cookie Scout account and connected mode is active, a consent event can also be sent to your account. That payload may include a consent identifier, category choices, a banner version reference, the page URL and the language. You are the data controller for your visitors. Cookie Scout is a processor for the consent log when the site is connected to an account.

Screenshots

Changelog

1.0.24

  • Language in a folder (for example /en/) is registered as a language domain, not only subdomains.

1.0.23

  • Fix: the reopen button keeps its fixed size and round shape even when the theme or Elementor applies global button styles.

1.0.22

  • The language tab now shows verification status for language domains (verified, pending, or could not be verified).

1.0.21

  • Fix: clearing the cache now also works with a Redis or Memcached object cache (a cache epoch in every key).

1.0.20

  • Fix: “Clear cache” now clears the cache for every domain and language (WPML and multi-domain), not only the admin domain.

1.0.19

  • Admin: added a Language section for WPML and other multilingual plugins, for domain and language management.

1.0.18

  • Language: added Norwegian and Swedish locale mapping in the WordPress plugin.

1.0.17

  • WPML and multi-domain: API calls send the current host and locale, and the banner, policy, category and blocker cache is now domain- and locale-aware.

1.0.16

  • Security: the connect flow now requires nonce verification before the API token is saved; consent JSON is sanitised and validated field by field before API calls.

1.0.15

  • Plugin Check: fixed GTM notice escaping, sticky form fields with nonce verification, User-Agent sanitisation and Google Fonts enqueue version.

1.0.14

  • Plugin Check: Tested up to WordPress 7.0; fixed i18n translators comments; removed load_plugin_textdomain; PHPCS adjustments for templates, passwords and admin GET flows.

1.0.13

  • Script blocking: added fixed fallback rules for payment scripts (including ePay/Bambora/Worldline domains) categorised as necessary, so checkout can work when optional cookies are rejected.

1.0.12

  • Compatibility: removed PHP 8 match in the settings template and replaced it with switch, to avoid parse errors on older PHP.

1.0.11

  • Banner: larger cookie icon in the floating reopen button and CSS that resists theme button/svg scaling; a little more space for the banner logo.

1.0.10

  • Script blocking: GTM detection now covers server-side / hosted gtm.js (for example your own domain with ?id=GTM- or Stape verticals), so the same consent rules as for googletagmanager.com GTM apply and scripts avoid incorrect “unknown” blocking.

1.0.9

  • Script blocking: on reload with valid consent in localStorage, that consent is now applied to the DOM (iframe placeholders and blocked scripts), so for example YouTube is shown without having to accept again.

1.0.8

  • Script blocking: skip the server-side buffer when the User-Agent contains CookieScoutRemoteScan/1 (backend Playwright scanner and wp_remote_get in the plugin), so scanning sees executable tags in the HTML.

1.0.7

  • Banner: schedule boot with DOMContentLoaded plus a short poll, so init is not skipped if markup arrives after the script (avoids a “dead” front end with certain themes/cache).

1.0.6

  • Banner: boot also runs if the DOM is already ready (avoids a hidden banner when the script loads late). Important for GTM/script blocking and for external scans.

1.0.5

  • Banner: consistent bottom padding in the cookie settings panel (matches sides/top).

1.0.4

  • dataLayer: also dispatches cookie_consent_update (Cookiebot-compatible) on consent, so existing GTM triggers can be reused.

1.0.3

  • Correct Cookie Scout terms/privacy URLs in readme; shortcode return hardening (esc_html__, wp_kses_post); safe shutdown flush for script-blocker output buffer.

1.0.2

  • Stricter escaping (admin UI, banner colours/position), check_ajax_referer on privileged AJAX, hex colour validation, connect-code format check, domain-list documentation, removed inline onclick confirm in favour of enqueued admin JS.

1.0.1

  • Hardened AJAX and checkout return URLs (nonces), improved script loading and output escaping for consent/blocker/GTM, removed frontend “Powered by” credit, admin settings scripts enqueued properly, readme external services documentation.

1.0.0

  • First public release