Cookease logo
Cookease logo

All articles

Consent mode shows inactiveUpdated a month ago

When this happens

After installing and configuring Cookease on Shopify, you may use some Google reporting tools that show that consent mode is inactive.


INFO

In most cases, this is caused by one of these two situations:

  • You’re testing from a location where the Cookease cookie banner is not shown, so Consent Mode won’t appear active.

  • Consent Mode is working, but Google’s reporting (GA4 / Google tools) hasn’t updated yet.


Before you start: verify the Cookease banner is actually showing

Consent Mode can only be detected reliably when the cookie banner is shown to the visitor. If the banner isn’t showing (for example, because you’re testing from a location where it’s disabled), most tools will report Consent Mode as not active.

What the banner should look like

On your storefront, the Cookease cookie banner typically includes:

  • Manage preferences

  • Accept

  • Optionally Decline (if enabled)


TIP

If you’re not seeing the banner, test in a private/incognito window and refresh the storefront page.


Step 1 — Test from a location where the banner is enabled

1. Open your storefront in a private window - Open a private/incognito browser window and visit your storefront homepage.

2. Confirm the cookease cookie banner appears - Make sure you can see the Cookease cookie banner with Manage preferences and Accept (and Decline if you’ve enabled it).


NOTE

If the banner doesn’t appear in your test session, Consent Mode checks will usually look “inactive” because no consent state is being collected from that visitor.


Step 2 — Confirm Cookease is enabled in your Shopify theme

Cookease’s banner settings live in your Shopify theme settings. Use the same path you’d use to control banner options like the Decline button.

1. Open Cookease in Shopify - In your Shopify admin, go to Apps > Cookease, then select Enable Cookease in your theme.

2. Review your banner related settings - In the theme settings area, confirm the cookie banner is configured the way you expect for your storefront. For example, you can control whether customers see a Decline option using Decline All Button set to Show or Hide.

Show the Decline button


WARNING

If Cookease isn’t enabled in the current published theme, the banner may not appear on your storefront—causing Consent Mode tools to report “inactive.”


You can use a consent debugging plugin (for example, Consent Mode Inspector) to verify whether Consent Mode is active and whether signals are being sent as expected.

What the “gcs” values mean

Some tools show a gcs value representing the current consent status:

  • G100: ad_storage denied, analytics_storage denied

  • G110: ad_storage granted, analytics_storage denied

  • G101: ad_storage denied, analytics_storage granted

  • G111: ad_storage granted, analytics_storage granted


TIP

Run your test again after interacting with the banner (for example, selecting Accept or opening Manage preferences) to see whether the consent state changes.


If the tool still shows issues

If your consent checking tool shows errors or doesn’t detect Consent Mode even when the banner is showing:

  • Re-check that you completed all Cookease configuration steps in Shopify and that Cookease is enabled on the correct (published) theme.

  • Confirm you are testing from a location where the cookie banner is enabled.

Even when Consent Mode is set up correctly, Google tools and reporting may continue to show that Consent Mode is not enabled for a period of time.


NOTE

Google’s modeling and reporting may require time to “learn” from your data after installation. Based on real-world timelines, this often takes at least 4 weeks, and can take up to 10 weeks depending on traffic volume.


Q. What’s the most common cause?

Either:

  • Misconfiguration (Cookease not enabled in the published theme, banner not showing in the test session, or incomplete configuration), or

  • Google-side delay (reporting/modeling not updated yet).


Q. What should I do if everything looks correct but GA4 still doesn’t reflect it?

A. If your storefront shows the Cookease banner and your consent inspector tool shows valid consent states (for example, G100 before consent and G111 after Accept, depending on your setup), the remaining gap is usually Google reporting latency.

In that case, allow time for Google’s reporting to update as more traffic and consent interactions are collected.

Was this article helpful?
Yes
No