Analytics and Tracking

Property

Also called GA4 property

The GA4 container that holds all measurement data for one business, fed by its website and app data streams.

Quick facts: Property

Category
Analytics and Tracking
Also called
GA4 property
Level
Beginner
Affects
Reporting scope, access permissions, cross-domain measurement
Where to see it
GA4 admin (property settings, data streams, property ID)
In this article4
  1. How a property works
  2. Why the property matters
  3. Where properties go wrong
  4. How to act on it

How a property works

Google Analytics is organised in layers. An account sits at the top, usually representing an organisation. Inside it are properties, and a property is the container that actually holds data. Beneath the property sit data streams — one for a website, others for an iOS or Android app — which feed events into the same pool so that a customer using both is measured together.

The property is where the decisions that shape your reporting live: the reporting time zone, the currency, the data retention period, the reporting identity, internal traffic rules, cross-domain settings and the links to Google Ads, Search Console and BigQuery. Each property has its own numeric identifier, and the tag on your site names that identifier, which is what decides where the data lands.

Two of those settings are worth flagging. Changing the time zone or the currency affects data from that point onward only; it does not restate history, so the change leaves a visible seam in year-on-year comparisons.

Why the property matters

Everything is scoped to it. Audiences, conversions, custom dimensions, comparisons and reports all belong to a single property and cannot see across to another. Data cannot be merged between properties later either, so the structure you choose at the beginning quietly determines which questions your business will ever be able to answer.

It is also the boundary for access. Granting someone permission at property level shows them all of that data, and granting at account level shows them every property beneath it. For anyone handing access to an agency or a contractor, that distinction is the whole of your data governance.

Where properties go wrong

The most common structural error is splitting one business across several properties — a separate one per domain, per language or per country — which makes a single customer look like several visitors and removes any chance of seeing the whole journey. Regional views are better handled inside one property with comparisons and filters.

The opposite error is pouring genuinely unrelated businesses into one property, where their events and conversions contaminate each other’s reports and no filter fully separates them.

Smaller but persistent faults include an unset or wrong time zone, so daily figures never line up with the ad platforms, and a forgotten test property still collecting alongside the real one.

How to act on it

Decide the structure before the first tag goes live: one property per business whose performance you judge as a whole, with data streams beneath it for each site and app. Set the time zone, currency and retention on day one, because two of those three cannot be applied retroactively.

Then keep access tidy. Grant at property level rather than account level, review who holds it when people leave, and keep a written note of which property identifier belongs to which site. Getting this right at the start is the cheapest part of any GA4 setup; restructuring afterwards means starting the history again.

Do and do not

Do

  • Set time zone, currency and retention before launch
  • Keep one business in one property with several streams
  • Grant access at property level, not account level

Do not

  • Split one customer journey across separate properties
  • Mix unrelated businesses into a single property
  • Expect a time zone change to restate past data

Questions people ask about this

Should each website have its own GA4 property?

Only if you judge them as separate businesses. If several domains serve the same customers and the same goals, keep them in one property with a data stream each and cross-domain measurement configured, so a single journey is not split into strangers. Genuinely unrelated businesses do belong in separate properties.

Can I merge two GA4 properties?

No. Historical data cannot be combined between properties, and there is no migration path that joins them. The nearest option is to send future data to one property and export the other's raw data to a warehouse where the two sets can be analysed side by side. Choose the structure early for this reason.

What is the difference between a property and a data stream?

The property is the container that holds the data and carries the settings, links and definitions. A data stream is a source feeding events into it, such as a website or a mobile app. One property can have several streams, and the events from all of them are reported together within that property.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.