The banner is there, and the tags fire regardless.
GDPR and consent for industrial websites rebuilt so the tracking behaviour matches what the visitor chose, the enquiry and download paths have a lawful basis your counsel is comfortable with, and measurement still produces usable data. What applies to your organisation is a determination for your legal counsel; our part is implementing what they decide and evidencing that it works.
The common gap is between what the banner states and what the site does. Tags that load before a choice is registered, scripts fired directly in templates outside the tag manager, embedded video and map components setting cookies on load, and chat widgets initialising regardless of the decision. Each is invisible in the interface and clear in a network trace.
Industrial sites collect through enquiry forms, document gates, sample requests and distributor registrations, and that data usually moves onward into a CRM or marketing platform. The consent question extends along that whole path: what is collected, on what basis, where it is stored, who processes it and how long it is kept.
Requiring an email address for a datasheet is a commercial decision with a data consequence. It is worth being deliberate about which documents are gated, what is collected at the gate, what the visitor is told at that moment, and whether a marketing permission is being bundled into a download request rather than asked separately.
Consent-compliant analytics loses some data, and the useful question is which questions still need answering. Consent mode with modelling, server-side collection where appropriate, and a measurement plan built around the decisions the business makes tend to preserve more usable insight than an implementation designed only to keep every event.
Applicability, lawful basis, retention periods, transfer mechanisms and the wording of notices are determinations for your legal counsel or data protection officer. We implement to those determinations and evidence the result. We do not offer legal advice and we do not offer a compliance guarantee, since conformance is a position your organisation holds rather than a property of the code.
An audit of current behaviour, a consent implementation that matches the policy your counsel sets, form and integration paths documented end to end, verified measurement, and evidence of the whole configuration. See GA4 and consent mode for the measurement side in detail.
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.
The difficulty differs with how the site collects. GDPR and consent work starts from those paths.
What comes up when an industrial company brings tracking and data collection into line.
The consent layer and everything it is supposed to control: analytics and advertising tags, embedded video, maps and chat components, enquiry and sample forms, gated document downloads, and the onward path into CRM and marketing systems. On most industrial estates the forms and their integrations turn out to be a larger part of the work than the banner.
No. Compliance is a position your organisation holds across its whole processing activity, most of which sits outside the website, and it depends on determinations your legal counsel or data protection officer makes. What we provide is an implementation matching those determinations, testing that the site behaves as specified, and documentation of the configuration as evidence.
Business context does not remove the obligations, since the data still identifies individuals at those companies, though it can affect the lawful basis available for some processing. National interpretations vary across the markets an industrial group sells into. Whether and how it applies to your organisation is a question for your legal counsel rather than something to infer from the sector.
Some, and the practical question is which questions still need answering. Consent mode with modelling recovers part of the picture, and server-side collection can help where it is appropriate. Structuring measurement around a smaller set of decisions the business makes usually preserves more useful insight than trying to retain every event.
It is a commercial trade-off before it is a data one. Gating raises the quality bar on enquiries and reduces reach, and in sectors where specifiers compare suppliers quickly it can remove you from consideration. Where documents are gated, it is worth asking for the minimum needed, saying what it will be used for, and keeping any marketing permission as a separate question.
With one implementation configurable per market rather than separate approaches maintained locally. Categories, default states, banner wording and language vary by market while the underlying mechanism stays shared, which keeps behaviour consistent and means a correction is applied once rather than negotiated with each country team.
They are among the most frequent gaps. Chat tools often initialise on page load and set storage before any choice is registered, and embedded video and map components can set cookies as soon as they render. Both need to be loaded conditionally, usually behind a placeholder that appears where the embed will be so the page does not shift when it loads.
By making new tags and embeds pass through a defined route, and by re-testing periodically. Most implementations degrade through a campaign tag added directly to a template or a new embed on a product page rather than through a decision to change the policy. A scheduled re-check catches those while they are still individually traceable.
Consent work frequently connects to these.
A banner that does not control the tags, or collection paths no one has mapped. Tell us what you are running and we will tell you how we would approach the GDPR and consent work.