Web Analytics · Google Analytics & GA4

GA4 Implementation & Configuration

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.

A GA4 property built around how your business runs, not whatever Google ships as the default.

Plan GA4 configurationAll Google Analytics & GA4 Consulting tasks
A Zeo crew assembling a GA4 property like furniture with panels, streams, and settings dials

Some of the 500+ brands we've worked with

See all references
  • Shell
  • Red Bull
  • Mynet
  • Odeabank
  • Axa Hayat Emeklilik
  • Vispera

How we run it

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

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.

  1. Map the account structure

    We agree how properties, streams, and any sub-brands or markets should be organized before touching any settings.

    Account structure map

    AI assist
    Drafts a property and stream map from your current accounts.
    Human gate
    Stakeholder confirms how sub-brands or markets should roll up.
    Owners
    GA4 Specialist, Marketing Stakeholder
    Illustrated figure sketching plans at a drafting table

  2. Configure the property

    We set retention, identity, internal traffic exclusion, referral exclusion, and any unwanted-referral cleanup directly in GA4.

    Configuration change log

    AI assist
    Applies retention and exclusion presets from the agreed map.
    Human gate
    Admin approves each setting before it goes live.
    Owners
    GA4 Specialist, Property Admin
    Illustrated figure stacking patterned building blocks

  3. 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.

    Verification notes

    AI assist
    Flags traffic that still classifies as an unwanted referral.
    Human gate
    Analyst confirms a flagged session is a real miss.
    Owners
    GA4 Specialist, Technical Contact
    Illustrated figure examining a search result row through a large magnifier

  4. Hand over the settings

    We document every choice we made and why, so a future admin doesn't undo it by accident.

    Configuration runbook

    AI assist
    Drafts the configuration runbook from the change log.
    Human gate
    Property admin signs off on the documented reasoning.
    Owners
    GA4 Specialist, Property Admin
    One illustrated figure passing a relay baton to another

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.

What you get

Configuration records that explain both the setting and its purpose

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.

    Accepted when

    Someone inheriting the account can tell why each property and stream exists.

    Cadence: Redrawn when the estate changes

  • Configuration record

    Configuration record

    Every setting we changed, including retention, identity, exclusions, and streams, with its value and the reasoning behind it.

    Accepted when

    Every changed setting lists its value and the reason it was set that way.

    Cadence: Appended at every setting change

  • QA notes

    Verification notes

    What we tested after configuring, and what real traffic looked like once the settings were live.

    Accepted when

    The checks were run on live traffic after the settings went in, not before.

    Cadence: Captured after go-live traffic

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.

Fit and readiness

The settings behind the property have never had a proper review.

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.

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.

People who build your measurement system

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 AnalyticsArticleby Zafer YıldızHow to Setup Google Analytics 4 (GA4)? Videoby Zafer YıldızGA4 ile Web Sitesi Performans Ölçümü | Zafer Yıldız, Zeo

Tools we use

Tools behind this work

  • 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

Next step

Build your GA4 property right before you build on top of it

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

Before we start

Questions teams ask before booking

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.