How to Set Up GA4: Tag, Events and First Reports
Google Analytics 4 setup in order: property and data stream, placing the tag, the events worth tracking, marking conversions and the first reports to read.
rabbitclip teamPublished: 7 min read
Short answer
Setting up GA4 means creating a property and a web data stream in your Google Analytics account, placing the measurement tag it gives you on every page of your site, deciding which events matter to your business, and marking the ones that bring revenue or enquiries as conversions. Once the tag is in the right place, basics such as page views start flowing on their own. The real work is defining the behaviour you want to measure up front, because GA4 only knows what you tell it, within the limits of your consent settings.
The setup fits into an afternoon, yet a correct one leaves a foundation that serves you for years. A careless one counts the same visitor twice, never shows a form submission, or lets your own team's browsing pollute the numbers. This article walks through the order, the decisions and the places people get stuck.
Cookie consent and consent mode are a separate subject, covered in our article on cookie consent and consent mode. Here we stay with the measurement itself.
What are a GA4 property and a data stream, and how do you create them?
A property is the container that holds the data of one site or app. A data stream defines the source that sends data into it; for your website you create a web stream. When the stream is created you receive a measurement ID. It starts with the letter G and decides which property the tag writes to.
Get the account structure right from the start. Open the account in the company's name, with a company administrator's address as owner. A property left inside an agency's or freelancer's personal account leaves your hands when the engagement ends. If you run several domains, keep them in one property when they are part of the same visitor journey and in separate properties when they are separate businesses.
How do you add the tag: directly or through a tag manager?
There are two routes. The first is to paste the tag code directly into the head of the site. The second is to install a tag manager such as Google Tag Manager and publish the GA4 tag from inside it. For a small one-page brochure site, direct placement is enough. For a site that will gain advertising pixels, form tracking and extra events, a tag manager is tidier, because you do not have to go back to a developer for every change.
Whichever you pick, never load the same tag twice. If the theme, a plugin and the tag manager all load GA4, every page view is counted twice. It is the most common mistake and the one noticed last.
- Direct placement: little upkeep, little flexibility; suits small sites
- Tag manager: easy to add events and pixels; needs versioning and publishing discipline
- Plugin: quick, but check that the same tag is not loaded somewhere else too
- After setup, open the real-time report in your own browser to confirm the tag fires
Which events should you track, and which should you mark as conversions?
In GA4 every interaction is an event: page views, scrolls, outbound clicks, file downloads, site search. Some of these are collected automatically through the enhanced measurement setting. But the events a business cares about most are usually defined by hand: form submissions, phone or WhatsApp taps, quote requests, purchases.
A conversion is an event that brings direct value to the business. In the interface the concept may also appear under the name key event; the idea is the same. Keep one rule for marking them: only mark an action that shows genuine intent to buy or to get in touch. If every page view becomes a conversion, the reports lose their meaning.
- Form submission: fire it on a successful submit, not on the button click
- Taps on phone, email and messaging links
- Reaching the quote or appointment request page
- In e-commerce, add to basket, begin checkout and purchase
Which reports should you read first after setup?
Do not dig into detail in the first week. Start with the acquisition report, which shows where traffic comes from: search, direct, social, ads, referring sites. Then see which pages are viewed and which events fire. Last, look at how many conversion events occurred and from which source.
If the numbers look wrong, suspect the setup before the business. Figures twice as high as expected usually mean a doubled tag; zeros point to a wrong ID or a blocked tag. GA4 does not process data backwards, so the days before installation stay empty. Delaying the setup means losing data.
What are the most common GA4 setup mistakes?
Most mistakes come from missing decisions rather than technical faults. The setup is done with no goal defined, and afterwards nobody knows what to look for in the reports. The second big one is failing to exclude your own team's and agency's traffic; on a small site it can drown out real visitors. Internal traffic should be defined and filtered out.
The third is forgetting consent. If visitor consent and measurement settings are not linked, either data goes missing or you take on legal risk, and a lawyer should advise on that. The fourth is leaving property settings such as data retention at their defaults. Choose the retention period knowingly.
- Loading the same tag from two places
- Marking too many events as conversions
- Not filtering your own traffic
- Not linking the ad account and Search Console
- Leaving the property in a personal account
When is GA4 not enough, or not needed?
GA4 shows what visitors did, not why. To understand why people drop off a page you may need heatmaps, session recordings or plain conversations with users. Visitors who decline cookies are also not fully reflected, so the numbers are an estimate of real traffic, not an exact count.
There are cases where it is not needed. For a static single page that works as a business card, is never updated and takes no advertising, a complex measurement plan is excessive. A lighter, cookie-free tool may be enough. What matters is that measurement feeds a decision: if nobody will open the report, there is no point in installing it.
Done in order, a GA4 setup is not tiring: property and stream, one tag, a few right events, conversion marking, then a short check. The next step is to write down the three actions that bring your business value and build the measurement around them. If you would like a second pair of eyes on whether your current setup works correctly, we would be glad to hear from you in a discovery call with rabbitclip.
FAQ
Do I need a developer to set up GA4?
Placing the tag in the site head or adding it with a plugin is something most site owners can do without a developer. Custom events such as form submissions may need a tag manager and sometimes a small code change.
When does GA4 data start to appear?
The real-time report shows you as soon as the tag fires. The standard reports need some time to process, so it is normal for them to look incomplete in the first days.
Does my old Universal Analytics data move into GA4?
No. The two systems use different data models, and the old data is not carried across as it was. If you need the old reports, keep your own archive of them.
Should GA4 be linked to Search Console and the ad account?
Yes, linking is worthwhile. The Search Console link brings search queries into the tool, and the ad account link passes conversion data to the advertising platform.
How do I know the tag is working?
Open the site in your own browser and try to see your visit in the real-time report. The preview mode of the tag manager and the debug view in GA4 also show which event was sent with which parameters.
