What is the first thing to verify when ga4 subproperties and roll-up properties (ga4 360) affects revenue?

Check whether the event fired with the correct transaction ID, revenue value, currency, and item array. Those four fields explain most ecommerce reporting failures.

Should I compare GA4 only to the ecommerce platform total?

No. Use order data, checkout flow behavior, and event payload evidence together. Platform totals alone do not tell you whether the issue is loss, duplication, or attribution drift.

How do I keep this from breaking after the next release?

Build a checkout QA routine that runs after changes to cart, consent, payment, shipping, discounts, or order confirmation logic.

GA4 Subproperties and Roll-Up Properties (GA4 360) (2026)

What are subproperties and roll-up properties in GA4 360?

Subproperties are derived properties that receive a filtered subset of data from a parent GA4 360 property. They allow you to give specific teams or clients access to only the data relevant to them, without exposing the full property's data.

Roll-up properties are aggregated properties that combine data from multiple source GA4 properties (or subproperties) into a single reporting view, enabling cross-brand or cross-regional consolidated analysis.

Both features are exclusive to GA4 360 (paid enterprise tier) — they are not available on free GA4.

The problem they solve: A multi-brand holding company has 8 brands, each with its own GA4 property. The group CMO needs to see combined revenue and traffic across all brands. Individual brand managers should see only their brand's data. Without 360 features, this requires manual data blending in Looker Studio (fragile, slow) or BigQuery UNION queries (requires SQL skill from everyone). Roll-up properties provide this natively in GA4's interface.

Subproperties: how they work

A subproperty is created by applying one or more filters to a parent GA4 360 property, creating a new property that receives only the matching data.

Example:

Parent property: Global E-commerce — All Markets Subproperty: UK Market — Brand A (filter: country = United Kingdom AND brand = Brand A)

The subproperty receives only UK / Brand A events. The UK market analyst logs into the subproperty and sees only their data. They cannot access Germany, France, or Brand B data even if those are in the parent property.

What subproperties inherit from the parent:

All events collected in the parent (filtered by your conditions)
Custom dimensions registered in the parent
Key events configured in the parent

What subproperties don't inherit:

Admin configuration (must be reconfigured per subproperty)
Google Ads links (must be set up separately on the subproperty)
BigQuery links (separate link required)

Access control advantage

The primary value of subproperties over property-level data filters (available on free GA4) is access control:

Data filters hide data but anyone with property access can still see the unfiltered parent
Subproperties create a completely separate property — users granted access to the subproperty cannot see the parent's unfiltered data

Want to see whether purchase, revenue, or item-level tracking is drifting in your property?

Audit revenue tracking

For agencies with strict data isolation requirements (client A must never see client B's data), subproperties are the architecturally correct solution.

Roll-up properties: how they work

A roll-up property receives data from multiple source GA4 properties (or subproperties), combining them into a single cross-property view.

Example setup:

Source property 1: Brand A — UK
Source property 2: Brand B — UK
Source property 3: Brand C — UK
Roll-up property: UK Portfolio — All Brands

The roll-up property receives events from all three sources, enabling cross-brand analysis. A brand user property or event parameter allows filtering within the roll-up to see individual brand performance when needed.

Roll-up property limitations:

Read-only: you cannot configure tracking, events, or custom dimensions in the roll-up itself
Attribution: cross-property user stitching is limited — a user who visits Brand A and Brand B is typically counted as two users in the roll-up (unless User-ID is implemented consistently across all brands)
Data freshness: roll-up data lags slightly behind source property data
Not a replacement for source properties: source properties still collect and store data independently

When to use each feature

Scenario	Best solution
Agency: 15 clients in one account, clients need isolated access	Subproperties (or separate properties)
Multi-brand: 8 brands, group CMO needs consolidated reporting	Roll-up property
Regional: UK/DE/FR sites, each region has own analyst	Subproperties from one parent property
Data governance: compliance team needs full data; marketing team needs subset	Subproperties for marketing; full parent access for compliance
Small agency: 3 clients, no GA4 360 budget	Separate free GA4 properties (same functional isolation)

Setup requirements

Prerequisites:

GA4 360 subscription (both features unavailable on free GA4)
Admin access to the parent property (for subproperties)
Admin access to all source properties (for roll-up)

Creating a subproperty:

GA4 Admin → Property Settings → Create subproperty → define filter conditions → confirm

Creating a roll-up property:

GA4 Admin (at account level) → Create property → Roll-up property → select source properties → confirm

Both require processing time (24–48 hours before data begins populating the new property).