When to run this checklist
Run it when a property is created, obviously, but creation is the least common reason to open it. The more frequent cases are inheriting a property someone else configured, replatforming a site so that the tag has to be installed afresh on new templates, adding a domain or a booking engine that visitors cross into, and changing the consent setup after a legal review. Each of those breaks one group of lines while leaving the rest intact, which is why the list is grouped rather than flat. Run it also before linking an advertising account, because the link imports whatever key events exist, mistakes included, and before any report is built that the business will make decisions on. An annual pass on a stable property catches the slow failures: a retention setting that was never changed, a filter still in testing state, an unwanted referral that appeared when the payment provider changed its domain. For a new business opening its first property, the tutorial on setting up the marketing basics for a new business places this checklist in sequence with account ownership, consent, listings and naming conventions.
Before you start
- Administrator access to the Analytics account that will own the property, held by the business rather than by an agency, and editor access to the tag container. The GTMTag management system. route to installing the tag, set out in the GA4-via-GTM guide, is the one most setups use.
- The tracking plan, even a one-page version, listing the actions that matter, the event name for each and the parameters it carries. The tracking plan guide shows what one looks like; without it the events group cannot be ticked honestly.
- A list of every domain and subdomain a visitor can cross, including checkout, booking and login providers hosted elsewhere, because the cross-domain and unwanted referral lines depend on it.
- The consent requirements for the markets the site serves, agreed with whoever owns privacy, since consent modeA Google tag feature that adjusts what tags collect according to the visitor's consent choices. behaviour is a setting, not a guess.
- The advertising and Search Console accounts that will be linked, with the right to link them from both sides.
- A test device and the DebugView report for the verification group, plus the naming convention for campaign parameters so that UTMURL tags identifying traffic source. values arrive in a shape reports can use.
The checklist
Groups build on one another: streams need a property, settings need a stream, events need the tag that the stream provides, and verification needs all of it. Ticking the verification lines early, because a page view appeared in real time, is the commonest way to leave a half-configured property looking finished. Where a line names a decision rather than a task, such as data retention or Google signals, tick it only once the decision is recorded somewhere other than your memory.
Property
Streams
Settings
Events
Definitions
Links
Verification
If an item fails
Most failed lines on this list are cheap to fix on the day and expensive to fix later, because the data collected in the meantime cannot be corrected. A property created in the wrong account, a parameter sent for months before it was registered as a dimension, a filter that excluded real visitors: in each case the history is gone. So the order of repair is by data loss, not by group. Fix anything that stops data arriving or throws it away first, then anything that mislabels it, then the links and the conveniences. Where a line fails because the setup was inherited and the reason for a decision is unknown, do not undo it on the spot; note it, find the person, and change it once the consequence is understood.
| Group that failed | Where the fix is explained |
|---|---|
| Property, streams, settings | GA4 setup, step by step, installing GA4 through GTM and consent mode |
| Events | Events and parameters, the tracking plan guide and e-commerce tracking |
| Definitions | Key events and conversions and audiences |
| Links | Google Ads integration and BigQuery export basics |
| Verification | Debugging and preview in GTM and the tracking verification checklist |
A regional estate agency's inherited property
A regional estate agency takes its marketing in-house and runs the list on the property its former agency
built. The property group fails at the first line: the property sits in the agency's account, and the only
administrator left the agency 8 months ago. Settings fail twice. Retention was left at the 2-month default,
so the explorations the new team wants to build have no history, and the internal traffic filter has sat
in testing for a year, which means the office's roughly 900 sessions a month have been counted as
visitors throughout. Events fail on registration: a property_type parameter has been sent with every
generate_lead event for 14 months but was never registered as a dimension, so it cannot be reported on.
The agency creates a new property in its own account, migrates the configuration and accepts the loss of
history rather than build on a property it does not own.
Common mistakes
- Ticking "tag on every template" from the homepage. The pages that matter most, checkout, confirmation, error and search results, are the ones built from different templates and the ones most often missed.
- Creating events before the plan. Names are invented at the keyboard, parameters differ between similar events, and the clean-up means renaming data that reports already use.
- Registering dimensions after the fact. A parameter sent before it is registered is collected but cannot be reported on for the period before registration.
- Linking the advertising account with auto-tagging off. The link exists, but sessions arrive without the click identifier and the import has nothing to match.
- Forgetting the unwanted referrals list. Every payment or booking provider on another domain becomes a traffic source and takes credit for sales that the campaign earned.
- Calling the setup finished at the first page view. Verification means every key event, with its parameters, compared with a count from outside Analytics after a few days.
The tracking verification checklist is the next list to open once this one is complete, and the checklists library holds the campaign and page lists that depend on a property set up this way.
