Website Analytics Setup: What to Track and Why It Matters

By Grocito12 October 2026

A good website analytics setup starts with the business questions you need answered, not with the tool. Decide what counts as a conversion, such as a form submission, a call or a purchase, track those as events, tag your campaigns consistently, respect visitor consent, and review the numbers on a regular schedule. Everything else is secondary.

Key takeaways

Begin with questions such as "which channels bring enquiries we actually win?" and only then choose what to measure.
Define two or three conversions that matter and track them as events, rather than relying on pageviews alone.
Consistent UTM tags and a clean filter for internal traffic make your data far more trustworthy.
Consent and privacy rules vary by country; build a consent flow deliberately instead of bolting it on.
A short monthly review that leads to decisions is worth more than a dashboard nobody opens.

Start with business questions

Most analytics accounts are installed once, left on default settings and never questioned. The result is a lot of numbers and very few answers. Before you touch Google Analytics or any other tool, write down the five or six questions you would genuinely like answered. For example:

Which pages and channels lead to enquiries or sales?
Where do visitors drop out of the journey from landing page to contact form?
Which campaigns deserve more budget, and which should stop?
Do mobile visitors behave differently from desktop visitors?
Which enquiries become paying customers?

Each question tells you what to track. If a metric does not help answer any of them, you can usually ignore it.

Define goals and conversions

A conversion is an action that moves a visitor towards becoming a customer. Choose a small number and name them clearly.

Common conversions for business websites

A contact or quote form submission.
A click on a phone number or a WhatsApp or email link.
A booking or demo request.
A purchase or a completed checkout, for online shops.
A file download that signals buying intent, such as a pricing guide.

Micro-conversions

Smaller steps, such as starting a form, viewing the pricing page or adding a product to a basket, help you see where people stall. Track them, but do not confuse them with the real goal. A visitor who watches a video has not yet become a lead.

Events, not just pageviews

Older analytics tools centred on pageviews. Current tools, including Google Analytics 4 style setups, treat nearly everything as an event: a page view, a scroll, a click, a form submit. This is more flexible, but it means you must decide which events matter and name them consistently.

Good event hygiene

Use a short, predictable naming pattern, for example the same verb and object order every time.
Add useful parameters, such as the form name or product category, but avoid personal data such as names or email addresses.
Mark only your real conversions as key events, so reports stay readable.
Test every event with the tool's debug or preview mode before trusting it.

A common failure is a form that shows a thank-you message without changing the URL, so no event ever fires. Always submit a real test enquiry and confirm that it appears.

Tag your campaigns with UTMs

When you share a link in an email, an ad or a social post, add UTM parameters so your analytics knows where the visit came from. Typical fields are source (where), medium (the type of channel) and campaign (the name). The tags are simple, but inconsistency ruins them: "Email", "email" and "e-mail" show up as three separate sources.

Keep a shared spreadsheet that lists the allowed values, use lowercase throughout and never add UTM tags to links within your own site, since that resets the visit's original source. If you run social media marketing or paid campaigns, this one habit makes channel comparison possible.

Consent and privacy

Analytics often involves cookies or similar identifiers, and rules on consent differ between countries and sectors. Some regions require opt-in before non-essential tracking, others are more relaxed, and contractual or industry obligations may add more. We are not lawyers, so confirm your obligations with a qualified adviser. In practice, some sensible habits apply almost everywhere:

Show a clear cookie or consent banner where required, with a genuine choice to decline.
Load analytics and advertising tags only when the visitor's choice permits it.
Never send names, email addresses or phone numbers into analytics events.
Keep your privacy policy accurate about what you collect and why.
Expect some visitors to decline, so treat your numbers as a sample of behaviour rather than a perfect count.

Tag management basics

A tag manager, such as Google Tag Manager, lets you add and change tracking code without editing the website each time. It is useful, but it can also become a dumping ground. Keep it tidy:

Give every tag, trigger and variable a clear name.
Use a preview mode and publish with notes, so changes can be traced.
Limit who can publish changes, because a wrong tag can break forms or slow the site.
Remove old tags from tools you no longer use.

Heavy tag setups also affect loading speed, which ties into Core Web Vitals.

Clean data: filters and sanity checks

Your own team's visits can distort a small website's numbers. Exclude internal traffic by IP address or a similar method, and filter out known bots where your tool allows. Check also that:

Only one analytics tag fires per page, to avoid doubled pageviews.
Your domain is not counted as a referral to itself, which hides the true source.
Payment or booking gateways do not break the session and mark returning visitors as new referrals.
Search Console is connected, so you can see the queries and pages that bring organic visitors.

Avoid vanity metrics

Pageviews, follower counts and raw visitor totals feel good, but they rarely drive decisions. Prefer measures tied to outcomes.

Instead of total visits, look at enquiries by channel.
Instead of time on site alone, look at whether people reach the contact or pricing page.
Instead of the number of leads, look at how many became qualified opportunities.
Instead of the average of everything, segment by device, location or campaign.

If a number goes up and you would not change anything because of it, it is probably vanity.

Build a dashboard and a monthly routine

A dashboard should answer your original questions on one screen: traffic by channel, conversions by page or campaign, and a few funnel steps. Keep it short. Our guide to choosing the right dashboard metrics goes deeper, and if you need combined reporting from several sources, our data analytics team can help.

A simple monthly review

Check that tracking still works: submit a test form and confirm the event.
Compare conversions by channel against the previous month and the same month last year.
Pick one page or campaign to improve and one to pause.
Write down the decision and the date, so you can judge it next month.

Connect analytics to your CRM

Analytics tells you who visited and what they did. It cannot tell you whether an enquiry turned into revenue. To close that gap, pass the campaign source, medium and landing page into hidden form fields, and store them against the lead in your CRM. Then you can compare channels by closed deals rather than clicks. A system such as our CRM and lead management product is built around capturing this kind of source information, and our guide on how to choose a CRM explains what to look for.

A worked example

Imagine a small training company whose website brings in enquiries through a contact form and a phone number. At present it tracks only pageviews. It decides on two conversions, form submissions and phone-number taps, adds both as events, tags its email newsletter and social posts with consistent UTMs, and adds hidden fields so each lead in its CRM records the source. After a couple of months, it notices that one channel brings plenty of visits but few qualified leads, while a quieter channel produces most of the paying students. It moves effort accordingly. The tool did not decide anything; the clear questions and clean data made the choice obvious.

FAQ

What should I track on my business website?

Track the actions that lead to revenue: form submissions, calls, bookings or purchases, plus a few supporting steps such as pricing page views. Add traffic source information so you can compare channels. Everything else is optional.

Do I need Google Tag Manager?

Not always. A very small site can add its tracking code directly, but a tag manager becomes helpful when you run several tools or change tracking often. Use it with care and clear naming.

How do I stop my own visits being counted?

Exclude your office IP address or use the internal traffic filter in your analytics tool, and test again afterwards. Remote teams may need a different method, such as a browser extension or a specific cookie.

Is a cookie banner always required?

Not everywhere, and the rules depend on your visitors' locations and the kind of tracking used. Check with a qualified legal adviser rather than copying another site's banner.

Next steps

Write down your five key questions, choose two or three conversions, and test that each fires correctly this week. Then add UTM tags to your next campaign and set a calendar reminder for a monthly review. If you would like help with tracking, reporting or an SEO audit that includes analytics, contact us and we will talk it through.