How Many Google Analytics Accounts Can You Set Up

The quick answer: Google lets you create up to 100 Analytics accounts under a single Google login. Most people never get near that number, because one account can hold multiple properties, and one property can hold multiple data streams, so you rarely need a new account just to track a new site.

I see this question a lot from agencies and consultants who assume they need a fresh Google Analytics account for every client. You don't, and in most cases you shouldn't. The account, property, stream structure exists precisely so you don't have to.

How the structure breaks down

Google Analytics 4 (GA4) is built in three layers, and understanding them is the whole answer to this question:

• Account, the top-level container tied to your Google login. This is where you're capped at 100
• Property, sits inside an account. Each property is a separate collection of data, typically one per website or app
• Data stream, sits inside a property. Each stream is one specific source, a website, an iOS app, an Android app

So one account can quite comfortably hold a website, its app, and a related microsite as three separate properties, each with its own data streams, all under one account, one login, one billing relationship if you're on GA4 360. You only bump into the 100-account ceiling if you're deliberately creating a new, separate account for every single client or brand instead of using properties within one account.

Why agencies get this wrong

I've worked with agencies managing 40 or 50 client sites who created a brand new Google Analytics account for every single one, under the agency's own login. That's a slow route to the 100-account ceiling, and it also makes account management painful: separate user permission sets, separate settings, no shared view across clients. The better structure, in almost every case, is one property per client website, grouped sensibly across a smaller number of accounts, often by service line or by how the client wants their own users to access the data.

What forces you to create a new account

There's really one good reason to spin up a separate Analytics account rather than adding a property to an existing one: ownership and access control. If a client needs to own their own Analytics account outright, with the agency added as a user rather than the account holder, that has to be its own account under the client's Google login, not a property tucked inside yours. That's an access decision, not a technical limit.

Step by step: setting up a new account correctly

1. Go to analytics.google.com and sign in with the Google login that should own the account (yours, or the client's, depending on who needs control)
2. Click Admin, then "Create Account"
3. Name the account clearly, I use the client or brand name, not "Website 1", because it gets confusing fast once you're managing several
4. Inside that account, click "Create Property" for the specific website or app
5. Set the correct time zone and currency at property level, this cannot be bulk-changed later without contacting support in some cases
6. Add a data stream (web, iOS or Android) and grab the measurement ID to install on the site

One detail that catches people out: the time zone and currency settings live at the property level, not the account level, so if you're managing several properties inside one account for clients in different countries, you set those individually, they don't inherit from the parent account.

Limits that matter more than the account cap

In eighteen years of doing this, I have never once seen a business hit the 100-account limit through legitimate need. The limits that trip people up in practice are further down the structure:

• Each account can hold a capped number of properties (Google's documented standard limit is generous, but it exists, and standard GA4 accounts aren't designed to hold hundreds of properties either)
• Each property has a data retention setting, 2 months or 14 months for user-level data, and it defaults to the shorter one, which quietly cuts off older data in reports if nobody changes it
• Standard GA4 properties have event volume thresholds; high-traffic sites can start sampling data in reports once you're deep into the millions of monthly events

If you're building out analytics for a large organisation, the property and data retention limits will bite you long before the account cap does. Set the retention to 14 months the day you create the property. I've had clients lose access to a full year of comparison data because the default two-month setting was never touched.

The property limit nobody reads about

Most content about GA4 limits stops at the account cap because it's the round, memorable number. The property limit gets less attention and it's the one that matters for organisations with a lot of brands or a lot of sub-sites. Google's default is generous enough that a small or mid-size business will never notice it, but I've worked with a franchise group where each location wanted its own reporting view, and by the time we'd mapped out separate properties for forty-plus locations plus a head office rollup, we were deliberately structuring accounts around regions rather than dumping everything into one, purely to keep permissions manageable rather than because of a hard technical wall.

The workaround for large multi-location businesses isn't more accounts, it's usually a head office GA4 property with a roll-up view, alongside separate properties (or in some setups, filtered explorations within one property) for individual locations. Google Analytics 360, the paid enterprise tier, raises several of these ceilings further and adds roll-up properties specifically designed for this problem, which is worth knowing if you're the one advising a franchise or multi-brand client on structure.

A mistake I made early on

Years ago I set a client up with a separate Analytics account for every campaign microsite they launched, thinking it kept things tidy. Eighteen months in, they had eleven accounts, scattered logins granting access, and nobody internally could tell me which account held which site without opening each one. We consolidated down to two accounts split by business division, moved every property across, and reporting got faster to build and easier to hand to their board. Tidy doesn't mean "one account per thing." It means a structure a stranger could understand in five minutes.

What this means if you're a freelancer or small agency

My advice is boring but it's correct: use one Analytics account per client relationship, not per website. If a client has three sites, that's three properties in one account. If you pick up a new client next month, decide whether they need their own account (because they'll want direct ownership and control) or a property inside an account you already manage for them. You'll be nowhere near 100 accounts for a very long time doing it this way, and the whole setup stays easier to hand over if the relationship ends.

I've written separately about why the right visitors matter more than more visitors.

Checking what you've already got before creating anything new

Before you create account number six for a new client, check the Admin panel account list first. Open analytics.google.com, click Admin, and look at the account selector at the top of the page. It's easy to forget you already have a suitable account sitting there from a project two years ago that never got cleaned up. I do a quick audit of this list every few months, deleting or archiving accounts tied to sites that no longer exist, mostly because a cluttered account list is where mistakes happen, someone adds a new property to the wrong account, or grants the wrong client access to the wrong data.

I have written more around this on the site: How Many Google Analytics Accounts Can You Set Up? The Real Limits Explained, How to Find Out How Many Backlinks Your Website Has, Why Google Analytics Might Not Be Showing Your Website Data.

Related reading: what happens if you fail google analytics certification.

Related: the data analytics page.

Building a dashboard? Here's an overview of the Google Analytics API for developers. Can't locate it? Here's where to find your Google Analytics tracking ID in a minute.

Frequently asked questions

What happens if I hit the 100-account limit?

Google won't let you create a 101st account under the same login. At that point you'd need to either consolidate existing accounts (moving properties where possible), delete accounts you no longer use, or use a different Google login for additional accounts.

Can I move a property from one account to another?

Yes, GA4 supports moving a property between accounts you have full control over, through the Admin panel under property settings. Historical data moves with it, but user access permissions do not carry over automatically and need resetting on the new account.

Does the 100-account limit apply per Google Workspace organisation or per individual login?

It applies per individual Google account, the login you use to sign into Analytics. A Google Workspace organisation with several staff logins could collectively manage well beyond 100 accounts, each staff member just can't personally own more than 100 under their own login.

Is there a limit on how many people can access one Analytics account?

There isn't a hard published cap on user seats at account or property level the way there is for accounts themselves, but Google does recommend keeping access lists tidy and reviewing them regularly, particularly at property and data stream level where permissions can get messy fast on larger teams.