Google Analytics Property: Find, Fix or Create One in GA4
By Toy Wen Da, Co-Founder · Updated · 6 min read · scored 93/100
A Google Analytics property is the container that holds the tracking setup and data for one website or app, identified by its own Measurement ID (the "G-" code). To find yours, open Admin in Google Analytics, pick the right account, then look in the Property column.
If you're hunting for your property because a traffic number looks off, SearchBlueprint's site traffic feature pulls your Google Analytics, Search Console and AI-referral data into one screen, so you can sanity-check the figures before digging through GA4's menus.
How to find your Google Analytics property and Measurement ID
Open analytics.google.com and sign in with the account that has access. Then:
- Click the gear icon labeled Admin in the lower-left corner.
- In the middle Property column, confirm you're looking at the right one. The dropdown at the top of that column lists every property you can access.
- Click Property details (sometimes labeled Property Settings) to see the Property ID and creation date.
- To get the Measurement ID, click Data Streams under the Property column, then select the web stream for your site. The ID (G-XXXXXXXXXX) sits near the top of that screen, next to the stream's URL.
If nothing shows up at all, you likely don't have access yet. Ask whoever set up the account to add you as a user at the property level, not just the account level, since permissions don't automatically cascade down in every direction.
How to create a new Google Analytics property
Starting from scratch is just as fast:
- From Admin, click Create Property at the top of the Property column (or the + button next to an existing one).
- Enter the business name, reporting time zone and currency.
- Add a data stream by choosing Web, iOS app or Android app. For a website, enter the URL and turn on Enhanced Measurement.
- Copy the Measurement ID and install it via the Google tag snippet on your pages, or through Google Tag Manager if you already use it.
Give the new property a few hours to start showing data in the Realtime report before assuming something is broken.
One property or several? How to decide
Most people land here with one question: should a new site get its own property, or share the one you already have? Bounteous' breakdown of this decision lists factors that still apply, even though the interface has since moved from Universal Analytics to GA4.
Under the old Universal Analytics setup, Google's own Analytics Help documentation confirmed a standard property was capped at 10 million hits a month, 50 properties per account and 25 views per property, and sampling kicked in on custom reports once a date range passed 500,000 sessions, when you'd see a banner reading something like "this report is based on 498,630 sessions (47.36% of sessions)." GA4 replaced views with data streams and changed the thresholds, but the underlying trade-off hasn't moved: combine sites for unified reporting and cross-domain tracking, or separate them for cleaner settings and data governance.
| Factor | Keep one property | Use a separate property |
|---|---|---|
| Reporting | You need one combined total across sites | Each site needs its own clean numbers |
| Cross-domain tracking | Required, users move between the sites mid-session | Not needed, sites are unrelated |
| Search Console | You only have one site to link (a property links to just one) | You have multiple Search Console properties to connect |
| Team access | Everyone can share edit rights | Different teams need separate, isolated permissions |
| Data volume | Combined traffic stays well under reporting limits | One site is already high-volume on its own |
When GA4's own tools are enough, and when they're not
For a single site and a one-off check, GA4's own screens are usually plenty. Realtime confirms the Measurement ID is firing, DebugView catches a misconfigured event, and Admin settings handle property-level access and linking.
GA4 alone starts to strain in a few places:
- Across multiple properties: GA4 won't total numbers from separate properties for you, so you're copying figures manually or exporting to a spreadsheet.
- Recurring monitoring: checking the same property every week for drops in organic traffic, crawl issues or AI referrals means re-running the same reports each time.
- Cross-source answers: GA4 tells you what happened on your site but doesn't explain why rankings moved or which keywords brought the traffic. For that you'll pair it with Search Console, and our breakdown of Google Search Console vs Google Analytics: The Real Difference shows which tool answers which question.
- Behavior visuals: GA4 has no built-in heatmap. If someone asked you to "pull up the heatmap in Analytics," read what GA4 gives you instead of a heat map before assuming the feature exists.
- Conversion diagnosis: GA4 shows conversion counts and funnel steps, but turning a drop into a fix is a different skill. Our guide on using Google Analytics for conversion optimization helps when a number is moving the wrong way and you're not sure which lever to pull.
Common mistakes with Google Analytics properties
- Reporting from the wrong property is easy when an account holds a legacy Universal Analytics property alongside the live GA4 one, so check the Property ID before trusting any number.
- Creating a second GA4 property for the same site by accident, usually by pasting the setup snippet twice, splits traffic between two Measurement IDs.
- Never linking Search Console means organic query data never shows up alongside the rest of the property's traffic.
- Giving account-level edit access when only property-level access was needed lets someone change settings on properties they shouldn't touch.
- Tracking staging or dev environments in the production property adds internal testing traffic to your session counts.
FAQs
What's the difference between a Google Analytics account and a property?
An account is the top-level container, usually one per business, that holds billing and top-level user access. A property sits inside the account and holds the actual tracking setup and data for one site or app, identified by its Measurement ID.
How do I find my GA4 Measurement ID?
Go to Admin, click Data Streams under the Property column, then open the web stream for your site. The Measurement ID (G-XXXXXXXXXX) appears near the top of the stream details.
Can one website have two Google Analytics properties?
Yes, technically, but it's rarely intentional. It usually happens when a tracking tag gets installed twice with different IDs, which splits your traffic and makes every report incomplete.
Do I need a separate property for a subdomain?
Not usually. Subdomains typically belong in the same property as the main domain, either as a separate data stream or with cross-domain settings enabled, so sessions stay unified.
Why can't I link my Google Analytics property to Search Console?
Each Search Console site can only connect to one Analytics property at a time. If it's already linked elsewhere, you'll need to unlink it there first or confirm which property should own that connection.
Check your property's numbers today
Pick one thing from this page and do it now: open Admin, confirm which Google Analytics property your reports are actually pulling from, and check that it's linked to the right Search Console site. If the numbers still don't add up across Google Analytics, Search Console and AI referral traffic, SearchBlueprint's site traffic feature lines all three up in one place so the discrepancy is easier to spot. You can see what that looks like on a real site in this sample SEO report.
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.