One of the main structural changes in Google Analytics 4 compared with Universal Analytics is the way data is collected.
In GA4, data is sent to a property through data streams. A data stream is simply the source that sends data into the property, whether that source is a website or a mobile app. This is one of the foundations of GA4, since the same property can bring together data from web and app environments under a single reporting setup.
Contents
What is a data stream in Google Analytics 4?
A data stream is a flow of data from a website or app into a Google Analytics 4 property.
GA4 supports three types of data streams: Web, iOS, and Android. This means the same property can receive data from a website, an iOS app, an Android app, or a combination of them.
In practice, a data stream is the connection between a digital touchpoint and the GA4 property where the data is collected and processed.
Types of data streams in GA4
As mentioned above, there are three types of data streams in Google Analytics 4: web, iOS, and Android. Each one is designed for a different environment, but all of them serve the same purpose: sending data into the GA4 property so it can be processed and reported later.
Web data stream
A web data stream is used to collect data from a website.
This is the stream you create when you want to measure activity on a site through the Google Tag or Google Tag Manager. Once the stream has been created, GA4 generates a Measurement ID, which is the identifier used in the tagging setup.
The web stream is also where some of the most important measurement settings are configured, such as enhanced measurement and cross-domain measurement.
In practice, this is the stream most businesses will work with first. It is the stream that collects page views, sessions, traffic source data, and the rest of the website interactions that later appear in GA4 reports. If enhanced measurement is enabled, the web stream can also collect events such as scrolls, outbound clicks, site search, file downloads, and video engagement without requiring extra tagging.
That makes the web data stream much more than just a technical connection between the website and GA4. It is also the place where some of the core data collection behaviour of the property is defined, which is why it plays such an important role in the overall measurement setup.
iOS data stream
An iOS data stream is used to collect data from an iOS app.
These streams are normally implemented through the Google Analytics for Firebase SDK, which allows app activity to be sent into GA4. This means the property can receive app data in the same overall setup used for other platforms, which is especially useful for businesses that want to analyze behaviour across both web and app environments.
The iOS stream is designed for app interactions rather than website visits, so the logic behind the measurement is different from a web stream. Instead of page-based navigation, app measurement is more focused on screens, in-app events, user engagement, and lifecycle activity. GA4 also automatically collects some app events through the Firebase SDK, which gives the implementation a useful starting point even before adding custom events.
For businesses with an iPhone or iPad app, this stream is what makes it possible to bring that usage data into GA4 and analyze it alongside other digital touchpoints. In that sense, the iOS stream helps extend the property beyond the website and gives a broader view of how users interact with the brand.
Android data stream
An Android data stream is used to collect data from an Android app.
Like the iOS stream, it is generally implemented through the Google Analytics for Firebase SDK. Once configured, it sends app data into the GA4 property so user activity in the Android app can be measured and analyzed.
The Android stream follows the same general logic as the iOS one. It is built for app measurement, not website measurement, so it focuses on app events, engagement, app lifecycle activity, and user behaviour inside the application. It also supports automatic event collection through the SDK, which gives the implementation a base level of measurement from the start.
This type of stream is especially useful when a business has an Android app that forms part of the same user journey as the website or iOS app.
What data streams are used for
Data streams are used to define where GA4 data is coming from.
Instead of creating separate properties for every environment, GA4 makes it possible to send data from different platforms into the same property through different streams. This allows reporting to be more unified across web and app environments and makes it easier to analyze the user journey more broadly.
This is one of the reasons why GA4 is structured differently from Universal Analytics. The property is no longer tied to just one website view in the old sense. Instead, it can receive data from multiple streams.
How data streams work in GA4
When you create a GA4 property, one of the first steps is to create a data stream.
From there, the stream generates the configuration needed to start sending data into the property. In the case of web streams, this includes the Measurement ID and access to settings such as enhanced measurement. In the case of app streams, the setup is usually tied to the app implementation through Firebase.
How many data streams a GA4 property can have
A GA4 property can have up to 50 data streams in total, with a limit of 30 app streams.
Even so, Google’s recommendation is usually much simpler: one web data stream per property, one iOS data stream per property, and one Android data stream per property. That setup is often the cleanest and easiest to manage.
Things to keep in mind when working with data streams
Although GA4 allows multiple streams inside the same property, that does not mean every site or app should automatically be grouped together.
The decision should depend on whether those touchpoints belong to the same business, the same measurement strategy, and the same reporting needs. If very different websites or apps are grouped into one property without a clear reason, reporting can become harder to manage.
It is also worth remembering that some configurations are handled at stream level rather than at property level. For example, cross-domain measurement is configured within the web data stream settings, and enhanced measurement is also managed there.
In short, data streams are one of the core elements of Google Analytics 4. They define where the data comes from and make it possible for a single GA4 property to receive information from websites and apps at the same time. Understanding how they work is important because they shape the way data is collected from the very beginning and affect how the overall measurement setup is structured.
