Skip to content

Guide 125 · Setup · GA4 + Tag Manager

Add a web data stream: the stream that turns your website into a source of events

Checked 11 November 2026 · Verification: data-stream limits recomputed (50 total streams − 30 app streams = 20 web slots left) · Steps traced to Analytics Help, read 11 November 2026 · 5-minute read

A property collects nothing until it has a data stream. The stream is the connection between the website and the property: the website sends events into the stream, and the stream carries them into the reports. For a website the stream type is Web, and creating it takes two fields — the website URL and a stream name — plus one decision, whether enhanced measurement stays on. This guide adds the stream the way Google's setup page describes it.

Expected signal

After step 3, the Web stream details page shows the stream name, the website URL, and a Measurement ID starting with G-. That ID is what every install method needs next.

Download the reference: the web data stream reference (JSON) (636 bytes, MD5 3d01618c2ed3629959ba2442e53fa0d4). The stream limits from Google's hierarchy page, with the remaining web slots recomputed: 50 total streams − 30 app streams = 20.

What you need

  • A GA4 property that already exists. Create the account and property first; the stream is added inside the property.
  • The website URL exactly as visitors reach it, including https. The stream takes the URL you enter, so a wrong scheme or a missing subdomain follows the stream into the reports.
  • A stream name. Use the website name. A property can hold many streams, and the name is how you tell them apart later.
  • The Editor role at the property level. Adding a stream changes the property, so a Viewer cannot do it.

The trace

  1. Open Admin and pick the right property. In Admin, check the Account column has the right account selected, then check the Property column has the right property. A stream added to the wrong property sends the site's data to the wrong reports.
  2. Add the stream. In the Property column, click Data Streams, then Add stream. Click Web. The other two choices, iOS app and Android app, are for apps, not websites.
  3. Enter the URL and the name. Enter the website URL and a stream name, then create the stream. Enhanced measurement is on by default when the stream is created; the toggles for each event live in the stream's settings and get their own guides in this section.
  4. Note the Measurement ID. The Web stream details page shows the Measurement ID, starting with G-. Copy it from this page. It is the ID the Google tag, Tag Manager, and the WordPress and Shopify installs all ask for.
  5. Check the stream budget. Each GA4 property can have up to 50 data streams in any combination of web and app streams, with a limit of 30 app data streams. If a property ever used all 30 app slots, 50 − 30 = 20 stream slots would remain, and those could only be web streams. One website needs one web stream; the limit only bites on properties that track many apps and sites together.

Dead ends

DEAD END — ADDING A SECOND WEB STREAM FOR THE SAME WEBSITE. One website needs one web stream. A second stream for the same site splits the site's events across two streams and two Measurement IDs, and the reports never add back together cleanly.

DEAD END — ENTERING THE URL WITHOUT HTTPS. The stream records the URL you type. If the live site is https and the stream says http, the stream details disagree with the site from the first day. Type the URL exactly as the site is reached.

DEAD END — CREATING THE STREAM IN THE WRONG PROPERTY. The property selector at the top of Admin is easy to miss. Check the account and property columns before clicking Add stream — moving a stream to another property afterwards is not a step Google documents.

End state

One web data stream in the right property, named for the website, with its URL recorded and its Measurement ID visible on the stream details page. Enhanced measurement is on. The property still measures nothing until a tag is installed on the site, which is the next guide in this section.

Sources

Checked 11 November 2026. The click paths above are the ones in Google's setup page, opened 11 November 2026, and the hierarchy page, read 11 November 2026. No step in this guide was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone. The reference file was checked in Python: its figures were recomputed from the documentation values and match the numbers on this page. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.