Skip to content

30 days free · no card needed

Cookie consent for Google Tag Manager

we read your container

← Cookie Rocks for your stack

Cookie Rocks reads your public Tag Manager container, lists the tools it loads and adds them to your cookie policy. Then it tells you which tags to make wait.

The Cookie Rocks logo: a cookie made of stone

How Cookie Rocks works with Google Tag Manager

Container read for you

Your container ID is found on your pages, in Site Kit and in GTM4WP. The public container file is read once a day, without a Google account. Paused tags are ignored.

Tools declared by themselves

A tool newly found in the container is declared automatically and appears in your cookie policy. You can untick it.

Data layer events

cr_consent_ready on every page and cr_consent_update after each choice, with cr_consent.marketing and cr_consent.statistics, for your triggers.

What to set, listed

The Overview page lists the tools loaded through Tag Manager that must wait for consent there: Meta, LinkedIn, Hotjar and the rest.

Free Audit and Cookie Rocks Pro, with Google Tag Manager

Cookie Rocks Audit, free

Finds your container on your pages, in Site Kit and in GTM4WP, reads it once a day and declares the tools it loads in your cookie policy. What the Audit checks.

Cookie Rocks Pro

Sends the visitor’s choice to Clarity, Microsoft Advertising and Matomo, holds the Tag Manager script in basic mode and pushes two data layer events. All the features.

Good to know

  • Tags other than Google’s inside the container must be made to wait in Tag Manager itself.

Questions

Does Cookie Rocks block the tags inside my container?

Google tags follow Consent Mode by themselves. The others (Meta, LinkedIn, Hotjar…) must wait in Tag Manager: use a Custom Event trigger on cr_consent_update, or Tag Manager’s own consent checks.

Do I need a Google account or API access?

No. Cookie Rocks reads the public container file that your pages already load.

Is reading the container part of the free audit?

Yes. It works with or without the paid plugin, and up to three containers are read.

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For Tag Manager users

See what your container really loads.

no google account needed

The free Audit reads your container today. The complete plugin adds the data layer events and the signals, free for 30 days.

  • During the trial: everything, including the full settings and the scans
  • After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
  • What waits for a key: most settings, updates and support

How the trial works, in detail

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.