Google Analytics 4 Multi-Property Dashboard: What's Missing and How to Fix It

Google Analytics 4 is genuinely excellent at what it does. The event-based model, Explorations, predictive audiences — for a single property, it covers almost everything a data-driven marketer needs. The problem starts the moment you have more than one property to manage.

Agency owners, consultants, and in-house teams running multiple brands all hit the same wall: GA4 has no native cross-property view. You get one property at a time, one tab at a time, one mental context-switch at a time. At two or three properties it's annoying. At five or ten it becomes a genuine operational drag that eats hours every week.

What GA4 Actually Gives You for Multi-Property Management

Before criticizing the gaps, it's worth being precise about what GA4 does offer. The Admin panel lets you switch between properties using the property selector dropdown. If you manage multiple accounts, you can use the account switcher to move between them. The Reports Snapshot gives you a customizable overview of key metrics — but scoped to a single property only. There is no way to pin metrics from Property A and Property B side by side.

The GA4 Data API (v1beta) does allow programmatic access to report data across properties, and the Admin API allows listing all properties you have access to. This is the surface area that third-party tools and custom dashboards build on. But if you're not an engineer, that's not a real solution — it's a starting point for one.

The Four Biggest Gaps

1. No Unified Realtime View

The Realtime report — which surfaces activeUsersin the last 30 minutes along with event counts, top pages, and traffic sources — is one of the most-used reports during launches and campaigns. But it's entirely per-property. If you're monitoring a campaign across three client sites simultaneously, you need three separate browser tabs open to three separate Realtime reports.

2. No Cross-Property Reporting in Explorations

Explorations is GA4's most powerful surface — free-form, funnel, path, segment overlap, cohort analysis. All of it is scoped to a single property. Any cross-property comparison has to be done manually: export from Property A, export from Property B, reconcile in a spreadsheet.

3. Search Console Data Is Siloed

GA4's Search Console integration is genuinely useful — but the data only appears in the individual property's reports. Comparing organic search performance across five sites means opening Search Console for each one separately, or building a custom Looker Studio connector.

4. No Portfolio-Level KPI Tracking

When a client asks "how are all our sites performing this month?" GA4 gives you no clean answer. You can't create a shared dashboard that pulls sessions, engagementRate, and conversions from ten properties into a single view. Every workflow that tries to answer this question is a workaround.

Why Google Won't Solve This Natively

GA4's architecture is built around the property as the fundamental unit of data isolation. Cross-property querying would require Google to build and maintain a federated query layer across millions of property combinations — with the privacy and data residency implications of doing so.

More importantly, Google already sells the enterprise answer to this problem through Google Marketing Platform and BigQuery. Large enterprises with many properties export GA4 data to BigQuery and build their cross-property views there. That's a reasonable solution if you have a data engineering team. It's overkill for a five-person agency.

The Workarounds People Actually Use

Looker Studio with the GA4 Connector

The most common workaround. You can add multiple GA4 data sources to a single report and create blended views. The practical limitations: blended data sources are complex to configure correctly, realtime data is not available (you're always 24–48 hours behind), and building a polished report for ten properties takes significant time upfront and ongoing.

Google Sheets with the GA4 API

The GA4 Data API allows batch requests against multiple properties. Some teams pull data into a spreadsheet via Apps Script. This gives you flexibility but it's brittle — API quota limits, schema changes, and authentication refreshes all become maintenance burdens.

Purpose-Built Dashboard Tools

The cleanest option. Tools like Perch Analytics authenticate via Google OAuth, read your existing GA4 and Search Console access, and present all your properties in a unified dashboard — realtime users, sessions, engagement rate, Search Console data, and AI traffic — with zero configuration. Free for up to three properties.

Choosing the Right Approach

• 1–2 properties, occasional cross-property reports: Looker Studio with the GA4 connector is probably sufficient.
• 3–10 properties, daily operational visibility: A purpose-built dashboard tool. The time you save not maintaining Looker Studio reports pays for itself almost immediately.
• Enterprise scale with a data team: BigQuery export plus a BI tool gives you the most flexibility at the lowest per-property cost.
• Need realtime monitoring: Neither Looker Studio nor the standard GA4 API will serve you here. You need a tool that reads from the Realtime API endpoint directly.

GA4 is not going to gain a native multi-property dashboard anytime soon. For agencies and consultants who live below the enterprise threshold, the practical path is to stop fighting GA4's limitations and use a tool built for the job. If you're managing three or more GA4 properties, it's worth trying Perch Analytics to see what a unified view actually feels like.