Basic vs advanced Google consent mode: what leaves the browser?

01

Start with the transmission requirement, not the banner label

A business owner asks an agency to make analytics wait for consent. The agency hears “do not use analytics cookies yet” and leaves Google tags running with denied storage. The owner meant “do not send Google measurement data yet.” Both people may call the result consent mode, but they have specified different behavior.

The useful distinction in basic vs advanced Google consent mode is whether the Google tags remain blocked or run with consent-dependent limits. Google’s consent mode overview describes basic mode as sending no data before consent, including no consent-status transmission. Advanced mode loads Google tags and can send measurements without cookies while storage consent is denied.

This article helps you write the requirement for an implementer. It does not select a lawful basis, install a CMP, configure redaction, or verify your website. Keep legal and policy decisions with the people accountable for them, and production changes with an authorized implementer.

02

Compare the same fresh visit in both implementations

Use a visitor with no saved consent choice as the starting point. A returning visitor with a valid stored choice is a separate case: ask how that choice is restored rather than assuming every page load begins unanswered.

For this comparison, the advanced implementation explicitly sets the relevant storage defaults to denied before measurement runs. Do not assume that choosing an “advanced” setting in a tool establishes those defaults correctly. Google’s implementation guide tells implementers to choose defaults according to company guidelines and set them before commands that send measurement data.

“Interacted with the banner” is not enough detail for a brief. Opening preferences, closing a panel, rejecting, and granting are different actions. Require the implementer to explain which state each action produces; do not silently treat a dismissal as a grant.

The table is a comparison of Google’s documented implementations, not evidence that an existing site follows either one. Mixed choices also matter. Granting analytics storage does not, by itself, grant every advertising purpose.

03

Understand why cookieless does not mean no transmission

Google calls these requests cookieless pings or measurements without cookies. They still communicate information to Google. Its Analytics consent behavior reference says that when analytics storage is denied in advanced mode, first-party analytics cookies are not read or written, but pings are sent for measurement and modeling.

The same reference lists information that pings can include: timestamps, user agent, referrer, consent-state information, and a random number generated on each page load. It also explains that normal HTTP/browser communication may include an IP address, while Google Analytics does not store or log IP addresses. Receiving information and retaining it are different questions.

Do not turn “no analytics cookies” into a claim that no identifying information could ever leave a particular implementation. Google notes that advertiser-set fields such as user_id and custom dimensions are sent normally. What your site adds to a request needs its own review. Avoid putting personal or sensitive information into test URLs, events, or captures.

There are also separate consent types, not one universal switch:

• analytics_storage governs analytics-related storage.
• ad_storage governs advertising-related storage.
• ad_user_data sets consent for sending user data to Google for online advertising purposes.
• ad_personalization sets consent for personalized advertising.

Google’s overview defines these types, and its implementation guide explains the v2 addition of the last two. Basic versus advanced is a different distinction. Neither “v2 enabled” nor a screenshot showing denied storage answers whether Google requests were blocked before a choice.

04

Decide what the business is actually asking for

Consider an illustrative repair-shop website. The owner says: “For the visitors in this brief, do not load the Google measurement tags or transmit their data until the relevant consent is granted. Keep them blocked after rejection.” That describes the transmission boundary of basic consent mode. It is not satisfied merely by showing that no analytics cookie appeared.

A different owner, after the necessary policy review, might specify: “Load the Google measurement tags with the agreed consent defaults denied. We understand that consent state and cookieless measurements will be transmitted before a choice and after denial.” That describes the advanced behavior being discussed here. The implementation still needs to respect every relevant consent type.

These examples are alternative requirements, not recommendations about which choice is lawful or suitable for your business. If the owner has not decided whether pre-consent transmission is acceptable, leave that decision unresolved rather than letting a vendor’s preset make it implicitly.

Modeling is a measurement tradeoff, not a reason to bypass that decision. Google distinguishes general Ads conversion modeling under basic mode from advertiser-specific modeling supported by advanced mode. Those are not promises of recovered sales or complete reporting. In particular, Google’s GA4 behavioral modeling guidance requires sufficient eligible data and says that even meeting the published prerequisites does not guarantee eligibility. A small business should not approve transmission on the assumption that modeled reports will necessarily appear.

05

Give the implementer a brief they can answer

Replace “make our banner compliant” with a scoped technical request. Keep the policy decision separate from the implementer’s description of what the site will do.

An example opening sentence is: “For a fresh visitor on these page types and in these regions, our requirement is to keep the named Google measurement tags blocked until the relevant grant, including no consent-status ping beforehand.” If your approved requirement instead permits advanced behavior, state the expected pre-consent transmissions explicitly. Do not reuse the blocking sentence and merely change the word basic to advanced.

Have the implementer mark unknowns before work begins. If a site has another tagging route or embedded service, it needs to be accounted for rather than hidden by the label on the main consent tool. This brief is not authorization to change live tags or publish a container.

06

Ask for evidence of behavior, not just a saved setting

A settings screenshot establishes what somebody selected, not what the browser sent. Ask an authorized specialist to relate the saved configuration to observations for no choice, rejection, a relevant grant, and return visits. Where regional behavior is configured, request evidence for the regions in scope.

Google’s Tag Assistant verification guide covers checking defaults, consent updates, and tag behavior. Pair that explanation with the agreed network and storage observations. A cookie check alone cannot establish a no-transmission requirement; equally, a denied-state measurement request is not by itself proof that advanced mode is malfunctioning. Its interpretation depends on the approved requirement and actual request contents.

For each scenario, ask for the page, test time, region assumption, starting saved-choice state, expected behavior, observed behavior, and unexplained differences. Keep captures private and remove sensitive details before sharing. Missing observations are unresolved, not a pass. This article supplies the questions; it does not perform or certify those checks.

LocalCMO’s marketing approval overview and audit trail overview describe human decisions and separate execution records for supported local marketing work. The Agent audit log help explains reading available Agent activity within the user’s access and permissions. These are workflow background, not documentation of a CMP, a Google consent-mode integration, a browser-request audit, or permission to deploy tags. Keep your consent brief and specialist’s evidence in the record your website team actually uses.