A visitor arrives on your website, clicks “Reject All” and continues browsing. Your cookie banner records their choice. But does the rest of your website follow it?

The answer depends on how the banner connects to your analytics, advertising pixels, forms and other tools. Installing a consent plugin is only part of the work. You also need to check what the website sends before someone makes a choice, after they decline and when they change their preferences.

For marketing teams, this matters in two ways: visitors’ privacy choices need to be respected, and the tracking you use to make advertising decisions needs to work as intended.

Why a cookie banner can look right and still work incorrectly

Website tracking often comes from several places. Google Analytics may load through Google Tag Manager, while an advertising pixel comes from a WordPress plugin. A form, chat widget or video embed may load another vendor’s scripts.

Those tools do not necessarily share the same consent controls.

For example, your banner might correctly block a Meta pixel managed through Tag Manager while a second copy, installed through a plugin, continues to load. The buttons work, the preference is saved, and the page looks fine. The problem is in the connections behind it.

This is why reviewing the banner’s appearance or its settings screen cannot tell you whether the implementation works.

Start with a list of your tracking tools

Before testing, identify what is installed and where it comes from. Include:

• Analytics and advertising tags, such as GA4, Google Ads, Meta and LinkedIn.
• Heatmaps and session recording tools.
• CRM forms, live chat and marketing automation scripts.
• Call tracking and third-party booking tools.
• Embedded videos, maps and other third-party content.

Ask your developer and marketing team to compare their lists. An old campaign pixel or a plugin added years ago is easy to overlook.

For each tool, record its purpose, how it loads and which privacy setting should control it. Your legal adviser can help determine the requirements that apply to your business; your technical team can translate those requirements into testable behavior.

How to check whether your cookie banner works

Use a clean browser session for each test. A fresh browser profile is useful because an existing consent choice, stored cookies or an ad blocker can affect the results.

Opening the banner and watching its buttons is not enough. You need to inspect both browser storage and network activity: what cookies are created and what information leaves the browser.

1. Visit without making a choice

Open your browser’s developer tools before loading the page. In the Network panel, watch which services receive requests. In Chrome, the Application panel lets you inspect cookies and other stored data.

Leave the banner untouched. Check the homepage and pages with forms, booking tools or embedded content.

Compare the activity with your agreed requirements. If analytics must remain blocked until a visitor accepts, confirm that the analytics tool does not load during this test.

2. Click “Reject All”

Start another clean session, reject optional cookies and browse several pages. Check whether the choice persists and whether the tools governed by that choice behave correctly.

Do not assume that an empty cookie list means no information is being sent. A script can transmit data without creating a cookie.

The reverse also needs care: seeing a request to a vendor does not, by itself, prove a violation. What the request contains and how the system is configured matter.

3. Accept one category at a time

If your banner offers separate Analytics and Advertising settings, test them separately.

Accept Analytics while leaving Advertising declined. Check that the analytics behavior matches that choice and that advertising tools remain appropriately restricted.

Then test the other combinations. A category switch is useful only if the tools assigned to it actually respond.

4. Change your mind

Accept optional tracking, then use the Cookie Settings link to withdraw that permission.

Continue browsing and reload the page. Check whether future data collection changes as expected and how previously stored identifiers are handled. Existing cookies and ongoing tracking are separate things to inspect.

5. Test Global Privacy Control

Global Privacy Control, or GPC, lets visitors send an opt-out preference through their browser. California’s Attorney General identifies it as a mechanism covered businesses must honor for applicable sale or sharing opt-outs.

It is not the same as rejecting every optional cookie. Test whether your website receives the signal and applies the required restrictions, including on pages that contain third-party tools.

Why Google Consent Mode needs a closer look

Google Consent Mode adjusts Google tag behavior based on consent settings. Its basic and advanced implementations behave differently.

With basic Consent Mode, Google tags are blocked until the relevant consent is granted. With advanced Consent Mode, Google tags can send cookieless measurements while consent is denied.

That distinction matters when interpreting a test. A request to Google after “Reject All” may reflect the selected implementation rather than a broken banner. However, if your approved requirement is that no Google requests occur before consent or after rejection, an advanced implementation that sends those measurements will not meet that requirement.

Also, Google Consent Mode does not automatically control every other vendor installed on your website. Meta pixels, session recording tools and embedded services need their own checks.

Test your conversions after making changes

Once consent controls are corrected, test the marketing measurement too.

Submit a test inquiry or complete a test booking with the relevant permissions enabled. Confirm that the conversion is recorded in the right platforms, once, and that the inquiry reaches your CRM.

Repeat the journey with those permissions declined. The form or booking process should still function, while the tracking follows the agreed restrictions.

A drop in reported conversions after a consent change deserves investigation. It could reflect less observable activity, a tracking error or a change in actual performance. Comparing analytics with CRM inquiries and booking records helps you understand which explanation fits.

When should you repeat a cookie consent audit?

Retest after adding a marketing platform, replacing a form, changing your consent plugin, launching a redesign or installing new tracking tags.

Keep a short record of the pages tested, consent choices, findings and corrections. That gives your team a reference when the website changes and makes it easier to catch a problem introduced by a new tool.

Need help checking your website’s tracking?

Traktek Partners reviews how cookie consent controls interact with analytics, advertising tags and website tools. We identify implementation issues, make technical corrections and verify the results against your agreed privacy requirements.

If you have a cookie banner but have never tested what happens behind it, a website privacy and tracking audit is a useful place to start.

‍