Study first
Review the ideas behind the questions
Check the admin structure before changing a GA4 setup. Focus on where data enters the property, who can access it, and which built-in collection settings affect reports.
Keep the hierarchy clear
GA4 account structure starts with accounts, properties, and data streams. Each level has a different job.
- A GA4 account contains properties, and a property is the container for reports based on collected data.
- A data stream is the flow of data from a website or app into Analytics.
- When a data stream is created, Analytics generates code that must be added before new data is collected.
In Practice
Group related touchpoints deliberately
A website and app for one product can belong in one property while still using separate streams for each touchpoint.
Do not expect old data before tagging
Creating a stream does not create past website activity. Collection starts when the generated code is added.
Common mistakes
Creating a separate account for every small touchpoint.
Use properties and data streams to organize related web and app touchpoints before splitting accounts.
Q&A
What is a GA4 data stream?
It is the flow of data from a website or app to Analytics.
When does a new stream start collecting data?
It collects from the time the generated code is added to the site or app.
Grant access at the right level
Access decisions should match the work someone needs to do and the properties they should see.
- Account-level access applies to all properties in that account.
- Property-level access applies only to that property with the permissions provided.
- Adding or changing users requires the Administrator role at the relevant account or property level.
In Practice
Use the narrow level that fits
If someone needs one property, property access is cleaner than account access.
Check inherited roles
A lower direct role on a property may not reduce a higher role inherited from the account.
Common mistakes
Giving account access when a teammate needs one property.
Grant property-level access when the user should not see every property in the account.
Q&A
Who can add a user in GA4?
A user with the Administrator role at the relevant account or property level can add or modify users.
What does effective permission mean?
It is the role and data restriction result after inherited and direct permissions are combined.
Check built-in setup signals
Some admin checks are about what GA4 collects automatically and where setup changes are recorded.
- Enhanced measurement page views are collected automatically and cannot be turned off.
- Scroll events trigger when 90% vertical depth becomes visible for the first time on a page.
- Change history records account or property changes for the last 2 years.
In Practice
Look at collection settings before adding custom work
For page views and scrolls, check enhanced measurement behavior before asking for extra implementation.
Use change history for setup surprises
When a link, stream, or setting changes unexpectedly, change history can show the item, action, time, and user.
Common mistakes
Assuming every scroll report needs a custom event.
Check enhanced measurement first because GA4 can collect scroll events using its documented 90% depth trigger.
Q&A
Where can an Editor investigate a property setting change?
Use account or property Change history to see details such as the item, action, time, and changed-by value.
What should be checked for scroll tracking before adding custom code?
Check enhanced measurement because it can collect scroll events when 90% vertical depth becomes visible.