Google Analytics uses several layers that sound similar but serve
different purposes. Selecting the wrong layer can mix unrelated websites
or leave WordPress connected to an empty stream.
The simplest model is: an account contains properties, and a property
contains data streams.
Site owners often ask this as ‘where is my website in Google
Analytics?’, ‘what is that G-number?’, or ‘why does Analytics show no
visitors?’ The account, property, stream, and measurement ID are related
parts of one setup, but each has a different job.
Analytics account
The account is the highest organizational level. A business may use
one account for several websites, or separate accounts when ownership
and access need strong separation.
The account is not the website tracker itself. It primarily holds
properties, permissions, and account-level settings.
GA4 property
A GA4 property is the reporting container for a business asset or
closely related set of digital experiences. It contains reports, events,
conversions or key events, audiences, links to other Google products,
and data-retention settings.
For unrelated websites with different purposes, owners, or audiences,
separate properties are usually cleaner. This prevents reports and
configurations from being mixed accidentally.
Web data stream
A web data stream represents the source that sends website activity
into the property. It has a website URL, stream name, and measurement ID
typically beginning with G-.
A property can contain more than one stream, including web and app
streams, but adding multiple unrelated websites to one property can make
reporting harder to interpret.
Measurement ID
The measurement ID tells the Google tag where to send data. It is not
a password, but it must match the intended stream. Copying an ID from
another website sends data to the wrong property.
When using a WordPress plugin to install analytics, confirm the
selected account, property, and data stream before enabling code
installation.
Avoid duplicate tracking
Analytics may already be installed through a theme, tag-management
plugin, Google Tag Manager, hosting integration, or another analytics
plugin. Enabling a second installer can cause duplicate page views and
unreliable engagement data.
Before turning on an “install analytics code” option, determine which
component currently owns the Google tag. Choose one primary installation
method and document it.
A safe setup sequence
- Sign into the intended Google account.
- Select or create the appropriate Analytics account.
- Create a separate GA4 property for the website when needed.
- Configure the correct reporting time zone and currency.
- Create a web data stream using the canonical HTTPS URL.
- Record the property name, stream name, and measurement ID
privately. - Connect WordPress using one installation method.
- Visit the public site while logged out.
- Check Realtime reporting and tag diagnostics.
- Exclude administrator traffic when the chosen tool supports it
appropriately.
Search Console and
Analytics are different
Search Console reports how a site appears and performs in Google
Search. Analytics reports activity after visitors reach the website.
They complement each other but are not interchangeable.
A WordPress SEO plugin may request access to both. Select the correct
Search Console property and the correct GA4 property/data stream
independently.
What data should appear
first?
Realtime activity can often appear soon after a successful
installation. Standard reports take longer to process. A new site with
little traffic may show sparse data even when tracking is correctly
installed.
Test deliberately: open a private window, visit several pages, and
observe Realtime. If nothing appears, check consent behavior, browser
blocking, tag diagnostics, the selected measurement ID, and whether the
site is serving cached markup without the tag.
Protect unrelated properties
When several websites share a Google account, verify names carefully
before saving. Do not rename, delete, or change the data stream of
another website merely because it appears in a selector.
Clear naming helps: use the domain or recognizable business/site name
for both the property and stream. Maintain a private inventory of which
measurement ID belongs to each website.
The hierarchy becomes manageable once each level has one clear job:
account for organization, property for reporting, stream for data
collection, and measurement ID for routing.
Establish
a measurement plan before collecting everything
Page views alone do not define success. Identify a small set of
meaningful actions, such as completing a contact form, downloading a
useful resource, following a qualified outbound link, or reaching a key
article section. Name and document events consistently before treating
them as business metrics.
Collect only what is necessary. Analytics configuration should align
with the site’s privacy disclosures, consent requirements, and
data-retention choices.
Frequently asked questions
Can one GA4
property track multiple websites?
It can, but that does not make it the clearest structure. Unrelated
sites are generally easier to administer and analyze when separated into
appropriately named properties and streams.
Why are my own visits
missing?
Logged-in-user exclusions, consent settings, browser protections,
filters, or extensions may block the test. Use a private window and
Realtime reporting, then verify the measurement ID.
Can GA4 replace Search
Console?
No. GA4 focuses on activity on the site. Search Console focuses on
Google Search visibility, queries, crawling, and indexing. Use them
together.
Related guides
- Rank Math Search Console and Analytics Setup
- How to Verify a Domain in Google Search Console