What is a Google Analytics 4 Account?

If you've spent any time with website analytics, you've witnessed the mandatory shift from the classic Universal Analytics (UA) to Google Analytics 4. This article will demystify the new GA4 account structure from the top down, explaining exactly what an account is and how its new components - Properties and Data Streams - work together to track your performance.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The New GA4 Account Hierarchy: A Quick Overview

Before diving into the details, it's helpful to understand the new chain of command in Google Analytics 4. The entire structure is designed to give you a more unified view of your user's journey, whether they're on your website, your iOS app, or your Android app. The hierarchy is organized in four neat layers:

• 1. Organization (Optional): The highest possible level. It’s an optional layer that represents your company and allows you to manage multiple Google Analytics accounts from one place. Most small to medium-sized businesses won't need to interact with this layer directly, as its main purpose is to manage user permissions and product integrations across a large corporation.
• 2. Account: This is the container for your business. An Account is not your website, it's the folder that holds the data for your website(s) and app(s). A single business should have a single Google Analytics account.
• 3. Property: A Property lives inside your Account and represents a single digital asset, like your main company website, your blog, or your mobile app. This is where your reports live and where you'll conduct your analysis.
• 4. Data Stream: A Data Stream lives inside your Property. It’s the specific source of data flowing into that property. For example, your website is one data stream, and your iPhone app would be another.

Think of it like a filing cabinet. The entire cabinet is your Organization. Each drawer is an Account for a specific business. Inside a drawer, each hanging folder is a Property (e.g., "CompanyWebsite.com"). And within that folder, the individual papers coming in are your Data Streams (e.g., website traffic data, app usage data).

What is a Google Analytics Account? The Top Level

The "Account" is the highest level of organization that most users will directly manage. It's the primary bucket that holds all the analytics setups for your business. It's important to clarify the distinction between a "Google Account" and a "Google Analytics Account."

• A Google Account is your personal login (e.g., your.name@gmail.com). You use this to sign in to all Google services, including Google Analytics, Gmail, and Google Drive.
• A Google Analytics Account is the container you create inside Google Analytics to manage your properties for a specific business or set of websites.

You can manage multiple Google Analytics Accounts from a single Google Account login. For instance, if you're a marketing freelancer, you might have access to the Google Analytics Accounts for all your clients through your one personal Google login.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Key Functions of the GA4 Account

The account level is primarily for administrative management. It’s where you control high-level settings that apply to everything within it. The most common tasks you'll perform at this level include:

• User Management: Adding or removing team members and assigning their roles (Administrator, Editor, Analyst, Viewer). Permissions granted at the Account level cascade down to all Properties within that account.
• Account History: Viewing a change history log to see who modified settings and when.
• Filtering (Internal Traffic): While most filtering happens at the Property level, defining internal IP addresses for exclusion is an account-level setting.

Best practice is simple: one business gets one Google Analytics Account. Even if your business has multiple websites, brands, or apps, they should almost always live as different Properties inside a single overarching Account representing your company.

Understanding GA4 Properties: Your Digital Assets

Moving one level down, we arrive at the Property. A GA4 Property is where the magic happens. It represents a single user base that exists across your website and mobile apps. This is the place where your data from various sources is collected, processed, and consolidated into the reports you use to make business decisions.

This is a fundamental shift from Universal Analytics. In UA, you had a "Web" property for websites and in later years, an "App + Web" property trying to bridge the gap. GA4 simplifies this entirely. There is just one type of property, designed from the ground up to receive data from any combination of websites and apps simultaneously.

Key Functions of the GA4 Property

This is where you'll spend most of your setup and configuration time, as settings here dictate exactly how data is collected and reported.

Property Level Settings

• Data Settings & Retention: Here, you define how long Google stores user-level data (either 2 or 14 months) before being deleted. You also manage Google Signals, which allows you to collect data from users who have enabled ad personalization, enabling more advanced demographic and interest reporting.
• Product Linking: The Property level is where you create crucial integrations with other Google tools. Linking your GA4 Property to Google Ads lets you import conversion data for ad optimization. Linking to Google Search Console pulls keyword and search query data directly into your GA4 reports. You can also link to BigQuery for raw data export, Merchant Center for e-commerce, and more.
• Reporting Identity: You can choose how GA4 identifies individual users across different devices and sessions. The blended model uses User-ID (if you provide it), Google Signals, Device ID, and modeling to create the most accurate journey map.
• Custom Definitions: This is where you register custom dimensions and metrics that are unique to your business. For example, if you collect an "Author" for your blog posts as an event parameter, you need to register it as a custom dimension here to use it in reporting.
• Conversions: You can mark specific events (like purchase or generate_lead) as conversions at the property level, signaling to GA4 which user actions are most important to your business.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Introducing Data Streams: The Funnels for Your Data

