Setting up GA4: the 3 settings you can't fix after the first 30 minutes

Paste the GA4 code into your site and numbers start flowing within minutes. Most owners treat that as the finish line. But a tag that fires and an account that's actually configured are two different things. Three settings sit between them, and if you skip past them now, there's no "restore to how it was" button waiting for you in month three — because that button doesn't exist.

None of the three is hard. Each is a few clicks. But Google built them to be deliberately irreversible: data cut off by an active filter never comes back, and if you raise your retention window late, the months already purged don't return either. All three belong on day one — before you paste the tag, or right after.

Don't leave your account structure to chance

GA4's hierarchy is simple: account → property → data stream. Google's own guidance is direct: if the site belongs to a different business, give it its own account; if it's a different channel of the same business — say, a website plus a mobile app — add it as a separate stream inside the same property (source: Google Analytics Help).

The common mistake happens during setup itself: a developer spins up a second property to test the install, wires the tag to it, then points the live site at the original property — or the other way round. Real traffic lands in the wrong place for weeks before anyone notices.

The cost is that properties don't merge and data doesn't move between them — each one is its own sealed container. Whatever landed in the wrong property during those first weeks stays there permanently, and your earliest history is split in two for good.

Before pasting the tag anywhere, open Admin and confirm exactly one property is active for the site, that it has one Web data stream attached, and that the stream's measurement ID (the one starting with G-) matches what's actually on the page. Delete any leftover test property from setup so no session can land there by accident.

Raise your data retention window now, not later

For standard properties, GA4 gives you exactly two choices for user-level (event) data retention: 2 months or 14 months (source: Google Analytics Help). This setting doesn't touch your standard reports — traffic trend lines, channel breakdowns, those stay forever. What it does limit is the Explore section, specifically funnel analysis and cohort comparison

Almost nobody notices this in month one, because the main reports keep working fine. It surfaces three or four months in, when you try to compare this quarter to last, or trace which campaign first brought in your current customers — and that window has already closed.

Go to Admin → Data Settings → Data Retention and set it to 14 months. Per Google's own documentation, raising the period applies to data you've already collected — meaning you can still rescue what hasn't been purged yet, but only what hasn't. That makes this a first-30-minutes task, not a someday one. While you're there, check the "Reset on new activity" toggle: turned on, it resets an active user's retention clock every time they return, keeping their data around longer.

Filter out internal traffic from day one

The moment a site goes live, your own team, your agency, and your developer click through it — testing buttons, submitting the form, reloading pages a few times each. GA4 logs every one of those as a regular visitor, because nothing tells it otherwise.

Google's documentation is explicit on two points: data filters apply only from the moment they're created forward, never retroactively; and once a filter is active, whatever it excludes is gone for good — it's never processed and never shows up in GA4 or in a BigQuery export (source: Google Analytics Help). That cuts both ways: skip the filter, and your team's test clicks stay mixed permanently into your first weeks of data; set it up with the wrong IP range — say your office shares an ISP block with a building full of other tenants, one of whom is a real customer — and their visits vanish just as permanently.

The steps

1. Find the real IP address for your office and anyone working from home (a browser search for "what is my ip" is enough).
2. In Admin → Data Streams → your stream → Configure tag settings → Define internal traffic, create a rule matching that IP to the internal_traffic_param parameter, value "internal".
3. Go to Admin → Data Settings → Data Filters and find the "Internal Traffic" filter.
4. Before switching it on, check the rule with a regular, reversible report filter first — see which sessions actually get tagged internal. Only once you've confirmed the right IPs are caught, flip the data filter to

None of these three settings has an undo — by the time you notice the mistake, the data is already gone, and there's no version to roll back to.

The payoff: 30 minutes now, no headache in month four

All three take a handful of clicks, but the order matters: confirm the account structure first, raise retention second, filter internal traffic third. Filing them under "I'll get to it" after the tag is live is the single most common mistake here, because for these three settings, "later" almost always means "too late."

If you'd rather hand this off, or just want certainty that the property structure is right from day one, our GA4 integration service sets up your account with all three of these in place from the start.