Analytics that measures what a visitor has consented to.
A GA4 and consent mode implementation for industrial B2B websites: consent categories mapped to the signals Google Analytics expects, tags gated so they wait for a choice, conversion events that reflect how technical buyers behave, and data-layer ownership that stays with you.
The behaviour is then verified in the browser under each consent state rather than accepted from a configuration screen. What consent is required in your markets is a legal determination your data protection officer or legal counsel makes; we implement to that definition.
A default GA4 installation collects data regardless of consent unless Consent Mode is specifically and correctly configured. On an industrial site selling into the EU, where a large share of traffic comes from buyers in scope of European data protection rules, that gap means measuring data the organisation may have had no basis to collect.
Getting it right involves four things: a mapping between your consent categories and the signals GA4 reads, a default state applied before any choice is made, tag behaviour that changes when a visitor declines, and evidence that it does. Scope depends on where your visitors are and what your organisation processes, which your legal counsel confirms.
GA4 configured with Consent Mode gating collection, verification that a declined choice stops the corresponding data collection, event and conversion tracking scoped to what remains measurable, and documentation for your data protection officer describing how the setup behaves under each state.
The measurement plan is built around industrial B2B behaviour rather than ecommerce defaults: datasheet and safety data sheet downloads, CAD file requests, product finder and filter usage, quote and enquiry submissions, distributor locator searches, and the return visits that precede a specification decision. See analytics and tracking.
Consent Mode works on named signals rather than a single on or off switch. Analytics storage governs GA4 cookies, ad storage governs advertising cookies, and two further signals cover the use of user data and personalisation for advertising. Each has to be mapped to a category in your consent banner, set to a default before the visitor chooses, and updated when they do.
Region-scoped defaults let you apply a denied default across the EEA and UK while another region follows a different rule, which matters for manufacturers selling globally from one platform. Where a tag manager sits in front of the tags, the same signals gate the rest of the marketing stack rather than GA4 alone.
Several GA4 settings affect data handling independently of consent and are frequently left at defaults: data retention period, Google Signals, granular location and device data, and the account-level data sharing options. We review each against what your organisation has decided to allow and document the resulting configuration.
Server-side tagging is worth considering where you want more control over what leaves the browser and what is forwarded onward. It changes the operational picture, since it introduces infrastructure your team or ours has to run, so we scope it as a decision rather than a default. Related reading: does industrial B2B website data have to stay in the EU.
We implement the technical configuration to whatever your data protection officer or legal counsel defines as required, keeping the legal judgment with the people qualified to make it while we get GA4 and Consent Mode to reflect that definition correctly.
We do not advise on whether a given setup satisfies GDPR, the ePrivacy rules or a national regulator, and no implementation should be treated as a compliance guarantee. What we provide is an accurate technical record of what the site collects under each consent state, which is what your legal team needs to make that assessment.
Code Industrial is the industrial B2B practice of Code Barcelona, an agency building corporate websites and digital platforms since 2015. The same strategy, design and engineering team works on every industrial project, from the first scoping session through to life after launch.
What is worth measuring, and what remains measurable under consent, differs by site. GA4 and consent mode work starts there.
What comes up when implementing consent-respecting analytics on an industrial B2B site.
No. GA4 collects data regardless of consent unless Consent Mode is specifically and correctly configured. A default installation fires tracking tags before a visitor makes any cookie choice, which is the most common gap we find when auditing industrial sites.
We configure Consent Mode so tags wait for the relevant signal, set the default state to denied where that is what your organisation has decided, and verify the behaviour in the browser rather than assuming the setup is correct.
It varies widely by market, banner design and audience. Professional buyers on industrial sites often opt in at a higher rate than consumer audiences, while traffic from corporate networks with strict browser policies or tracking protection can reduce measurable sessions further than the banner alone suggests.
We treat the resulting rate as a design constraint rather than a problem to solve, building Consent Mode modelled conversions and cookieless measurement into the setup so reporting stays useful at whatever opt-in level your markets produce.
GA4 configuration is one part of a wider implementation rather than a standalone setup. It has to use the same consent categories and banner logic as the rest of the site, including advertising tags, chat widgets, embedded video and any marketing automation script.
A common failure is a banner that blocks GA4 correctly while a third-party embed drops cookies before any choice is made. We audit the full tag inventory rather than the analytics tag alone. See analytics and tracking.
No. Defining what consent is required, in which markets and on what legal basis sits with your data protection officer and legal counsel. Requirements differ between EU member states, the UK and non-European markets, and they change as guidance and case law develop.
We implement the technical configuration, including cookie categories, banner behaviour and tag gating, to whatever standard they define, flag technical limitations we find, and document what the site does under each state so they can assess it. We do not present any implementation as a compliance guarantee.
In the basic form, tags are blocked entirely until consent is granted, so a declined session sends no data at all. In the advanced form, tags load in a restricted state and send cookieless pings that carry no identifiers, which lets Google model the behaviour of declined sessions in aggregate.
Advanced measurement gives more complete reporting; the basic form sends less. Which is appropriate is a decision for your data protection officer, and we implement whichever they specify rather than defaulting to the option that reports better.
It is worth considering where you want control over what leaves the browser, what is enriched before being forwarded, and which third parties receive anything at all. It also improves resilience against client-side blocking, which affects industrial audiences on managed corporate networks.
The trade-off is operational: a server-side container is infrastructure that has to be hosted, monitored and paid for, and it does not remove the need for a consent signal. We scope it as a deliberate decision rather than a default, and note that it does not by itself change what your organisation is permitted to collect.
Yes, and this is the pattern we usually recommend. GA4 receives the event that a quote request was submitted along with non-identifying context such as the product category or page, while the name, company and email go only to the CRM. A pseudonymous reference can link the two inside your own systems for pipeline reporting.
Sending names, email addresses or free-text enquiry content into analytics creates a data protection problem and breaches Google terms. We check existing setups for it, since it appears often in form integrations built without review.
Through one measurement specification applied across the estate: shared event names and parameters, a single tag manager container structure, one consent platform with region-scoped defaults, and a documented configuration each market inherits rather than reinvents.
Without that, country sites end up with different event names for the same action and reporting cannot be aggregated. On multi-market platforms we set this up alongside the wider architecture. See WordPress Multisite and international SEO.
GA4 and consent mode connects closely with these related technology pages.
Analytics you are not confident reflects visitor consent. Tell us what you have and we will set out how we would approach GA4 and consent mode.