New format
How to set up Google Analytics 4: a beginner’s guide
To see traffic and events you need a Google account, a GA4 property, a website data stream, and a tag on your pages. Old guides about “UA-XXXX and views” are outdated — below is GA4 logic for beginners.
The Analytics UI moves — lean on Google Help and the meaning of each step. Goals / key events, ecommerce, and UA differences live in neighboring articles.
Account, property, and data stream
Sign in to Google Analytics → create an account (your company) → a GA4 property → a Web data stream with the site URL and a stream name.
Set report time zone and currency with intent — they define day boundaries and money in ecommerce. Industry and business size feed Google’s tips, not magic accuracy.
Hierarchy in short:
- account — the organization
- GA4 property — the data container
- stream — site or app
- measurement ID (G-XXXX) — for the tag
Putting the tag on the site
Option A: paste the global gtag.js snippet (or the wizard’s code) on every page, usually in `<head>`. On a CMS — via theme, plugin, or GTM, not “homepage only.”
Option B: Google Tag Manager — container on the site, then a GA4 Configuration / Google tag with the stream ID. Easier to add events without editing code every time.
Confirm HTTPS has no mixed content and the tag isn’t firing twice (double page_view wrecks reports).
Install checks:
- Realtime shows you on the site
- DebugView sees events while debugging
- no second identical counter
- internal IPs can be excluded later
What to turn on right after install
In the stream, enable enhanced measurement on purpose (page views, scroll, outbound clicks, site search — as needed). Link Google Ads if you run ads; remarketing and Google signals only within consent and policy.
Next: key events (conversions), ecommerce events for a store, internal traffic filters. Don’t wire User-ID and complex cross-domain “just in case” without a real job.
Beginner order:
- tag works in Realtime
- 2–5 key events marked
- the team has property access
- cookie / consent policy covered
- plan: ecommerce or goals — via the links below
FAQ
Should I still set up Universal Analytics?
Not as the foundation. Create GA4. Skip old instructions with “views” and analytics.js.
Code in `<head>` or Google Tag Manager?
Both work. GTM is easier when you have many tags (Ads, pixels, events). For one counter, gtag.js on the site is fine.
How many properties can I create?
Account and property limits are in current Google Help. At the start — one GA4 property per site (or a site+app pair if that’s the job).
When does data show up?
Realtime / DebugView — almost immediately after a correct install. Full reports lag; don’t expect “like yesterday in UA” in the first minute.
Do I need cookie consent?
Yes — follow your privacy policy and regional consent rules. Don’t put personal data in event parameters.
Still installing UA views — and Realtime shows nothing in GA4?
We’ll create a GA4 property and web stream, wire gtag or GTM once, and verify in DebugView before chasing ecommerce.
Discuss the task
