Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Data Stream

A source of data flowing into a GA4 property: one web stream for a site or an app stream for each iOS or Android app, each with its own settings.
Analyticsplatform featureUpdated

Definition

A data stream is a flow of data from a website or app into a GA4 property. Google Analytics describes everything it collects as events, and every event reaches the property through a stream. There are two kinds:

  • A web stream for a website, collected by the Google tag. It is identified by a measurement ID beginning with a letter G and a hyphen, which the tag uses to send data to the right place.
  • An app stream for an iOS or Android app, collected through the Firebase SDK that the app developers install.

The hierarchy runs account, property, stream. The property holds the reports, the key events, custom definitions, data retention and data filters; the stream holds the identifier and the collection settings for one source.

In practice: web and app streams and the settings on each

The GA4 setup checklist creates the web stream early, straight after the property, because the tag cannot be installed without its measurement ID. Its rule of thumb is one web stream per site: a second stream is for a genuinely separate site or an app platform, not for a subdomain, and a staging environment is better given its own property so that test events never reach production data.

The stream is also where several important settings are found:

  • Enhanced measurement, which records page views and a set of common interactions automatically, each arriving as an event with its Event Parameter values.
  • Cross-domain measurement, a list of the business's own domains between which the visitor's identifier is passed in the link, so a journey stays one session.
  • Unwanted referrals, a list of referrers, such as a payment provider, that should not start a new source.
  • Internal traffic rules, which tag visits from the business's own network so that a data filter on the property can exclude them.

The guide to common GA4 mistakes traces two familiar problems to these settings: self-referrals from a checkout or gateway, fixed by cross-domain measurement and unwanted referrals, and internal traffic left in reports because the stream rule was created but the property's filter was never switched from testing to active.

Property, stream and tag: how the pieces fit

A business with both a website and an app can hold a web stream and app streams in the same property, so journeys that cross from one to the other can be reported together. The guide to web-to-app journeys relies on that arrangement, with a stable user identifier set at sign-in on both. For a new business, the order matters: the marketing setup guide for a new business creates the property, then the stream, then the settings and consent behaviour, and only then verifies the data. When a site changes hands, the stream's identifier and the person who controls the tag are recorded in the GA4 property handover checklist, because data that stops after an access change has often lost a stream or tag owned by someone who left.

Illustrative example — not a real result

A ferry ticket seller recovers its campaign sources

Halcyrn Ferry Tickets sells crossings on its main site and takes bookings on a separate booking-engine domain, with payment handled by a third-party provider. In its GA4 reports the booking domain was the second-largest source of purchases, with 1,140 of 3,900 purchases in a quarter credited to it as a referral, and the payment provider added another 420. The team opened the web data stream, listed both its own domains in the cross-domain measurement setting and added the payment provider to unwanted referrals. In the next full month, self-referrals fell to 35 purchases out of 1,280, and paid search and email recovered the purchases their visitors had started.

GA4 is the platform whose properties the streams feed. Cross-Domain Tracking is configured on the web stream and is the setting most often missing when a business runs more than one domain. A Key Event is defined at the property level from events that arrive through any of its streams, so a purchase counted in the app and on the web can be one key event. Each Event Parameter travels with its event through the stream, and a parameter only becomes reportable once it is registered as a custom definition on the property.

Common confusions

  • A stream per subdomain. Subdomains of one site belong in one web stream; separate streams split the same visitors into two populations.
  • Staging as a second stream. Test events then land in the production property; a separate property is safer.
  • The stream is the property. Reports, key events and retention belong to the property; collection settings belong to the stream.
  • Settings apply to old data. Cross-domain, referral and internal traffic changes take effect from the moment they are saved.
  • Deleting a stream to start again. The stream's identifier is wired into the tag; a new stream means a new identifier and a re-tagged site.

More terms to look up

Where this term is used

Sources

  1. [GA4] About events — Google Analytics Help

Related