Setting up GA4 — the first week checklist

A GA4 property that has only been installed and never configured beyond that will collect data, but most of what makes it useful — conversion events, internal traffic exclusion, cross-linked Search Console data — has to be set up deliberately, and doing it in the first week rather than months later avoids losing that period of data permanently.

The GA4 setup checklist, in the order that actually matters

1. Confirm the tracking code — the Google tag — is firing correctly. Every GA4 property is built around a web data stream, and each data stream has its own Google tag (the tracking snippet, whether installed directly or through Google Tag Manager) that sends events to it. Open GA4’s Real-time report, visit the site from a separate browser or device, and confirm the visit appears within a minute or two. If it does not, nothing else on this list is worth doing until the underlying installation is fixed.

2. Exclude internal traffic. Without this, visits from the business’s own staff, and from anyone building or testing the site, are mixed into the same reports as genuine visitor traffic, quietly inflating every number. GA4’s Admin settings allow internal traffic to be defined by IP address or a custom parameter and excluded from standard reporting.

2a. Confirm enhanced measurement is switched on for the data stream. GA4 properties collect a set of events automatically through enhanced measurement — scrolling, outbound clicks, file downloads and site search among them — configured per data stream in Admin → Data streams. It is on by default for a new property, but it is worth confirming rather than assuming, since a data stream reconfigured or migrated from an older setup can end up with individual measurement options switched off.

3. Set data retention to the longest available period. Covered in more detail on GA4 basics for a non-analyst — this is an Admin setting, and the default is not always the maximum available, so it is worth checking explicitly rather than assuming.

4. Mark the events that actually matter as conversions. Form submissions and, where relevant, tracked phone-call clicks need to be explicitly marked as conversion events in Admin → Events before they show up in the reports built to highlight them — the mechanics are covered in full on conversion tracking and goals in GA4.

5. Link Search Console to the GA4 property. This is a one-time setup step in GA4’s Admin → Product links section, and it is what makes Search Console’s organic search query data visible inside certain GA4 reports rather than needing to check two separate tools for related questions.

6. Set up UTM parameters for any paid or email campaigns already running. If a campaign is live and sending traffic without UTM tags, that traffic is likely arriving under a generic “referral” or “direct” label rather than being attributed to the campaign that actually drove it — see UTM tags and campaign tracking explained.

7. Bookmark the handful of reports actually worth checking regularly, rather than relying on memory to find them each time — Acquisition Overview, Engagement → Pages and screens, and the conversion events report set up in step 4 cover most of what what to actually measure on a small business website identifies as worth tracking.

The setting most commonly left on the wrong default

Check the property’s timezone and currency settings before anything else is trusted. GA4 buckets every event into a calendar day based on the timezone configured for the property in Admin → Property settings, and this defaults to whatever was selected at creation rather than automatically detecting the business’s actual location. A property left on a US timezone default will report a day’s traffic split across the wrong 24-hour window for an Australian business, which quietly distorts every day-level comparison — including the month-on-month and same-period-last-year comparisons this cluster relies on throughout. This is a one-time setting, cheap to check and expensive to discover wrong a year later once a full year of data has accumulated under the incorrect boundary.

Deciding who gets access, and at what level, before the account has a history worth protecting

The first week, before a property has accumulated a year of data anyone would mind losing, is the easiest point to set access correctly — adding the business’s own Google account as Administrator, and any supplier or agency involved as Editor rather than Administrator. Doing this in week one avoids the far more awkward conversation of asking a supplier to hand back or downgrade access after a relationship has already ended, covered in full on who owns the analytics account. It is worth treating as part of the initial setup checklist rather than an afterthought raised only if a problem arises later.

Validating the whole chain with one real test, not just individual pieces

Confirming each step above works in isolation is not the same as confirming the whole chain works together. Before considering setup complete, submit one genuine test enquiry through the site’s actual form (or place a test call through a tracked number, if that is in use) and confirm it appears, correctly, as a marked conversion event in GA4 — not just as a raw event in DebugView, but showing up in the Conversions view under Engagement, attributed to a sensible source. This single end-to-end test catches a class of failure that checking each configuration screen individually does not: a form correctly submitting, a tracking event correctly firing, and a conversion correctly being marked, but the three not actually wired together because of a naming mismatch between the event that fires and the event that was marked as a conversion.

Why the first week’s data looks thinner than it will later

New properties often show noticeably sparse or incomplete-looking data in their first few days, beyond the ordinary week-to-week variation any site has. Some of this is the property still building up its baseline of returning-visitor recognition and channel classification; some of it is simply that a handful of days is too short a window to see a representative pattern in even a moderately trafficked site. This is expected and is not, on its own, evidence that the setup has failed — the checklist above, and specifically the one-test validation in the previous section, is the more reliable signal of whether configuration succeeded, rather than judging the setup by how full the first week’s dashboard looks.

A one-page summary

Step	Where	Why it can’t wait
Confirm tracking fires	Real-time report	Nothing else matters if this is broken
Exclude internal traffic	Admin → Data settings	Inflated numbers from day one, invisible later
Set retention to maximum	Admin → Data settings	Cannot be applied retroactively
Mark conversions	Admin → Events	Conversion reports are empty without this
Link Search Console	Admin → Product links	Needed for combined organic search reporting
Add UTM tags to live campaigns	Campaign URLs	Otherwise attributed as generic traffic

What to do next

Work through the checklist in order — several steps genuinely cannot be backfilled once data has already been collected without them. Once configured, reading a monthly report without being an analyst covers what to actually look at going forward. If this configuration is being handled as part of a new build, small business website design covers where analytics setup typically sits in that kind of project.