Most people don't get stuck on the *steps* of setting up Google Analytics. They get stuck one level up — on what an account is versus what a property is. Get that wrong and you end up with traffic landing in the wrong bucket, or a tangle of accounts you can't cleanly hand off later.
So before the click-through, here's the distinction that actually matters.
---
Account vs Property, in One Breath
GA4 stacks like this:
Organization → Account → Property → Data stream
An account is the top-level container. It usually maps to one business or legal entity — "Sun Life Malaysia," "DCXTribe." It governs terms of service, user access, and who can see what. One account can hold up to 2,000 properties.
A property is where the data actually lives. It's one analytics database for one site, one app, or a combined web+app experience. It has its own Measurement ID — the tag you paste into your site — and that ID is what routes data to *this* property and no other.
Below the property sit data streams (Web / iOS / Android), which replaced the old "views" from Universal Analytics.
The rule of thumb:
New account → a separate business or legal entity (different owners, contracts, teams) New property → a different site/app/user base, but still the same business
DCXTribe is a new *site* under an existing business, so the right move was a new property — not a new account.
---
What You're Setting Up
You → Google tag on your site → GA4 property → reports you can actually use
A few minutes of clicking, then a snippet of code on your site. That's the whole job.
---
Before You Start
1. A Google account with access to a GA4 account (the container) 2. The site URL you want to track (e.g. https://www.dcxtribe.com) 3. Edit access to your site's HTML <head> — directly, or via a CMS/plugin
---
Step 1: Create the Property
In Google Analytics: Admin → Create → Property.
Fill in three things — and they matter more than they look:
Property name : DCX Tribe Time zone : Malaysia (GMT+08:00) Currency : Malaysian Ringgit (RM)
The time zone sets when your "day" rolls over in reports. The currency only matters if you ever track revenue, but it's annoying to change opinions later — set it correctly now.
---
Step 2: Answer the Business Questions
GA4 asks for context to pre-configure your reports. These aren't load-bearing, but answer them honestly:
Industry : Online Communities Business size : Small (1–10 employees) Objectives : Generate leads + Understand web/app traffic
The objectives you pick just change which default reports GA surfaces first. You can change them anytime.
---
Step 3: Create a Web Data Stream
This is the part that connects GA to your actual site. Add a Web stream pointing at your URL:
URL : https://www.dcxtribe.com Stream ID : (auto-generated)
When the stream is created, GA hands you a Measurement ID — it looks like G-XXXXXXXXXX. That ID is the bridge between your site and this property.
You should see: a confirmation screen with the stream listed and a G- ID visible.
---
Step 4: Install the Google Tag
Copy this into the <head> of every page on your site. Replace G-XXXXXXXXXX with your own Measurement ID:
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXXXXX');
</script>On WordPress, Webflow, or most CMS platforms, you don't touch raw HTML — paste the ID into the header-script setting or a GA plugin instead.
Data starts flowing within 24–48 hours. It is not instant. Don't panic at an empty report on day one.
---
Common Problems and Fixes
Problem: You created a whole new account by mistake
This is the most common one. If your new site belongs to a business you already track, you wanted a property, not an account. Delete the stray account and re-create the property under the right one — before you've shared access with anyone.
Problem: No data after a day
Check three things, in order:
[ ] The tag is in the <head>, not the <body> [ ] The Measurement ID in the snippet matches the one in your stream [ ] You're looking at the right property (easy to mix up with multiple sites)
Problem: Reports show the wrong "day"
Your time zone was set wrong at creation. Fix it in property settings — but know that historical data won't retroactively shift.
---
Quick Checklist
[ ] Property created under the correct account [ ] Time zone and currency set correctly [ ] Web data stream added with the right URL [ ] Measurement ID copied [ ] Google tag installed in <head> of every page [ ] Waited 24–48 hours before checking for data
---
What's Happening Under the Hood
Account → who owns and can access the data Property → the database that stores and reports your events Data stream → the pipe that carries events in from one source (web/app) Measurement ID → the label on that pipe, so events land in the right property
Get the hierarchy right once and everything downstream — Google Ads links, BigQuery export, user permissions — clicks into place at the property level where it belongs.
---
*All views are my own. This guide is shared for learning and experimentation.*