Google Analytics

Google Analytics is Google’s own measurement tool, and it has been the industry default for so long that most business owners assume it is just part of having a website. It counts visits, tells you which page someone landed on, which one they left from, and whether they came from a search, an ad, or a link somebody sent them. None of that is exotic. What matters is whether it is set up honestly, and whether it survives contact with a browser that does not want to be tracked.

That second part is where most installs quietly fail. A huge share of visitors now run ad blockers or privacy extensions that specifically target the standard Google Analytics script. When that script gets blocked, the visit still happens, the phone still rings, the form still gets submitted, but the report shows nothing. You end up making decisions off a number that has already been filtered by whoever is best at avoiding measurement, which is a strange way to run a business.

Why it matters to you

If you cannot see which pages and channels actually produce calls and bookings, every marketing decision is a guess dressed up as a strategy. Google Analytics, done properly, is the record that tells you whether the money going into the site and into Google Ads is doing anything. It is also the format your bookkeeper, your ad platforms, and most outside consultants expect, so having it in place keeps you compatible with everyone else’s tools.

How I set it up

I do not drop the standard Google tracking script straight into the page and call it done. On the sites I build, Google Analytics loads through Cloudflare’s own infrastructure instead of running as a client-side tag, in place of a conventional tag manager setup. That keeps the numbers from quietly disappearing when a visitor’s browser fights back, which is the whole point of ad blockers as a category worth understanding rather than ignoring.

The account itself is created under the client’s own login, never mine, so the history stays theirs from day one. I connect it to lead tracking so that a phone tap, a form submission, or a booking click gets recorded as a real event rather than an anonymous pageview, and I wire the results into Google Ads so the advertising can be judged on actual bookings instead of clicks.

What it looks like in practice

Day to day, you will not open Google Analytics unless you want to. What you will get instead is a plain-language monthly report that pulls from it, telling you how many people visited, called, and booked, in words rather than dashboards. If you do log into the account yourself, you will see real numbers that match what your phone and your booking calendar already told you, because the measurement was built to survive the browsers trying to hide it rather than to look impressive in isolation.

The quiet win is what does not happen. Nobody spends a marketing budget for three months only to discover the tracking never worked, because the setup was checked against real ad blockers before it went live, not after the invoices started arriving.