Most businesses have GA4 installed and still cannot answer the only question that matters: which channel brought the customer. I set up analytics, conversion tracking and reporting so every enquiry is traceable to the ad, page or search that produced it.
Nearly every account I open has at least two of these three problems.
01
GA4 is collecting page views and nothing else. You can see that people visited; you cannot see that eleven of them clicked WhatsApp. Every decision after that is made on traffic, which is the least useful number on the screen.
02
Links shared without UTMs, ads landing on untagged URLs, referrals stripped by redirects. The channel that is actually working disappears into a bucket that tells you nothing, so budget goes to whatever is easiest to see.
03
Your own visits, your developer, a preview environment and a scraper or two, all counted as users. On a small site that can be a quarter of the traffic, and it quietly flatters every number you look at.
Good analytics is not more dashboards. It is a small number of numbers you can actually trust — and act on.
Collection, conversions, attribution and reporting — set up once, correctly, in accounts you own.
Property and data stream configured, internal and developer traffic excluded, data retention set to the maximum, cross-domain handled if you have more than one site, and unwanted referrals filtered out so payment gateways stop stealing credit for your sales.
Form submissions, WhatsApp clicks, phone taps, email clicks, PDF downloads and booking completions each tracked as their own named event and marked as a key event — so “conversions” means enquiries, not scrolls.
Verified, sitemap submitted, indexing issues surfaced, and linked to GA4 so organic queries and landing pages sit alongside behaviour data instead of in a separate tool you forget to open.
Pixel installed with the right standard events, deduplicated against server-side Conversions API where it is worth doing, so Meta can optimise on real leads instead of guessing from a browser that blocked it.
A naming convention for campaigns you can actually stick to, applied across ads, email, WhatsApp and social, plus custom channel groups — so six months from now the reports still make sense.
One dashboard pulling GA4 and Search Console into the numbers that matter for your business, plus a short walkthrough — recorded — so you can read it yourself instead of depending on me to interpret it.
What is installed, what is firing, what is double-counting and what is quietly broken. Most sites have at least one tag that has been wrong for months.
We write down the two or three actions that represent a real business outcome. Everything else is context, not a target.
Tags, events and filters shipped, then tested in DebugView and realtime — a conversion event is not done until I have watched it fire.
Dashboard built, walkthrough recorded, admin access left in your name. You should not need me to see your own numbers.
Tracking is set up once and then mostly left alone. I would rather do it properly, hand you the keys and have you not need me again than sell a monthly fee for reading a dashboard you could read yourself.
Everything is created in your Google and Meta accounts, with you as owner and me added as a user you can remove. That matters more than it sounds: agencies losing or withholding a client’s historical analytics data is depressingly common, and it is not recoverable.
Longer if there are several domains, a checkout flow, or a CRM to connect.
Events work immediately. Comparing periods honestly needs a month of clean collection first.
You are the admin. Historical data stays with your business, not with whoever set it up.
Probably, and here is the test: open GA4 and try to answer “how many enquiries did we get last month, and which channel sent them?” If you cannot answer that in under a minute, what you have is traffic counting, not analytics.
Installing the tag is about five per cent of the job. Defining conversions, filtering noise and tagging campaigns is the other ninety-five, and it is the part that usually was never done.
They will never match, and expecting them to will waste a lot of your time. Meta counts a conversion against the ad it thinks caused it, including view-throughs, using its own attribution window. GA4 counts sessions and applies its own model, and iOS privacy rules block a share of both.
The right approach is to pick one source as the decision-maker for each question — Meta for optimising campaigns, GA4 for comparing channels — and to watch the trend rather than argue about the gap.
Not always. On a small static site, direct gtag events are simpler, faster and easier to maintain than a container nobody understands.
GTM earns its place when there are many tags, several people changing them, or a developer bottleneck between you and a simple tracking change. I will recommend the lighter option when it fits, because an extra layer you cannot maintain is a liability.
The setup avoids collecting personal data in analytics — no names, emails or phone numbers in event parameters, which also happens to violate Google’s own terms. IP anonymisation is standard in GA4, and consent handling is included where your audience requires it.
If you sell into the EU or UK, say so early and a consent banner wired to Google consent mode becomes part of the scope rather than an afterthought.
Clicks, yes — a tap on a WhatsApp button or a phone number is an event like any other, and for most Indian small businesses those are the real conversions.
What a click cannot tell you is whether the conversation happened or went anywhere. Connecting that properly means call tracking numbers or a CRM, which is a bigger piece of work, and worth doing only once the click data shows enough volume to justify it.
Send me your site. I will tell you what is being measured, what is missing and what is being counted twice — before you spend anything.
