How to Test Consent Banner Configuration & Behavior
Testing your consent banner confirms that consent behavior matches your regional requirements and your intended technical implementation. This article walks through the checks to run and what to look for in each.
Step 1: Verify default consent settings
Start with how the banner behaves on first page load, before any interaction.
Check whether the banner is configured as:
Opt-in: no non-essential activity occurs until consent is granted.
Opt-out: non-essential activity is allowed until the user rejects it or adjusts preferences.
To test:
Open a private or incognito browser window.
Load your site for the first time.
Open the banner’s settings and check that each category toggle shows the intended default.
Open browser developer tools and review stored cookies (Application > Cookies).
Default behavior should match your regional compliance strategy and internal policy decisions. For help choosing a model, see How to Choose Between Opt-In and Opt-Out Consent Models.
Test regional variations
Consent behavior may vary by visitor location, depending on your configuration. For example, you may apply an opt-in model for EU traffic and an opt-out model elsewhere.
Use a VPN to simulate traffic from each region.
Clear browser storage, or use a fresh private window, between tests.
Load the site and check the banner defaults and cookie behavior.
Confirm that regions requiring opt-in consent show the right defaults and that other regions behave as expected. See How to Identify Regions Requiring Opt-In Consent Models.
Step 2: Verify cookie nullification after Reject
When a user rejects non-essential categories, cookies may still exist in the browser but should be nullified or otherwise made inactive, depending on configuration.
Allow cookies to be set, either by default or by opting in.
Reload the page and confirm the cookies exist.
Change the banner preferences to reject or disable non-essential categories.
Recheck the cookies in browser developer tools.
Confirm that non-essential cookies have their values removed, overwritten, or otherwise disabled in line with your configuration. A cookie name alone does not indicate active data collection: focus on whether the cookie still holds a meaningful value.
Step 3: Test Global Privacy Control (GPC) signals
If Global Privacy Control (GPC) is enabled in the browser, your site should respect the signal in line with your configuration.
Enable GPC in a browser that supports it, or with the Captain Compliance GPC extension for Chrome.
Open a new private window.
Load your site.
Confirm that every non-essential category is disabled. By default, Captain Compliance treats a GPC signal as a rejection of all non-essential categories, wherever the visitor is. Then review cookies in browser developer tools to verify that the result is enforced.
If your banner uses bucket mode, each bucket has its own setting for whether it is turned off when GPC is detected. In that case, confirm that the result matches your configuration. See How to Use Bucket Mode to Customize Consent Categories and GPC Behavior.
Step 4: Confirm script blocking behavior
The consent banner controls consent state, but script blocking depends on how each script is deployed:
Scripts loaded through Google Tag Manager must be gated with consent settings. See How to Gate GTM Tags with Native Consent Settings.
Hard-coded or inline scripts must be wrapped in consent-aware logic. See How to Gate Non-Essential Scripts and Beacons Using Explicit Consent Logic.
Cookie blocking alone does not prevent all network requests. See How to Avoid Network-Traffic-Based Privacy Litigation.
To validate:
Reject non-essential categories.
Open browser developer tools and watch the Network tab.
Confirm that non-essential third-party requests do not run unless consent is granted.
If scripts still fire after Reject, more configuration is needed in GTM or through execution gating. If you deploy through GTM, also run the scenario grid in How to Test Your GTM Consent Setup.
Testing best practices
Always test in private or incognito windows.
Clear caches and browser storage between tests.
Avoid testing while logged in, unless the test requires it.
Test both first-load and post-consent scenarios.
