Skip to content

Guide 140 · Setup · GA4 + Tag Manager

GA4 account and property structure: how accounts, properties, and data streams fit together

Checked 11 November 2026 · Verification: hierarchy limits recomputed (100 × 2,000 = 200,000 properties; 2,000 × 50 = 100,000 streams per account) · Steps traced to Analytics Help, read 11 November 2026 · 6-minute read

GA4 is a hierarchy, and every setup mistake in this section is a hierarchy mistake: a stream in the wrong property, a second account where a second property belonged, a user added at the wrong level. The levels are organization, account, property, and data stream, and each level has a limit that decides how far the structure stretches. This guide sets the structure out once, with the numbers, so the rest of the section has something to stand on.

Expected signal

After reading this guide, you can say which level a setting lives at — account, property, or stream — before opening Admin, and the counts in the reference file match Google's limits page.

Download the reference: the GA4 structure reference (JSON) (1044 bytes, MD5 9b2c1d7f086cde565abd36a2e5f9ae82). The hierarchy limits from Google's hierarchy page, with both ceilings recomputed: 100 × 2,000 = 200,000 properties and 2,000 × 50 = 100,000 streams per account.

What you need

  • Nothing to click. This guide is the map, not a task. Read it before creating accounts, properties, or streams.
  • The four level names. Organization, account, property, data stream — in that order, top to bottom.
  • One decision: which business each account stands for. An account is the gateway to Analytics and the container for properties, so the account boundary is the business boundary.

The trace

  1. Start at the top: the organization. The organization is optional. It represents a company and lets you manage product users, permissions, and cross-product integrations across Google's products. You access organizations at marketingplatform.google.com. Most single-business setups never need one.
  2. Then the account. The account is the gateway to Analytics and provides the container for the properties. You can have one or more Analytics accounts, up to a maximum of 100. Each account can contain up to 2,000 properties, so one Google account's ceiling is 100 × 2,000 = 200,000 properties in total.
  3. Then the property. Properties are the containers for the reports based on the data collected from the apps and sites. You can create up to 2,000 properties in an account. A property is a website, a mobile application, or a device such as a kiosk — one property per thing being measured, not one per page.
  4. Then the data stream. A data stream is a flow of data from a customer touchpoint — an app or a website — to Analytics. Each GA4 property can have up to 50 data streams in any combination of web and app streams, including a limit of 30 app data streams. That puts the ceiling for one account at 2,000 properties × 50 streams = 100,000 streams, although no real account gets near it.
  5. Place the settings at the right level. Users can be assigned at the organization, account, and property levels, with permissions at each level. Access management, property creation, and data retention are property-level or account-level jobs; the Measurement ID, enhanced measurement, and tag settings are stream-level jobs. A setting looked for at the wrong level is not missing — it is one level up or down.
  6. Work the example. A business with 2 websites and 1 app needs 1 account, 1 property, and 3 data streams: 2 web and 1 app. That is 3 of the property's 50 stream slots used, leaving 50 − 3 = 47 free. A second business needs its own account, not a second property in the first business's account.

Dead ends

DEAD END — ONE PROPERTY PER PAGE. A property is the container for a whole website or app. A property per page splits one site's data across dozens of properties that can never be added back together.

DEAD END — ONE ACCOUNT PER WEBSITE OF THE SAME BUSINESS. An account is the business boundary. Two websites of the same business belong as two properties in one account, where one Administrator can manage both. Two accounts mean two access lists and two billing relationships for no gain.

DEAD END — TREATING A CHECKOUT DOMAIN AS A SECOND STREAM. A data stream is a flow from a touchpoint — a website or an app. A checkout domain is not a second touchpoint; it is the same website on a second domain, and it belongs in the same stream with cross-domain measurement.

End state

The hierarchy is clear: an optional organization at the top, then an account for each business, then properties for each website or app, then data streams for each touchpoint. The limits are 100 accounts, 2,000 properties per account, and 50 streams per property with at most 30 of them app streams.

Sources

Checked 11 November 2026. The levels and limits above are the ones in Google's hierarchy page, read 11 November 2026, and the setup page, opened the same day. No step in this guide was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone. The reference file was checked in Python: its figures were recomputed from the documentation values and match the numbers on this page. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.