Cookie banners and consent for a small business marketing site: do you need one, and how to set it up
Short answer: A cookie banner is the pop-up that asks visitors whether a website may store small tracking files (cookies) or similar data on their device. You generally need one if you have visitors in the UK or EU and your site uses analytics, advertising or tracking tags beyond the strictly necessary. In the US there is no federal banner rule, but state laws such as California's require an opt-out for selling or sharing personal data, and a browser signal called Global Privacy Control must be honoured by businesses the law covers. This is information, not legal advice, so check the rules where your visitors live.
You run a small business website with analytics, ads or a chat widget and want to know whether you need a cookie banner and how to set one up properly.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The answer depends on two things: where your visitors are, and what your site loads. A site with no analytics, no ad tags and no embedded third-party tools may need no banner at all. A typical marketing site, with Google Analytics, a Facebook (Meta) pixel, a chat widget and an embedded video, almost certainly does if any visitors are in the UK or EU. In the US, the duty is usually an opt-out and a privacy notice, not a pop-up. Rules change, and nobody can promise you a perfect setup, so use this page as a working checklist and confirm the details with the regulator pages listed at the end.
First, what is being regulated
A cookie is a small file a website stores in a visitor's browser. The same rules also cover similar tools: pixels (tiny invisible images that report a visit), local storage, scripts and tags. The rule in the UK and EU is about storing or reading information on a person's device, not only about cookies by name. Some of that is allowed without asking, such as storage that is strictly necessary to run the service you asked for (for example a shopping basket or a security token). Marketing and most measurement storage generally needs a choice from the visitor.
Three separate layers often get mixed up:
- Device access rules (ePrivacy in the EU, PECR in the UK): do you need permission to store or read something on the device?
- Data protection law (GDPR): what lawful reason do you have to use the personal data you collect, and what do you tell people?
- US state privacy laws: can people opt out of your selling or sharing their data, and do you honour a signal like GPC?
A banner usually covers the first layer. It does not replace a privacy policy, and it does not fix the second or third.
Do you need a banner? A decision table by visitor location
| Where the visitor is | What the rule generally asks | Practical setup |
|---|---|---|
| UK | PECR (the Privacy and Electronic Communications Regulations, the UK's rules on email and device access) regulation 6 says a person must not store or access information on a user's device unless an exception applies. Schedule A1 lists the exceptions: strictly necessary, a narrow statistical purpose, appearance and functionality choices, and emergency location. The UK's data protection regulator, the ICO (Information Commissioner's Office), published final guidance on storage and access technologies in April 2026, per the ICO's own page URL. Check it for the current analytics exception. | Ask before loading ad pixels and most marketing tags. Give a clear reject choice. |
| EU / EEA | The ePrivacy rule (the EU's rule on device access and electronic communications) is described in secondary sources as requiring consent for non-essential storage or access, with GDPR (the General Data Protection Regulation) standards for what counts as consent. Regulators such as France's CNIL (the French data protection regulator) expect refusing to be as easy as accepting. Whether GDPR itself demands a "reject" button on the first layer is debated, since the text is silent, but regulators push the strict view. | Opt-in banner, equal-weight accept and reject buttons, nothing non-essential loads before a choice. |
| California | The state's CCPA (the California Consumer Privacy Act) gives people the right to opt out of the sale or sharing of their personal information. Businesses that sell or share must offer two or more opt-out methods, and the Attorney General's page says a user-enabled Global Privacy Control signal "must be honored" as a valid opt-out. The law applies if a business has over $26,625,000 in annual revenue (the inflation-adjusted figure in use since January 2025; the thresholds are adjusted every odd-numbered year, so check the current figure), handles 100,000 or more California residents or households, or earns 50 percent or more of revenue from selling personal information. Page updated 28 August 2026. | A "Do Not Sell or Share My Personal Information" link if you sell or share, plus honouring GPC. |
| Rest of the US | No federal cookie-banner law. Obligations come from state privacy laws, mostly an opt-out model, and thresholds differ by state. | A clear privacy policy, an opt-out where a state law applies, and no promises you do not keep. |
A small California business under all three thresholds may not be covered by the CCPA at all. A UK or EU visitor, though, brings the device rules into play no matter how small you are, if your site is aimed at them or they use it. If you are unsure, the simplest policy is to treat everyone like an EU visitor. That costs you some measurement data, and it is cheaper than sorting visitors by country.
What a small marketing site actually loads
Do an inventory before you pick any tool. Typical items, and a rule of thumb for each (confirm with each vendor's documentation):
| Item | What it does | Usually needs a choice (UK and EU)? |
|---|---|---|
| Google Analytics 4 (GA4) | Google's free visitor statistics tool | Generally yes, unless you rely on a narrow exception such as the UK statistical one, which has conditions. |
| Meta (Facebook's parent company) pixel, Google Ads tag, LinkedIn Insight tag | Advertising tracking | Yes. Advertising is not exempt. |
| Chat widget | Live chat or AI chat bubble | Depends on what it stores. Check the vendor. |
| Embedded YouTube videos or maps | Third-party content | Often yes. Some providers have a privacy-enhanced mode. |
| Web fonts from a third party | Fonts loaded from another company's server | Not a cookie, but it sends the visitor's address to that company. Hosting fonts yourself avoids it. |
| Contact form, session and security cookies | Keep the site working | Usually strictly necessary. |
The UK exception for statistics, in PECR Schedule A1, applies only if the sole purpose is improving the service, the data is not shared except with someone helping you improve it, visitors get clear information and a simple, free way to object. It also excludes collecting data a device sends automatically. It is narrow. Do not assume "analytics" as a category is exempt. The French regulator's audience-measurement exemption is also narrow, according to summaries. Cookie-free analytics tools can lower the amount you need to ask for, but check the tool's own claims against the conditions.
Google Consent Mode, in plain words
Google Consent Mode is a setting that passes a visitor's cookie choice to Google's tags so they adjust their behaviour. Google's page says it does not provide a banner. It works with your banner. If a visitor says no, the tags send cookie-free signals instead of storing identifiers, and Google models some of the gap.
For visitors in the European Economic Area, Google's tag manager help says that to use ad personalisation and measurement with Google tags you must collect consent and share the consent signals, using the parameters ad_user_data and ad_personalization. It says a Google-certified consent tool is one route, and that you should confirm with your provider that you are on the latest version. If you run no personalised ads, the pressure is lower, but check your own tags against Google's page.
Your options for the banner
| Option | Good for | Watch out for |
|---|---|---|
| No banner, no non-essential tags | A simple brochure site with no analytics or ad tags | You lose visitor data. Any later tag you add changes the answer. |
| Cookie-free analytics | A site that needs counts, not ad retargeting | Check the tool against the legal conditions, not just its marketing. |
| A consent management platform (CMP) | Sites with ads and several tags | Monthly fees at scale, setup work, and the need to confirm it actually blocks tags. |
| Your website builder's built-in banner | Quick setup | Check it blocks tags before consent and logs choices, not just shows a bar. |
| A Google-certified CMP with Consent Mode | Sites running Google Ads to EEA visitors | Confirm version and settings with the provider. |
Whatever you pick, a good banner has the same features: it explains each purpose in plain words, offers accept and reject with equal weight, does not pre-tick boxes (the EU's top court ruled in the Planet49 case that pre-ticked boxes are not valid consent, as summarised by secondary sources), blocks non-essential tags until the choice is made, remembers the choice, lets people change it later, and keeps a log of choices.
Example: how one site builder handles consent
Ploy is an AI website platform that builds and hosts marketing sites and includes built-in analytics. Its docs show a useful pattern to look for in any builder. As of November 2026, Ploy says its analytics follows your cookie banner: when a visitor refuses, it stores no visitor ID on the device, keeps only a small cookie named ploy_consent (180 days) that remembers the refusal, and uses an anonymous ID that resets daily. It sets a first-party cookie named ploy_anon_id for one year when a visitor accepts, or when the site reports no choice. Importantly, Ploy does not add a cookie banner for you. You need your own banner and privacy policy, and you call a short line of code from the banner (window.ploy.consent with granted or denied) on every page load. Ploy waits up to one second for your banner, and if your site never calls it, Ploy sets its cookie. So make your banner call the denied option as early as it can on every page load, then switch to granted if the visitor accepts, and check Ploy's analytics docs for the current wording. Ploy says the GA4, Meta pixel, Google Ads and LinkedIn tags it adds wait for that consent signal.
The lesson applies to any builder: "the platform follows my banner" is only true if you wire the banner to it. Test it, as shown below. Ploy's visitor identification feature (matching visits to companies) works for net-new visitors in the US only, per Ploy, and see whether identifying visitors is legal for the extra rules. For the platform overall, read what Ploy is.
Setup steps (about 2 hours)
- Inventory. List every tag, pixel, widget and embed on the site. Open your browser's developer tools, look at the Application tab for cookies and local storage, and compare to what you expect.
- Decide per item. Strictly necessary, needs a choice, or remove it. Removing a tag you do not use is the cheapest fix.
- Pick the banner tool from the table above.
- Set your defaults by region if the tool supports it: opt-in for the UK and EU, opt-out with GPC for California, notice-only elsewhere. Google recommends region-specific defaults for consent mode.
- Connect tags to consent. Make each non-essential tag wait for the choice. In Google Tag Manager (Google's free tool for managing site tags), that means consent settings on the tags.
- Update your privacy policy. List what you collect, why, who receives it, how long you keep it, and how to opt out or contact you. See privacy policy and terms before launch.
- Add the link to cookie settings in your footer so visitors can change their mind.
Test plan with pass and fail rules
- Open the site in a clean private window. Before you click anything, check cookies and network requests. Pass: only strictly necessary storage exists, and no ad or analytics requests fire in the UK and EU default. Fail: tracking requests appear before a choice.
- Click reject. Reload. Pass: no new non-essential cookies, and the banner does not reappear on every page. Fail: cookies appear anyway.
- Click accept. Pass: your analytics and ad tags now fire once.
- Change the choice from the footer link. Pass: tags stop (some tags need a page reload to stop, so check the vendor's note).
- Turn on a Global Privacy Control signal in a browser or extension that supports it (check the GPC site for supporting browsers), then visit as a California visitor if you can. Pass: your site treats it as an opt-out of sale or sharing.
- Check on mobile. Pass: the banner does not cover the page and both buttons are readable.
Who this page is not for
If you handle health, finance or children's data, run large ad budgets to the EU, or have received a complaint, get advice from a privacy lawyer in the relevant country. Regulators have fined large companies, such as a reported 150 million euro fine against Shein for cookie practices (per a vendor blog summary, so check the regulator's own statement). A small business is not the usual target, but ad-funded sites with big EU audiences are higher risk.
How I'd approach this
I would start by cutting tags, not buying a banner. Most small sites carry two or three tags nobody uses. Then I would pick one analytics tool, one banner, and a rule: nothing loads until the visitor chooses, for everyone.
First-week plan. Day 1: inventory every tag and cookie. Day 2: remove what you do not use. Day 3: choose the banner and connect it to your analytics. Day 4: update your privacy policy and add the footer link. Day 5: run the test plan above and write down the results. Day 6: fix anything that failed and test again. Day 7: set a calendar reminder to repeat the test every quarter and whenever you add a new tag.
Decision rule. If you have any UK or EU visitors and use ads or analytics, use an opt-in banner. If your visitors are mostly in the US, use a clear notice, an opt-out where state law applies, and honour GPC. If you want a custom site where consent, forms and lead tracking are built to your own rules, Blur Studio builds those, see what that includes. For a broader pre-launch review, use the launch-readiness checklist.
Related guide: compliant websites for accountants, lawyers and clinics.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Do I need a cookie banner for a small business website?
If you have visitors in the UK or EU and use analytics, advertising tags or other non-essential storage, you generally need to ask first. In the US there is no federal banner rule, but state privacy laws can require an opt-out. A site with no non-essential tags may need no banner. Check the rules where your visitors live.
Is Google Analytics exempt from cookie consent?
Not as a rule. The UK has a narrow statistical exception with conditions in PECR Schedule A1, and France's regulator has a narrow audience-measurement exemption, but Google Analytics is not automatically exempt in the UK or EU. Check the conditions and the current regulator guidance.
Is Google Consent Mode a cookie banner?
No. Google's page says consent mode communicates a visitor's choice to Google's tags and works with your banner or consent tool. It does not provide a banner.
What is Global Privacy Control and do I have to honour it?
Global Privacy Control (GPC) is a browser setting that tells websites a visitor opts out of the sale or sharing of their data. California's Attorney General page says it must be honoured as a valid opt-out by covered businesses. Do not assume it is required in every other state. Check each state's law.
Does my website builder add a cookie banner for me?
It depends on the builder. Ploy's docs say it does not add a banner and that you must connect your own to its consent function. Check your builder's help pages, then test that tags really wait for a choice. See what Ploy is for that example.
Do I need a reject button on the first layer of the banner?
Regulators such as France's CNIL expect refusing to be as easy as accepting, and many tools put a reject button on the first layer. Some legal commentary points out that the GDPR text is silent on this. The safe choice is equal-weight buttons on the first layer.
How often should I test my banner?
After setup, after any new tag or widget, after a redesign and at least once a quarter. Tags added by an agency or a plugin are the usual cause of silent failures.
Are visitor identification tools affected by cookie consent?
Yes. Tools that match visits to companies or people raise extra questions, and some are US-only. Read whether it is legal to identify website visitors and whether visitor tracking is allowed under privacy law before turning one on.
More in this topic: Websites: legal and trust basics (7 guides) →