When to run this checklist
Run it whenever a Google Analytics property changes hands: an agency leaves or a new one arrives, the analyst who built the property moves on, a freelancer's contract ends, or the business is sold, merged or split. Run it before the outgoing owner's access is removed, not after; most of the lines need their cooperation, and the documentation group in particular cannot be completed by someone reading the property cold.
The outgoing owner prepares the material and the incoming owner ticks the lines, with a person from the business present for the ownership group, because the point of that group is that the business itself, not either agency, ends up in control. Anything the handover reveals was never configured, such as an internal traffic rule that was never set, belongs to the GA4 setup checklist rather than this one. Scoring how good the inherited implementation is belongs to the analytics implementation audit, which is worth scheduling once the handover is complete, and tidying what the property has accumulated, from key events and custom definitions to interface rules and audiences, is the tutorial on cleaning up an inherited GA4 property. When the analytics property is only one part of a whole programme changing hands, the tutorial on taking over an existing marketing programme puts this checklist inside a wider inventory of accounts, spend, contracts, assets and customer data.
Before you start
- Administrator access for a named person at the business, granted before anything else is changed.
- The tracking plan or whatever stands in for it: a spreadsheet, a ticket history, the container itself. The tracking plan guide describes what a complete one contains.
- A list of linked products: Google Ads accounts, Search Console properties, BigQuery projects and any other integrations shown in the property's admin area.
- The GTMTag management system. container, with its version history and a note of who can publish.
- A list of reports and dashboards known to read from the property, from the people who use them.
- An hour with the outgoing owner, booked, to walk through the decisions nobody wrote down.
The checklist
The groups run in the order a handover goes safely: secure control first, then capture what is known, then move what is connected, then hand over the tags, and only then confirm nothing stopped. Do not remove the outgoing owner's access until the documentation group is complete.
Ownership and access
Documentation
Integrations
Tag setup
Verification
Where each check is explained
The widget keeps each line short enough to tick; the reasoning sits in the guides. Each check links to the page that explains it.
| Check | Explained in |
|---|---|
| Confirm the business owns the account and holds administrator rights | GA4 setup, step by step |
| List every user and remove anyone who no longer needs access | GA4 setup, step by step |
| Move linked Google Ads, Search Console and BigQuery projects into the business's ownership | GA4 and Google Ads integration |
| Hand over the tracking plan with every event and parameter in use | Tracking plans |
| List the key events and why each one counts | Key events and conversions in GA4 |
| Record custom dimensions and audiences with their purpose | GA4 audiences |
| Document filters, internal traffic rules and unwanted referrals | Common GA4 mistakes |
| Confirm the BigQuery export runs in a project the business controls | BigQuery export basics |
| Check the advertising link, auto-tagging and imported key events | GA4 and Google Ads integration |
| List the dashboards and data sources that read from the property | Dashboard governance |
| Hand over the tag container together with its version history | Container governance |
| Record how consent is configured and who maintains it | Consent mode |
| Check data still arrives after the access changes | GA4 not showing any data |
| Agree who answers data questions from now on | Marketing data quality |
If an item fails
An ownership failure is the one to escalate the same day. If the business does not hold administrator rights on its own account, or the property sits in an account the agency owns, nothing else on the list is safe until that is resolved; ask the current administrator to grant the business admin access before any other change. The same applies to a BigQuery export billed to the outgoing owner's project: once their project closes, the export stops, and the history it held may go with it. The BigQuery export basics guide explains how the link is set up so it can be recreated in a project the business controls. If the current administrator will neither grant the business admin access nor move the property, the tutorial on moving to a new GA4 property builds a replacement in the business's own account and runs it beside the old one until links, conversions and reports have moved.
Documentation failures are common and rarely block the handover, but they should be written down as gaps rather than ticked. A custom dimensionA GA4 reporting field created by registering an event, user or item parameter so it appears in reports and explorations. with no recorded purpose belongs on the same list, with the date it was registered, because its reports start on that date. A Key EventA GA4 event marked as important to the business, the property's measure of success. nobody can justify should be listed with a question mark and reviewed, not deleted on the spot, because a Google Ads campaign may be bidding on it. An advertising link where Auto-TaggingA Google Ads setting that adds a click identifier (GCLID) to every ad click's landing URL. is off, or key events are imported twice, is a measurement fault in its own right and goes to the GA4 and Google Ads integration guide.
If data stops arriving after access changes, check first whether a tag or a data streamA source of data flowing into a GA4 property: one web stream for a site or an app stream for each iOS or Android app, each with its own settings. was owned by a removed user's account, then work through the GA4 not collecting data guide.
A letting agency changes its marketing agency
Marrowby Lettings, a residential letting agency, moves its marketing from one agency to another. The ownership group fails at once: the outgoing agency holds the only administrator login, and the property sits inside the agency's own account alongside forty other clients. The handover pauses for a week while the property is moved into an account the lettings firm owns. The documentation group turns up eleven custom dimensions, of which four are still populated, and a "valuation request" key event that fires twice on the thank-you page. The BigQuery export runs in the old agency's project, so a new project is created under the firm's billing and the export relinked before the old one is closed. A month later, when the new agency asks why valuation requests fell by half, the handover record shows the duplicate was fixed on a known date.
Common mistakes
- Removing the old agency before the handover. The access goes first, the knowledge goes with it, and the incoming team reverse-engineers decisions that one conversation would have explained.
- Treating access as ownership. A long list of users with admin rights is not the same as the business owning the account; check whose organisation the property actually belongs to.
- Forgetting the things outside the property. The tag container, the BigQuery project and the dashboards all have their own owners and their own access lists.
- Deleting what nobody can explain. An unexplained key event or audience may be feeding bidding or remarketing; question it first.
- No named owner at the end. The handover finishes, both agencies assume the other answers data questions, and the first report nobody trusts goes unanswered.
The GA4 setup checklist covers anything the handover shows was never configured, and the checklists library holds the rest.