Data Streams are a brand-new concept in GA4 and the source of a lot of initial confusion. At its core, a Data Stream is simply a specific flow of data into your GA4 Property. You create a separate data stream for each platform you want to track.

There are three types of data streams you can set up inside a single property:

1. Web Stream (for a website)
2. iOS App Stream (for an iOS application)
3. Android App Stream (for an Android application)

For example, if your business has a marketing website and an iOS app, your GA4 setup would look like this:

• 1 Account: "My Company"
• 1 Property: "My Company - Brand Analytics"

GA4's event-based data model allows it to seamlessly merge the data from both of these streams. A user who visits your pricing_page event on the website and then triggers the start_trial event in the app can be analyzed as part of a single, cross-platform journey.

Measurement ID and Enhanced Measurement

When you create a Web Data Stream, GA4 gives you a unique Measurement ID, which looks like G-XXXXXXXXXX. This is the only ID you need to start collecting website data. You add this ID to your website via the Google Tag (gtag.js) script or through Google Tag Manager. It tells Google where to send the data.

Web Streams also come with a powerful feature called Enhanced Measurement. When enabled (which it is by default), it automatically tracks a set of important user interactions without you needing to write any extra code. This includes:

• Page views: Every time a page loads.
• Scrolls: When a user scrolls 90% of the way down a page.
• Outbound clicks: Clicks that lead users away from your domain.
• Site search: What your users are typing into your site's search bar.
• Video engagement: Plays, progress, and completes for embedded YouTube videos.
• File downloads: Clicks that trigger a file download (e.g., PDF, DOCX).

This automated tracking gets you much richer data right out of the box compared to the minimal setup of Universal Analytics.

Best Practices for Structuring Your GA4 Account

Getting your GA4 account structure right from the start saves a lot of headaches later on. Here are a few simple but powerful best practices to follow.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

1. One Business, One Account

Resist the temptation to create separate analytics accounts for different parts of your business. Your company should almost always live under a single "Account." It simplifies user administration and provides a centralized place to govern your data policies.

2. Create Properties Purposefully

The main reason to create separate Properties within one Account is to isolate data that shouldn't be analyzed together. Common examples include:

• Production vs. Staging: Create a Property for your live website (brand.com) and a separate one for your development environment (dev.brand.com) to keep test data from polluting your real user data.
• Different Brands: If your company owns legally distinct brands with entirely separate audiences and websites, each brand should get its own Property.
• Sub-Domain Strategy: If you have a separate blog (blog.brand.com) and your main site (www.brand.com) and the user journey between them isn't meant to be analyzed as a single journey, you might split them into different Properties. However, GA4's cross-domain capabilities often make this unnecessary, it's usually better to track them in one Property.

3. Use Clean Naming Conventions

When you're managing multiple properties and data streams, clear naming is a lifesaver. Adopt a consistent standard and stick to it.

Poor Example:

• Property Name: Analytics Setup
• Data Stream: my web stream

Good Example:

• Property Name: [BRAND] Production - Web/App
• Data Stream Name: [Web] mybrand.com - Production
• Data Stream Name: [iOS] Brand Mobile App - Production

Final Thoughts

Understanding the layers of a Google Analytics 4 account - Account, Property, and Data Stream - is fundamental to collecting clean data and generating meaningful reports. This new structure is more flexible and powerful than its predecessor, a necessary evolution for a world where the customer journey is scattered across websites and mobile apps. By setting up your account thoughtfully, you're building a solid foundation for data-driven decisions.

We know that even with a perfectly structured account, digging through GA4's interface to answer a simple question like "which campaigns drive the most user registrations?" can be a time-consuming process. At Graphed{:target="_blank" rel="noopener"}, we remove this complexity entirely. You can connect your GA4 account in seconds and then ask your data questions in plain English - no more hunting through menus. Instantly create live dashboards and reports to analyze your performance, all without needing to become a GA4 expert.