- SureCookie Installation Guide
- Installing SureCookie Pro
- Updating SureCookie
- How to Set Up SureCookie: Onboarding Wizard Guide
- SureCookie Dashboard Overview
- Connecting Your Site to SureCookie (Scanner Setup)
- Using SureCookie on Multiple Sites
- Uninstalling SureCookie & Data Cleanup
- SureCookie Shortcodes Reference
- Preferences Settings (Menu, Branding, Analytics)
- Customizing Banner Content
- Customizing Banner Layout
- Custom CSS for Banner Styling
- How to Configure the Floating Widget
- Customizing the Preference Modal
- Controlling Where the Cookie Banner Appears
- Customizing Banner Colors (Custom Colors, WCAG)
- Customizing the Blocked Content UI
- Banner Text in the Wrong Language (WPML, Polylang, and Locales)
- Re-Consent
- Understanding SureCookie Logs
- How to Set Up Geographic Targeting
- Block Scripts Until Consent (Resource Blocking)
- Setting Up Google Consent Mode v2
- Consent Models Explained (Opt-in vs Opt-out)
- Exporting Consent Logs (PDF Proof + CSV)
- Consent & Data Settings (Duration, Retention, Renew)
- Consent Forwarding Across a Multisite Network
- Resource / Script Blocking (Add Embeds + Fixes)
- Troubleshooting SureCookie
- Fix a Stuck or Failed Cookie Scan
- Why Some Cookies Aren’t Detected
- Banner Not Appearing: Troubleshooting
- Settings or Cookie Categories Not Saving or Loading
- Embeds Blocked After Consent (YouTube, Maps, Vimeo)
- Site Performance / Page Speed
- Scanning Your Site From Your Browser
- Importing and Exporting SureCookie Settings
- Verifying Your Domain With a DNS Record
How SureCookie Honors Global Privacy Control (GPC)
Global Privacy Control (GPC) is a privacy setting in the visitor’s browser. When it is on, the browser tells every site it visits not to sell or share the visitor’s data. Visitors set it once, or their browser has it on already, so it reaches your site before your banner appears.
SureCookie honors the signal automatically. It is part of the free plugin, and there is nothing to set up. This article explains what changes for visitors who send the signal, how to test it, and the questions site owners ask most.
Note: This article describes SureCookie 1.8.0 and later. Version 1.7 and earlier behave a little differently; see Changes in SureCookie 1.8.0 below.
Why It Matters
Several US state privacy laws, including California’s CCPA/CPRA and Colorado’s privacy act, require the businesses they cover to treat a browser opt-out signal such as GPC as a request to opt out of the sale or sharing of personal data and of targeted advertising. A visitor who sends the signal should not have to click anything on your site to opt out.
Whether these laws cover your site depends on where your visitors live, what you do with their data, and the size of your business. Confirm what applies to you with your legal counsel. For the California setup, see CCPA / CPRA Compliance with SureCookie.
Which Browsers Send the Signal
- Brave: On by default.
- DuckDuckGo: On by default in its browser apps and extensions.
- Firefox: On by default in every private window. In normal windows, visitors turn it on under Settings → Privacy & Security → Tell websites not to sell or share my data.
- Chrome, Safari and Edge: No built-in setting. Extensions such as Privacy Badger and DuckDuckGo Privacy Essentials send the signal.
What SureCookie Does With the Signal
SureCookie checks for the signal in the visitor’s browser on every page, and in each request the browser sends to your server. It applies to every visitor who sends it, in every region and consent model, and it outranks any choice the visitor makes on the banner.
| Category | While GPC Is On |
|---|---|
| Essential Cookies | Always allowed |
| Functional Cookies | Follows the visitor’s choice |
| Analytics Cookies | Blocked, whatever the visitor chooses |
| Marketing Cookies | Blocked, whatever the visitor chooses |
| Uncategorized and custom categories | Blocked, whatever the visitor chooses |
Essential and Functional content delivers what the visitor came for, so the signal leaves it to the visitor’s choice. Analytics, Marketing and anything SureCookie cannot classify stay blocked while the signal is on.
Everywhere SureCookie Shares Consent
The same rule reaches every place SureCookie tells other tools about consent:
- Scripts and embeds: Blocked items stay blocked, even after Accept All. This works on cached pages too, because the check runs in the browser.
- Placeholders: A placeholder for blocked content replaces its text with “Your browser is set to tell websites not to sell or share your data, so this content stays blocked.” It also drops the Accept & Load button, which could not load the content.
- Google Consent Mode:
ad_storage,ad_user_data,ad_personalization,personalization_storageandanalytics_storageare sent as denied.functionality_storagefollows Functional Cookies. - WP Consent API:
statisticsandmarketingread as denied, andpreferencesfollows Functional Cookies. See WP Consent API Compatibility. - Microsoft Clarity and PixelYourSite: They are told consent is denied for the blocked categories.
What Stays the Same
- The banner still appears. SureCookie does not hide the banner or show a separate GPC message. The visitor’s choice still applies to everything the signal does not cover.
- The consent log records the visitor’s choice. It stores what the visitor clicked. It does not record that the signal was present.
- The choice is kept. If the visitor later turns the signal off, their saved choice applies again from the next page.
Pro Settings Do Not Override It
SureCookie Pro settings that relax consent never apply to a visitor who sends the signal:
- Geographic Rules: A visitor in a region with no banner, or with an opt-out default, still has Analytics and Marketing blocked.
- Allow Tracking Scripts on Excluded Locations: On pages where you hide the banner, scripts stay blocked for these visitors. See Controlling Where the Cookie Banner Appears.
How to Test It
Use a browser that sends the signal, such as a Firefox private window or Brave.
- Open your site in that window.
- Press F12 to open the developer tools, and open the Console tab.
- Type
navigator.globalPrivacyControland press Enter. It returnstruewhen the signal is on. - Click Accept All on the banner.
- Check that blocked embeds show the browser-signal message instead of Accept & Load.
- Open the cookie list (Storage → Cookies in Firefox, Application → Cookies in Brave) and confirm that tracking cookies such as
_gaor_fbpare not set.
To see what other visitors get, repeat the test in a window where navigator.globalPrivacyControl returns false or undefined, such as a normal Chrome window without privacy extensions.
Tip: Clear your site’s cookies between tests, so a choice from an earlier test does not carry over.
Changes in SureCookie 1.8.0
Version 1.8.0 narrowed the signal to what it is about and made it visible to visitors.
| Behavior | 1.7 and Earlier | 1.8.0 and Later |
|---|---|---|
| Functional content | Blocked | Follows the visitor’s choice |
| Placeholder for blocked content | Shows Accept & Load, which does nothing | Explains the signal, with no button |
WP Consent API preferences | Denied | Follows Functional Cookies |
getConsentSummary() | Lists the recorded choice as allowed | Lists only what is allowed, plus effectivePreferences |
If you are on 1.7 or earlier, update SureCookie to get these changes. See Updating SureCookie.
Frequently Asked Questions
Visitors click Accept All, but a video, map or widget stays blocked. Why?
Their browser sends GPC, and the content is in a category the signal blocks, usually Marketing. The placeholder says so. Most embeds, such as YouTube and Google Maps, share data with their provider, so keep them where they are.
If the content does not track visitors, you can change its category under SureCookie → Tracking Manager → Scripts and Embeds. Click the edit icon on its row, choose a Category, click Update, then click Save. Choose Functional Cookies for content visitors ask for, or Essential Cookies only when your site cannot work without it, because Essential loads before any choice.
It works in Chrome but not in Firefox or Brave.
Brave sends the signal by default, and Firefox sends it in private windows. Run navigator.globalPrivacyControl in the console of the window that fails. If it returns true, SureCookie is honoring the signal as intended.
I turned off the Firefox setting, and it still happens.
The checkbox in Firefox’s settings controls normal windows only. Private windows send the signal unless privacy.globalprivacycontrol.pbmode.enabled is set to false in about:config. If a normal window still returns true with the setting off, an add-on such as Privacy Badger or DuckDuckGo Privacy Essentials is sending it. Open Help → Troubleshoot Mode in Firefox to test with every add-on switched off.
The consent cookie says analytics is true, but nothing loads.
The surecookie_user_consent cookie stores what the visitor clicked, and the signal decides what runs. Both are working as intended: the visitor’s choice is kept, and the signal blocks Analytics while it is on.
WP Consent API values stay on deny after Accept All.
This has the same cause. While the signal is on, SureCookie tells the WP Consent API that statistics and marketing are denied, when the visitor clicks and again on every page load. A value you set by hand with wp_set_consent() lasts only until the next page. Test in a window without the signal.
getConsentSummary() lists a category as allowed, but isAllowed() returns false.
In 1.7 and earlier, getConsentSummary() reported the visitor’s recorded choice. From 1.8.0, its allowed list matches isAllowed(), effectivePreferences gives the enforced state of each category, and preferences keeps the recorded choice. See Frontend JavaScript API & Events (surecookieManager).
Can a visitor override the signal for one service?
Not today. No banner choice, placeholder click or preferences setting releases Analytics or Marketing while the signal is on. Consent to a single service that could coexist with the signal is a request we are tracking. It has no release date yet.
Can I turn GPC support off?
No. There is no setting to ignore the signal, in the free plugin or in SureCookie Pro. SureCookie honors it for every visitor who sends it, wherever they are.
Do I still need a cookie banner?
Yes. Most visitors do not send the signal, and they still need to make a choice. Where the law requires opt-in consent, such as under the GDPR, the banner is how visitors give it.
Do I still need a Do Not Sell or Share link?
Usually, yes. The signal covers visitors whose browser sends it, while a link handles requests visitors make directly, including data you share outside the browser. Confirm what your site needs with your legal counsel.
Will my analytics numbers drop?
Yes, for visitors who send the signal. If SureCookie blocks your Google tag until consent, those visitors are not counted. If Enable Google Consent Mode is on, Google’s tags load with analytics storage denied and send cookieless pings, so no _ga cookie is set.
Does it work with page caching?
Yes. SureCookie checks the signal in the browser on every page, so a cached page is held back the same way.
Next Steps
To control which content falls under each category, see Manage Cookie Categories. If embeds stay blocked for visitors without the signal, see Embeds Blocked After Consent (YouTube, Maps, Vimeo).
We don't respond to the article feedback, we use it to improve our support content.