The cookie banner is a technical decision.

On mobile, many pages first show a cookie notice that covers half to all of the screen, with several options to choose from. What the visitor came to see sits behind it. Closing the page before reaching the content is common.

The notice is usually seen as an unavoidable legal requirement. It is not entirely one. It exists because the analytics tool stores cookies or identifiers on the device, and that requires prior consent in several jurisdictions. Some authorities, such as France's, exempt from consent audience measurement that does not identify people, does not combine data with other services, and does not track across sites. Cookieless tools such as Umami point to that model.

There is no search pressure to shrink it either. Google penalizes mobile pop-ups that cover content, but exempts those that respond to a legal obligation, such as cookie consent. The incentive has to come from design.

The trade-off is clear. Deep analytics adds detail about each user. Aggregate measurement without identifiers is enough to know what works, without charging admission with a banner. In most products the second option weighs more, and users themselves are not asking to be known in depth.

Consent rules change by country and by tool. Requirements are worth confirming in detail because they can change, and even without a banner the measurement should be disclosed in the privacy policy.