Skip to content
WEBSITE STRATEGY

Why Don't You Install Google Analytics on Our Website?

What a tracking script costs your visitors, when consent banners are really required, and how server-side analytics counts visits without either.

By Brĭmeli · · Updated

DIRECT ANSWER

Google Analytics runs a third-party script in every visitor's browser, sets cookies that require consent in some regions and misses visits when an ad blocker stops the script. Server-side analytics reads the host's own records of pages served instead, with no script, no cookies and no gap from ad blockers. To track leads, we count inquiries where they arrive.

Key terms

Client-side analytics
Measurement that runs as a script in each visitor's browser and sends data to an outside service, as Google Analytics does.
Server-side analytics
Measurement taken from the hosting provider's own records of the pages it served, with nothing added to the page.

Two ways to count visits

How client-side and server-side analytics compare
Google Analytics (client-side) Server-side analytics
Where it runs A script loads in each visitor's browser The host's records of the pages it served
Added to the page A third-party JavaScript file on every visit Nothing [1]
Cookies Yes None [1]
Ad blockers and disabled JavaScript Can stop the script, so the visit goes uncounted No effect on the data [1]
What it reports Detailed behavior, plus advertising and audience tools Page views, unique visitors, top pages and top locations [1]
Limits Undercounts visitors who block it Counts unique visitors by IP address, which is approximate [1]

The cost to every visitor

A script has to be downloaded and run on the visitor's phone before it can report anything. One script is modest. Analytics rarely travels alone, though: tag managers, ad pixels and chat widgets tend to follow it, and each one adds work for the phone before your page settles. Netlify describes its server-side method this way: "Since there's no client-side code involved, the performance of your site doesn't suffer" [1]. Core Web Vitals for business owners explains how speed is measured.

The rules depend on where your visitors are [2]:

  • In most of the EU and EEA, analytics cookies need opt-in consent before they load.
  • In the UK, analytics used only for statistics can run with clear information and a simple way to object, since February 2026. Analytics tied to advertising still needs consent.
  • In the US, state privacy laws generally don't require opt-in consent for analytics. Several require notice and an opt-out, and analytics that feeds ad targeting is regulated more tightly.

Many US sites show a banner anyway, to be safe. Whatever the reason, a banner over the first screen is the first thing a new client sees. Server-side analytics sets no cookies, so it doesn't call for one. Your own obligations depend on your audience and your other tools, so check them with your attorney.

What ad blockers do to the numbers

Ad blockers and privacy tools can stop analytics scripts from loading, and visits they stop go uncounted. Server-side records are kept by the host as pages are delivered, so Netlify notes that its data "isn't affected when your visitors use ad blockers or disable JavaScript" [1].

What no analytics tool tells you

Neither method tells you whether a visit became a client. Page views measure attention. Revenue starts with a received inquiry: a message that arrived, from someone you can trace to a source. Count those where they land, whether that's an inbox, a client portal or a phone log. Measure website leads beyond clicks shows how.

When Google Analytics still makes sense

If you buy Google Ads and need conversion data inside Google's tools, or a marketing team works in Google Analytics every week, it can be added with consent handled properly. Treat that as a decision with a cost to speed and to the first screen, made for a reason.

How Brĭmeli handles analytics

We don't add a tracking script to the pages we build. When you want traffic numbers, we turn on the host's server-side analytics. Lead tracking happens where inquiries arrive. The website plans include launch checks, analytics and form tracking on Day 0. To have that set up with a new site, start a project.

Sources and method

The comparison table is a Brĭmeli editorial summary. This entry is general information, not legal advice. Each linked source supports only the statements numbered beside it. Sources verified November 2, 2026.

  1. Netlify Docs: How Web Analytics works
  2. CookieChimp: Do analytics cookies require consent? (June 16, 2026, updated October 29, 2026)