Whether you're an agency taking over from a previous agency, an in-house analyst stepping into a new role, or a consultant brought in to assess a client's setup — inheriting a GA4 property puts you in the same position: responsible for data you didn't create, built on decisions you weren't part of.
The property might be well set up. It might be a mess. It's almost always somewhere in between — some things configured correctly, some things wrong, and some things that were once correct but have drifted over time as the site evolved and nobody kept the tracking in sync.
The first job is to find out which is which. Until you know what you've been handed, you can't trust any of it — and you certainly can't make recommendations based on it.
Start with Events and Conversions
Event tracking and conversion tracking are the first things to verify when you inherit a property. They're the foundation of everything — without them, you don't know whether the data represents what's actually happening on the site.
The most common inheritance problems sit here. Events that exist in GA4 but haven't fired in months. Conversion events that are technically active but tracking the wrong interaction. Purchase events missing critical parameters like transaction_id or value. Duplicate events that double-count every interaction. Naming conventions that are inconsistent — the same action tracked as three different event names by three different people over time.
None of these are obvious from looking at the GA4 reports surface. A conversion event that's been misconfigured still appears in the events list. It still shows a count. The count is just wrong.
Build an Event Inventory
Before you can assess whether the tracking is correct, you need a complete picture of what's there. Pull a full list of events from the GA4 property — every event that has fired in the last 90 days — and work through it systematically.
For each event, establish:
- What is this event supposed to track?
- Is it firing on the right interaction?
- Is it firing at the right frequency — not too often, not missing fires?
- Does it have the parameters it needs — and are those parameters returning the right values?
- Is it a conversion event, and if so, is it the right one?
- Who set it up and when — is there any documentation?
There will be events you can't explain. Events with names that give no indication of what they track. Events that fire thousands of times a day with no obvious corresponding user action. Events that fired once three months ago and never again. These are the inherited technical debt of a property that wasn't maintained — and they need to be classified before you can work with the data.
Review the GTM Container
Most GA4 implementations are managed through Google Tag Manager. The GTM container is where the implementation decisions were made — and where most of the problems will be visible.
When you inherit a property, open the GTM container and take inventory:
- How many tags are there, and how many are active?
- When were tags last modified, and by whom?
- Are tags named clearly and consistently — or is naming ad hoc?
- Are there zombie tags — tags that are still active but shouldn't be firing?
- Are trigger conditions specific enough, or are tags firing more broadly than intended?
- Is there documentation — tag descriptions, notes, a change log?
The GTM container tells the story of how the implementation evolved over time. You'll see the original setup, the campaign tags that got added and never removed, the quick fixes that became permanent, the failed experiments that never got cleaned up. That history is useful context for understanding why the property looks the way it does.
It's also where you'll find most of the conversion tracking issues. Use GTM's preview mode to walk through the critical user journeys — form submissions, purchases, key CTA clicks — and verify that the right tags fire at the right moments with the right data.
Check the Property Configuration
Beyond event tracking, a range of property-level settings affect data quality and need to be verified when you take over a property. These are easy to miss because they don't show up in event reports — they just silently affect everything.
- Data retention — is it set to 14 months? The default is 2 months, and it's common to inherit a property where nobody changed it.
- Internal traffic filter — is the company's own traffic excluded? If not, employee sessions are in your data.
- Referral exclusions — are payment processors excluded? If Stripe or PayPal appears as a traffic source, conversion attribution is broken.
- Data streams — are there duplicate streams? Stale streams that stopped receiving data? Cross-domain configuration for properties spanning multiple domains?
- Consent Mode — is it implemented? Is it implemented correctly? For any property receiving EEA traffic, this is a compliance requirement.
- Attribution model — what model is in use, and is it appropriate for the business?
Establish a Trustworthy Baseline
Once you've worked through the event inventory, the GTM container, and the property configuration, you have enough of a picture to make a judgment: is this data trustworthy enough to work with, or does it need remediation before you can use it as a foundation?
The answer is usually "it needs some work." The question is how much, and what the priority order is.
A practical approach:
- Fix conversion tracking first — this is what decisions are made on. If purchase events or lead form events are misconfigured, fix them before anything else.
- Document what you found — create a record of the property's state when you took it over. This protects you if historical data is questioned later, and gives you a baseline to measure improvement against.
- Be honest about data gaps — if the previous setup was tracking something incorrectly, historical data for that metric is unreliable. Acknowledge that clearly rather than presenting it as accurate.
- Fix before you report — don't produce a quarterly report or a campaign performance analysis on data you know is wrong. Fix the tracking first, even if that means a short delay.
Run a Full Audit on Day One
A manual audit of an inherited property takes time — working through the event inventory, the GTM container, the property configuration. GA4 Health Check runs 50+ checks automatically in 60 seconds, giving you a complete diagnostic picture of the property's health from the moment you take it over.
Run it on day one. Know what you're working with before you make a single recommendation or produce a single report. The audit report becomes your baseline — the documented state of the property when you took responsibility for it.
Audit your inherited property — $79 →
