How a cookie banner works
The banner is the visible part of a consent system. When it is built properly it does three jobs: it holds non-essential scripts back until the visitor chooses, it stores that choice so the site can prove what was agreed and honour it on later visits, and it gives a way to change the answer afterwards. Cookies that the site cannot function without — a login session, a basket, a security token — do not need permission and should not be sitting behind the button.
The enforcement does not happen in the banner itself. A consent platform, or your tag manager, is what actually blocks analytics, remarketing and pixel tags until the choice comes back, and passes that choice on to advertising and measurement tags so they behave accordingly. A banner with nothing wired behind it is a picture of a question.
Why cookie banners matter
There is a legal reason and a practical one. Where a site has visitors in the EU or UK, permission is expected before non-essential tracking starts, and the request has to be a real choice rather than a notice. That obligation follows the visitor, so a business anywhere — Kathmandu included — can be covered by it when it markets to those countries.
The practical reason is that the banner shapes your data. Every decline is a genuine gap in analytics and a person missing from remarketing audiences, so consent design quietly determines how much of your reporting exists at all. It also lands on the first screen a visitor ever sees, and on a mobile-heavy market like Nepal a panel that swallows the whole screen is measurable friction before anyone has read a word.
Where cookie banners go wrong
The most common fault is cosmetic consent: the banner shows, the visitor clicks, and the tags fired on page load regardless. The second is a rigged choice — accept as a bright button, reject buried in a settings menu or missing altogether, or boxes pre-ticked in your favour. Regulators in the EU and UK have been explicit that consent designed to be difficult to refuse is not consent, and that pattern is the one most likely to be complained about.
Then there are the self-inflicted ones. A banner installed on a site with no European visitors and no tracking worth consenting to costs conversions and gains nothing. A banner that loads late and pushes the page around damages page experience. And a site with no way to withdraw consent leaves the visitor with no route back, which is the part people notice and resent.
What to do about it
Decide first whether you need one, based on where your visitors actually are and what you actually run. If the honest answer is yes, choose a tool that genuinely blocks tags rather than one that only draws the panel, and confirm it by loading the site and watching whether the tags fire before you click. Give reject the same weight as accept, keep the panel small on phones, and make sure the choice is stored rather than re-asked on every page.
Keep a record of consents so a later question can be answered, and check that the marketing tags respect the signal — the join between consent management and measurement is where most setups quietly break. If your reporting matters, treat the banner as part of the analytics and tracking build rather than as a legal item bolted on at the end.
