The property settings nobody reviews are the ones that quietly decide what your reports mean.

Default GA4 settings can distort reporting long before anyone notices. We configure streams, retention, filters, and identity around how the business operates before events are added. You end up with a GA4 property built around how your business runs, not whatever Google ships as the default.

Plan GA4 configuration All Google Analytics & GA4 Consulting tasks

Some of the 500+ brands we've worked with

See all references

The settings most teams never touch, each one chosen for a reason. Nothing here is symbolic. Each step changes an actual setting, and we tell you which one before moving to the next.

How we hold ourselves to it

How many properties and streams you actually need — We figure out the right property and stream count for your setup, and how everything should roll up if you're running multiple sites, apps, or brands.
Retention and identity, matched to your reports — We configure how long GA4 keeps your data and how it stitches users across devices and sessions, matched to what your reports actually need.
Internal traffic and referral noise, filtered before it counts — We filter out your own team's traffic and stop payment processors or subdomains from showing up as referral sources.
Cross-domain sessions that survive the handoff — We set up web and app data streams and, where you sell or convert across multiple domains, make sure a session survives the handoff.

Map the account structure
We agree how properties, streams, and any sub-brands or markets should be organized before touching any settings. The stakeholder confirms how sub-brands or markets should roll up.
Account structure map
Configure the property
We set retention, identity, internal traffic exclusion, referral exclusion, and any unwanted-referral cleanup directly in GA4. The admin approves each setting before it goes live.
Configuration change log
Verify in a live environment
We check how real traffic is classified, looking for false referrals, internal visits in reports, and sessions that break during domain handoffs. The analyst confirms a flagged session is a real miss.
Verification notes
Hand over the settings
We document every choice we made and why, so a future admin doesn't undo it by accident. The property admin signs off on the documented reasoning.
Configuration runbook

The settings teams often overlook, configured with a clear purpose.

Automation drafts the property and stream map from your current accounts, applies retention and exclusion presets from the agreed map, and flags traffic still classifying as an unwanted referral. The approvals stay with your side: how sub-brands roll up, every setting before it goes live, and whether a flagged session is a real miss.

Documentation for settings that are usually invisible until they cause a problem.

Structure diagram
Account and property structure
How your properties and streams are organized, and why, so it makes sense to whoever inherits the account next.
Configuration record
Configuration record
Every setting we changed, including retention, identity, exclusions, and streams, with its value and the reasoning behind it.
QA notes
Verification notes
What we tested after configuring, and what real traffic looked like once the settings were live.

We call it done when: internal traffic and known referrals classify as expected on live traffic, cross-domain sessions survive the handoff, and every changed setting carries its reason.

Match your situation against the list below before committing to a full build.

A good fit when

You're launching a new site, app, or business unit, and GA4 still needs its foundational settings built.
Your property still uses unreviewed defaults for retention, internal traffic, or referrals, so nobody can explain what those settings mean for reports.
Several web and app properties need one account structure, but nobody has agreed how the sites, apps, or markets should roll up.
GA4 admin access and a technical contact are available, but the property structure and foundational settings are still undecided.

A Zeo crew assembling a GA4 property like furniture, connecting panels, streams, and settings dials

Better handled as other work when

The property is already configured correctly and you only need events and conversions defined. That belongs in GA4 Event & Conversion Tracking.
You are unsure whether the current setup is trustworthy at all. Start with GA4 Audit & Remediation Planning instead.

If one of these is closer to your situation, start here instead: All Google Analytics & GA4 Consulting tasks

We call it done when: the account structure is agreed, including how sub-brands or markets roll up, before a single setting is changed.

Zeo designs measurement systems that connect a business decision to governed collection and reporting you can check. The people shown here work on the part of that system this page covers.

Content we've produced on this topic

Articleby Didem HimmetliGA4: The Future of Digital Analytics Articleby Zafer YıldızHow to Setup Google Analytics 4 (GA4)? Videoby Zafer YıldızGA4 ile Web Sitesi Performans Ölçümü | Zafer Yıldız, Zeo

Google Analytics
where streams, retention, filters, and identity get set before events are touched
Google Tag Manager
carries the config tag that connects the site to the property just configured
Google Tag Assistant
the live-environment check that a wrong default doesn't announce itself

Bring the current setup, whether new or established. We will identify defaults that do not fit and correct them.

Plan GA4 configuration

Do you also set up our events and conversions?

Not in this task. Property configuration and event design are kept separate on purpose. Once your property is configured correctly, GA4 Event & Conversion Tracking covers naming events and key events.

What if we already launched with default settings?

That's normal, and fixable. We review what's live, tell you what's silently wrong, and reconfigure it without losing your existing history where that's possible.

Will changing these settings affect our historical data?

Some settings, like retention, only affect data going forward, so nothing already collected changes. Others, such as account structure, can't be changed later without starting a new property. We walk through which category each setting falls into before anything moves. Whatever we decide together goes into the configuration runbook, so the reasoning survives even if the person who approved it moves on.

What GA4 access does the setup require?

Admin access to GA4 and a technical contact who knows your domain structure, app setup, and whether you run multiple brands or markets.

By team

By industry

By tool

GA4 Implementation & Configuration

Four steps, each ending in a setting someone can point to.

Map the account structure

Configure the property

Verify in a live environment

Hand over the settings

Configuration records that explain both the setting and its purpose

Account and property structure

Configuration record

Verification notes