IIDigital MarketingAnalysis
Cookie Banners and Measurement: What Still Works Without Consent
Since consent banners became mandatory, many businesses see only part of their visitors in web analytics. The question is which numbers still hold up and how to measure without gambling away trust.
Key takeaways
- Under Section 25 of Germany’s TDDDG, any access to the visitor’s device requires consent unless it is strictly necessary for the service explicitly requested. Web analytics with cookies is generally not.
- Many numbers remain without consent: Search Console, the business profile, the source in the inquiry form and the CRM. They show inquiries and orders, not every click.
- Manipulative banners work against the business. An experiment shows that vague wording and a missing reject option lower the sense of control and trigger resistance to later ads (Ju, Ham and Yel 2026).
- The three-layer measurement sorts numbers by whether they touch a device and bases decisions on the layer that is complete without consent.
Why does web analytics show only part of your visitors?
Many owners experience the same thing: web analytics reports far fewer visitors than before, although inquiries have not fallen. The reason usually lies not with the website but with the consent banner. Anyone who rejects or dismisses the banner is not recorded by analytics that sets cookies. The numbers then show only visitors who agreed.
This article therefore answers one question: Which measurement is still possible without consent, and how does a small business design banner and measurement so that its numbers hold up and visitors’ trust does not suffer? We first clarify the legal situation and the terms, then a model from advertising research that explains why intrusive banners do harm. After that we look at study findings, weigh two views and sort the measurement methods into three layers. This article is not legal advice.
A banner that pushes for a yes buys numbers and pays with trust.
What does Section 25 TDDDG require, and what counts as device access?
In Germany, two sets of rules interlock for cookies, as the article on B2B retargeting already describes. The Telecommunications Digital Services Data Protection Act (TDDDG), called TTDSG until May 2024, regulates access to terminal devices in Section 25. Anyone who stores information in a user’s browser or reads it from there needs the user’s consent, unless the access is strictly necessary for the service requested. The General Data Protection Regulation (GDPR) then governs whether the personal data obtained in this way may be processed.
Device access is broader than the word cookie suggests. It also covers pixels, local browser storage and methods that read device features to recognize it. The Datenschutzkonferenz, the body of Germany’s data protection authorities, deliberately gives no blanket approval for audience measurement in its guidance for digital services. The specific purpose is what counts. Strictly necessary are, for example, a cookie for the shopping cart, for login or for storing the banner decision itself. Web analytics showing how many visitors come from where serves the operator, not the service the visitor wanted.
Courts have clarified the requirements for consent. In 2019 the Court of Justice of the European Union ruled in the Planet49 case (C-673/17) that a pre-ticked box is not valid consent, and Germany’s Federal Court of Justice followed in 2020 (I ZR 7/16). The Datenschutzkonferenz also requires that rejecting be as easy as accepting. Since April 2025 Germany has also had the Consent Management Ordinance (Einwilligungsverwaltungsverordnung). It allows recognized services in which users store their decisions centrally. Website operators, however, are not obliged to honor such services.
| Access | Purpose | Usual classification |
|---|---|---|
| Cookie for language choice, login or banner decision | Function the visitor triggers | strictly necessary, no consent needed |
| Web analytics with cookies or recognition | Statistics for the operator | consent needed |
| Advertising pixels and retargeting | Ads on other sites | consent needed |
| Embedded maps, videos, third-party fonts | Displaying content | often consent or local hosting needed |
| Server log without storage in the browser | Operation and security of the website | no device access, GDPR still applies |
Changes have been announced but not adopted. In November 2025, in the so-called Digital Omnibus, the European Commission proposed among other things an exemption from consent for aggregated audience measurement and one-click rejection. The Council adopted its position on October 21, 2026, Parliament’s position is pending, and entry into force is not expected before 2027. Until then, Section 25 TDDDG applies unchanged. Plan according to the law that applies today.
Two views: maximize consent or rebuild measurement?
The first view relies on the banner. It says: without consent there are no usable numbers, so the banner must be designed so that as many people as possible agree. Colors, order and wording are optimized for this. In its favor is that web analytics with consent shows more precise paths through the website than any other source.
The second view relies on measurement. It says: a small business’s decisions depend on inquiries and orders, and these can be counted without device access. The banner stays honest, web analytics provides a sample, and steering is based on numbers that are complete. The findings on reactance support this, as does the legal situation, under which a pushy banner is vulnerable.
I consider the second view the more sustainable one. A small B2B business often has only a few thousand visitors a month. At such volumes, more precise web analytics says little about the one question that matters: which source brings orders. That question is answered by the measurement chain from the article on how to measure marketing success, and its decisive links, inquiry, conversation and order, lie in the form and the CRM, not in the visitor’s browser.
The three-layer measurement: which numbers remain without consent
From the legal situation and the findings I derive an order that I call the three-layer measurement. It sorts every number by whether it requires device access. Steering is done with the bottom layer because it is complete. The upper layers supplement it.
Layer 1: without device access
Search Console, business profile statistics, the source question and hidden source field in the form, the inquiry list and the CRM. These numbers are complete because they do not depend on consent. Inquiries, conversations and orders per source belong here.
Layer 2: technical logs and aggregated counting
Server logs show page requests for operation and security. Some analytics tools count without cookies and without recognition. Whether that is permissible without consent in the individual case is disputed. Have the setup checked before you rely on it.
Layer 3: with consent
Web analytics with cookies, advertising pixels, retargeting. These numbers are a sample of visitors who agreed. They show paths through the website and patterns, but not totals.
Worked example with freely chosen numbers. The consent rate depends heavily on website and banner. The inquiry rate of 1.2 percent matches the example in the article on a website that brings inquiries. Only the form is complete for everyone who inquires.
For clicks from Google Search, Google Search Console provides impressions, clicks and position without any cookie being set on the website. How these numbers relate to whether a business is found is described in the article on how to measure visibility. And how to improve the inquiry rate with few visitors is covered in the article on how to measure the website inquiry rate.
Conclusion: what still works without consent?
The question was measurement is possible without consent and how banner and measurement can be designed so that numbers hold up and trust remains. Without consent, everything remains that needs no device access: Search Console, business profile, the source field in the form, the inquiry list and the CRM. With these, inquiries, conversations and orders per source can be counted completely. Web analytics with cookies now provides only a sample, useful for paths and patterns, not for totals.
The banner should be honest, not only because the law requires it. The findings on reactance show that visitors who were pushed meet later messages with more resistance. A business that bases its decisions on the complete bottom layer can afford an honest banner. The experiments cited do, however, come from consumer business, and how buyers react to banners has not been studied. The direction remains robust: if you take the obligation seriously, you lose numbers you do not need and keep the ones that matter.
What you can put into practice right away
- Open your website in a private browser window and check whether rejecting on the first layer is as easy as accepting.
- Ask your agency or service provider for a list of the services the website loads and compare it with the banner.
- Check whether your inquiry form stores the source and asks how the person found you.
- Decide which three numbers from layer 1 you will review monthly, and have banner and analytics checked by your data protection officer.
Frequently asked questions
Do I need consent for Google Analytics?
As a rule, yes. Web analytics that sets cookies or recognizes visitors is not strictly necessary for the service the visitor wants to use and, under Section 25 TDDDG, requires prior consent. This is not legal advice.
Which cookies are allowed without consent?
Allowed without consent is access that is strictly necessary for a service explicitly requested, such as login, shopping cart, language choice or storing the banner decision. Statistics and advertising are generally not included.
Is there web analytics without a cookie banner?
Some tools count without cookies and without recognition. Whether that is permissible without consent is disputed, because other forms of device access can also fall under Section 25 TDDDG. Reliably consent-free are Search Console, the business profile, the source field in the form and the CRM.
Does the reject button have to be equivalent?
According to the requirements of the German supervisory authorities, rejecting must be as easy as accepting. A banner that hides rejection behind further steps is legally vulnerable. It can also trigger resistance to later advertising.
Sources
- Ju, I.; Ham, C.-D.; Yel, E. (2026): Dark Patterns in Data-Consent Disclosures and Consumer Reactance to Online Behavioral Advertising. Journal of Advertising, 55(3), 307-325.
- Ntemkas, C.; Teixeira, L. V.; Islami, L. et al. (2026): GDPR Dark Patterns in Cookie Consent: An Automated Study of High-Traffic Websites Accessed from Denmark. Future Internet, 18(9), 487.
- Godinho de Matos, M.; Adjerid, I. (2022): Consumer Consent and Firm Targeting After GDPR: The Case of a Large Telecom Provider. Management Science, 68(5), 3330-3378.
- Utz, C.; Degeling, M.; Fahl, S.; Schaub, F.; Holz, T. (2019): (Un)informed Consent: Studying GDPR Consent Notices in the Field. Proceedings of the ACM SIGSAC Conference on Computer and Communications Security, cited in Ju, Ham and Yel (2026).
- Friestad, M.; Wright, P. (1994): The Persuasion Knowledge Model: How People Cope with Persuasion Attempts. Journal of Consumer Research, 21(1), 1-31.
- Datenschutzkonferenz: Guidance of the supervisory authorities for providers of digital services, version 1.2 (in German).
- Heuking (October 23, 2026): Cookie consent under the Digital Omnibus: planned changes and technical implementation.
- Court of Justice of the European Union, judgment of 1 October 2019, C-673/17 (Planet49).
- German Federal Court of Justice, judgment of 28 May 2020, I ZR 7/16 (Cookie Consent II).
Note. This article gives a general overview as of November 2026 and is not legal advice. The law, guidance and the legislative procedure on the Digital Omnibus may change.



