How-to · Beginner · 30 minutes

How to Add Google Analytics

Everything you need to measure your audience properly, with consent handled the way it should be — the steps in order, the snag to watch, and the tip our support desk gives everybody.

See the plans Ask us a question

Straight answer first

The job: measure your audience properly, with consent handled the way it should be. Time to allow: 30 minutes. Skill needed: beginner.

Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.

Written by the Hosting Seller staff · Checked 1 August 2026

Beginner

Difficulty level

30 minutes

Time to allow

Stages

24/7

Help at any hour

You do not need to be technical for this. The walkthrough is written for first-timers, tested on our own platform, and honest about which parts are genuinely fiddly and which are merely unfamiliar.

One promise before you start: nothing in this guide is irreversible. Where a step could bite, we say so and give you the undo.

The overview before the detail

Here is the route in full: set up the ga4 property, add the tag by plugin or by hand, put consent in front of it, confirm it with the realtime report and track the handful of events that matter.

Each stage is a few minutes of steady clicking — the time it takes depends mostly on how familiar the control panel already feels. The detailed steps sit further down this page; skim the whole route once before you begin.

The mistake nearly everyone makes

The double install. A plugin and a hardcoded snippet both firing inflates every number by half again, and the discovery usually arrives after months of confidently wrong decisions.

Forewarned really is forearmed here. This one mistake accounts for most of the frustration the subject produces, and it is entirely avoidable once somebody names it.

The trick worth borrowing

Consider self-hosted Matomo, one click away in Softaculous, as the privacy-forward option. Your data stays on your own hosting, nothing is handed to a third party, and the consent conversation gets a good deal shorter.

Small habits like this are the real difference between people who find hosting easy and people who find it stressful. The tools are identical; the working method is not.

The parts we have already done for you

Several steps in this guide exist only because hosting historically made you do them. On our plans SSL issues itself, backups run daily without being asked, and one-click installers replace the manual setup entirely. What is left is the part that is genuinely yours.

Stuck halfway through at an odd hour? That is exactly what round-the-clock human support is for — tell us where you are in this guide and we will pick it up from there.

A rising chart standing in for a website that keeps growing

Why the job is simpler on our plans

Tutorials age badly when they are written against imaginary hosting. These are written against ours: the same panel, the same installer and the same defaults you will meet.

Real people answer the counter at any hour, including the awkward questions other hosts wave off as out of scope.

Step by step, tested exactly as printed
The snag flagged before you reach it
The dull steps are already automated
People on hand at any hour if you stall

Why Hosting Seller

On every plan, as standard

Automation where it belongs

SSL, backups and installs run themselves here, so the guide covers only what is genuinely yours to do.

Works exactly as written

Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.

5 steps, no filler

Each stage is a few minutes of steady clicking, with the fiddly parts marked as fiddly.

Written from real tickets

Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.

The snag, named early

The classic mistake for this exact job is flagged before step one, so 30 minutes stays 30 minutes.

Scoped honestly

Measure your audience properly, with consent handled the way it should be is a beginner-level task — this guide budgets 30 minutes and says which steps the platform absorbs.

First Steps

From choosing to live

1
Set up the GA4 property
Create the property and a data stream for your domain. The measurement ID, the one beginning with G-, is the only thing the site needs from that screen.
2
Add the tag by plugin or by hand
An analytics plugin, or the theme's header snippet slot, puts the tag on every page. Plugins add dashboards; a snippet adds nothing but the tag. Both work perfectly well.
3
Put consent in front of it
Your cookie banner should gate analytics according to each visitor's choice. Measurement respects the consent layer, and never the other way round.
4
Confirm it with the realtime report
Visit your own site and watch the realtime report. Seeing yourself appear confirms the whole pipe, from the page to the property, in about ten seconds.
5
Track the handful of events that matter
Form submissions, key clicks, purchases. A few deliberate events beat a dashboard full of defaults that nobody ever opens twice.

In the Box

Packed with every plan

SSH, Git and Composer on the plans built for developers
LiteSpeed caching running at the server, not bolted on by plugin
The renewal price printed on the tag matches the order price
Mailboxes that carry your own domain name
Webmail in the browser plus IMAP, POP and SMTP for your own client
DDoS filtering handled out at the network edge
One-click installs for WordPress and 400+ other applications
Nothing added at setup — no joining fee, ever
A backup taken daily, with restores you run yourself
The Softaculous installer for one-click application setup

Across the Counter

The questions we get asked most

Analytics shows nobody, but the site clearly has visitors.

Either the tag is not firing — visit the site yourself and watch realtime — or the consent banner is blocking by default, or an ad-blocker is stopping it in your test browser. The realtime self-visit test tells you which in two minutes.

Does the analytics tag slow the site down?

Only slightly, since an async tag loads off the critical path. Keep to one analytics system and load it the standard async way. The cost is real but small measured against knowing where your visitors come from.

Can I bring a domain I already own?

Yes, and transfers in are routine. Unlock the name at your present registrar, collect the auth code, then start the transfer from your client area. Whatever registration time is left comes across with it, and DNS keeps answering the whole way through.

Do you shift an existing site across at no charge?

We do. Open a ticket with the login details for your current host and the whole lot comes over: files, databases, mailboxes and configuration. You check the copy before DNS changes hands, and the old site keeps serving customers until the new one takes the traffic, so nobody ever sees a gap.

Can I test changes somewhere safe first?

Yes — plans with staging let you clone the live site, work on the copy, then push it across when you are satisfied. It is the difference between hoping an update behaves and knowing that it does before any customer meets it.

Where do the servers actually sit?

Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.

Can one plan hold more than a single website?

From the Pro tier upward, yes — several sites, each with its own domain, mailboxes and certificate, all under one account. If those extra sites belong to clients rather than to you, reseller hosting is the better fit: it gives each one proper separation.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

Whenever you're ready to order.

From a first website to a rack of servers, moving up is a change to your account rather than a migration.

See the plans