Written for Cookie Rocks 2.10.0, checked on 5 November 2026. The current version is 2.11.2: some details may have changed.
Most WordPress sites run Google tags, a page cache, a page builder or a multilingual plugin. Each page of this section shows how to set up one of these tools with Cookie Rocks.
The free Cookie Rocks Audit adds no script and no style to your visitors’ pages. It reads your site from the administration and changes nothing your visitors receive.
Set it up in 3 steps
- Open Cookie Rocks, Cookies, and click Scan my pages. The Audit then knows which tools your pages use.
- Open the Developers page. In the Compatibility table, the On this site column shows the version of each tool installed on your site.
- For each tool you use, open its page below and follow its own 3 steps.
The integration pages
- Google Consent Mode, Tag Manager and Site Kit: the Google tags on your pages, the signals they receive, and what your Tag Manager container loads.
- WP Consent API: how Site Kit, WooCommerce and other plugins read the visitor’s choice.
- Pixel Manager for WooCommerce: the three settings that let it follow the visitor’s choice itself.
- Caching plugins: page caches, optimisation plugins and delayed scripts.
- Divi and Elementor: page builders, their videos and forms.
- WPML and Polylang: the languages of your site, translated policies and the language of the banner.
Forms protected by reCAPTCHA, embedded videos and maps, and tools such as Microsoft Clarity or Matomo are covered on the Cookies page. The cookie plugins whose banner and settings the Audit reads are listed on Cookie plugins.
Tip. A tool missing from the Compatibility table can still work. The table only lists what was tested.
What the Audit reads
- The pages opened by the scan, as a visitor receives them.
- The settings of other plugins, stored in your database: your cookie plugin, Site Kit, your Tag Manager plugin.
- Your public Google Tag Manager container, the same file every visitor downloads from Google.
How each tool is tested
Each line of the Compatibility table gives the version tested and how:
- Tested at each version: tested automatically before every release of Cookie Rocks.
- Tested on a live site: tried on a real site, with the date and the version.
- Tested automatically with its latest version: tested around each Cookie Rocks version with the latest version from WordPress.org.
- Reproduced in the tests: its behaviour is imitated in the tests, not the plugin itself.
- Written from its documentation: built from the publisher’s documentation, not yet tried on a real site.
A newer version of a tool usually works. It is tested for the next release of Cookie Rocks.
With Cookie Rocks Pro
For site owners, tool by tool: Cookie Rocks solutions.
Next step: Google Consent Mode, Tag Manager and Site Kit.