GA4 for multiple websites: how to see them in one view

If you run three websites, you probably have three Google Analytics 4 properties. Google Analytics shows one property's reports at a time, so the question "which site's traffic moved this week?" means opening each one, setting the same date range, and remembering the numbers from the last tab.

There are five ways around that, from free and fiddly to paid and built in. None is right for everyone. Here is how GA4 is organized, what each option does, and where each one falls short.

How GA4 splits your data

GA4 has three levels. An account holds properties. A property is where reports, key events, and user permissions live. A property collects data through data streams, and Google's help on data streams says a property can have up to 50 of them, any mix of web and app, with at most 30 app streams.

Two things follow from that. Reports never cross properties: every chart, exploration, and comparison is inside one. And the Analytics Data API quotas are per property too, so a script that reads several sites makes one set of requests per site.

Option 1: switch between properties

The property picker at the top of Google Analytics is free and needs no setup. For two sites you check now and then, it is enough.

It stops working when you want a comparison rather than a look. You read each site in isolation, so a 20% drop on one site and a normal week on another feel the same until you write the numbers down. Most people who run several sites start here and slowly stop checking the smaller ones.

Option 2: one property for every site

You can send several websites into one property, either as separate web streams or with the same tag on each site. Every report then covers all of them, and you can split by site with the Hostname dimension, which the Data API schema describes as the subdomain and domain of the page.

The cost shows up later. Totals mix products that have nothing to do with each other, so every report needs a filter before it means anything. Key events are defined once for the property, so a signup on one product and a signup on another share a definition. People you add see every site, since permissions are set per property. And splitting the sites apart later does not split their history.

One property does make sense for one product spread over several domains, like a marketing site and an app on another domain. That is what cross-domain measurement is for: it lets GA4 count a person moving between those domains as one user. For separate products, keep separate properties.

Option 3: a roll-up property

GA4 does have a built-in way to combine properties: the roll-up property. It takes data from up to 200 source properties and reports on them together. The catch is in the first line of Google's help page: roll-up properties are available only to Google Analytics 360 accounts, and only 360 properties can be sources. Analytics 360 is the edition you sign a contract with Google for. A roll-up also collects data only from the day each source is added, not before.

If you already pay for 360, use it. If you run a few small products, it is not a realistic option.

Option 4: a Looker Studio report

Looker Studio is free and has a GA4 connector. Each data source points at one property, and a blend joins up to five data sources on a field they share, such as date. So a chart of daily users for five sites, one line each, is a blend of five GA4 sources joined on date.

This works well for a fixed report you look at the same way every week. The tradeoffs are upkeep and scale. Each blend is built by hand, a sixth site means another blend, and adding a site means editing every chart that should include it. If you want a deeper look at where Looker Studio fits, we wrote a comparison of LopeBase and Looker Studio.

Option 5: the Analytics Data API

If you write code, the Data API's report method returns the same numbers the reports show. A small script can loop over your property IDs, pull users and pageviews for the last 7 days and the 7 before, and write one row per site into a sheet. It is free within the quotas, which are 200,000 core tokens per property per day on a standard property.

You own it from then on: the service account, the credentials, the schedule, and the fixes when a field changes. For one person running several products, that is often the piece that never gets finished.

What to compare across sites

Whichever option you pick, compare the same few things for every site, each against the period before rather than as raw totals. Sites of different sizes only line up as changes.

• Users and pageviews, this week against last. The site that moved most is the one to open.
• Key events per site. A signup or purchase count tells you more than sessions do, as long as each property marks the right event as a key event.
• Channel mix. A site that suddenly gets most of its visitors from one source is fragile, and one that lost its organic search traffic needs a look in Search Console.
• Silence. A site reporting no pageviews at all usually means the tag broke in a deploy, not that nobody came.

If you also run Search Console for each site, the guide to Search Console across many domains covers the search side, and the weekly review routine puts traffic next to revenue and uptime.

Option 6: a tool that reads every property

This is where LopeBase fits, so read this part knowing we built it. The Google Analytics connector connects with one read-only Google sign-in, as a Viewer, and you pick one GA4 property per product. It never changes your GA4 setup.

On the Analytics page, each product gets a card: pageviews for the last 7 days against the days before, a daily chart, and weekly and monthly users. Products that use PostHog, Plausible, or Cloudflare Web Analytics sit on the same page, each with its own logo and numbers, never added together, since every tool counts differently. LopeBase also reads the key events you marked in GA4 by channel, landing page, and device, and flags a site under Needs attention when it has had no pageviews for 7 days.

It has limits worth knowing. It reads GA4 properties only, not old Universal Analytics. It does not read GA4 funnels or retention. And because GA4 reports a key event rate per channel rather than a head count, the converters it shows per channel are worked out from that rate, so they are close but not exact. The Google connection guide covers setup and the common errors.