Basic vs Advanced Consent Mode: a marketer's guide with a worked example

Basic Consent Mode blocks Google tags until the relevant consent is granted. Advanced Consent Mode loads tags with consent defaults and can send cookieless measurements while consent is denied. Both need a correctly implemented choice and update process. They differ in the information available before permission and, consequently, the inputs available for modelling.

The choice should follow your website's requirements and data-handling decisions. A larger reporting number is not a sufficient reason to change it.

Follow one visitor through each setup

Imagine a fictional retailer advertising to European shoppers. A visitor clicks an ad, lands on a product page and rejects optional cookies. Later in that visit, they place an order.

In the Basic setup described here, the relevant Google tags stay blocked. They do not send the rejected visitor's activity to Google through those tags. The retailer's order system can still record the sale as part of fulfilling the purchase.

In an Advanced setup, Google tags load with denied defaults and can send cookieless measurements. That is still data transmission. Do not describe it as “nothing is collected” or assume that the absence of cookies settles every legal question.

Google's consent-mode overview documents these behaviours. Make sure the chosen behaviour is reflected in the implementation and the information provided to visitors.

A reporting example without a recovery promise

Suppose the same retailer has 100 paid orders in a week. Its advertising report currently shows 60 attributed conversions. These are invented numbers used to explain reporting, not a forecast or Passiro customer result.

It would be tempting to describe the difference as “40 conversions Consent Mode will recover”. That conclusion skips several questions. Were all orders driven by the advertising being reported? Are the dates, attribution windows and conversion definitions aligned? Were refunds or duplicate events handled consistently?

Now suppose an eligible Google Ads setup reports 12 additional modelled conversions, bringing the reported total to 72. Under this simplified example, the report already contains the modelled contribution. Adding another 12 would double count it.

The business still has 100 paid orders. Modelling changes the estimate in an advertising measurement system; it does not create 12 new purchases. See Google's explanation of modelled conversions for how estimates are incorporated into reporting and bidding.

What matters for a smaller advertiser

First establish whether the account is eligible for the modelling feature you are discussing. Implementation and modelling activity are separate checks. Google Ads exposes different statuses in its consent-mode diagnostics.

GA4 behavioural modelling is also a separate feature from Google Ads conversion modelling. Google's GA4 eligibility guidance includes data-volume requirements and an Advanced implementation. Do not assume that enabling a banner makes modelling available in every report.

If your site is small, a sensible first win is a correct, documented setup. Plan campaign reporting around the evidence available now, and revisit modelling when the relevant account signals support it.

Choose the mode with a short decision brief

Before changing anything, have marketing and the implementation owner answer four questions:

• Are any Google requests allowed before the visitor grants the relevant consent under our agreed setup?
• Which disclosures, regional rules and internal policies govern that decision?
• Which modelling feature are we expecting to use, and have we checked eligibility?
• How will we prove that both rejection and later updates behave correctly?

Write down the chosen mode and the reasoning. That prevents someone from changing the behaviour later because a generic tutorial recommended a different setting.

Then test the implementation order

Defaults and updates need to reach the relevant tags at the right time. A tag that runs before the intended consent state is established cannot be judged only by the state shown later.

For Tag Manager implementations, Google's consent-template APIs support setting default consent and updating it. Ask your developer to verify the sequence rather than adding a second custom consent script without understanding the first one.

Check a fresh visit, rejection, category-specific acceptance and withdrawal. Include the conversion page. Use the practical cookie-banner test for the full journey, then record the release in your reporting notes.