GA4
GA4 audit checklist: what to check before your next campaign launch
A practical GA4 audit checklist: check GA4 is working, test key events in DebugView, verify UTM and cross-domain tracking, and confirm Google Ads imports.
A GA4 audit is a structured check that proves your Google Analytics 4 property records the actions your campaigns depend on: once, at the right moment, with the right values, and with enough context to explain where the visitor came from.
Campaign reporting should not begin after the campaign launches. By then, a missing parameter or duplicated conversion has already affected bidding, attribution, and the decisions your team makes from the data. A focused audit before launch is not about checking every setting. It is about proving that the campaign journey produces one complete and trustworthy record.
The quick GA4 audit checklist
Use this table as the short version. The sections below explain how to run each check.
| Check | What good looks like | Where to verify |
|---|---|---|
| Business action defined | One written rule for what makes a lead or purchase valid | Measurement plan |
| GA4 is collecting | page_view and key events arrive with correct parameters |
DebugView, network tab |
| Events fire once | One event per completed action, only after success | GTM preview, DebugView |
| Ecommerce values | transaction_id, value, currency, and items are complete |
DebugView, backend order |
| Campaign context | UTM values survive redirects and domain changes | Landing page URL, DebugView |
| Source of truth | Test orders or leads match backend or CRM records | Order system, CRM |
| Ads optimization | Google Ads bids on the intended key event, counted once | Google Ads conversions |
1. What business action should the campaign create?
Choose the action the campaign is meant to create. It might be a qualified lead, a completed purchase, or a booked consultation.
Write down the exact conditions that make the action valid. For a lead, that could mean a successful server response rather than a form button click. For a purchase, it means a confirmed order with a real transaction ID, currency, and value.
This definition becomes the reference for every later check. Without it, an event can be technically active while still measuring the wrong thing.
2. How do you check that GA4 is working?
Start with one real test journey. Use Google Tag Manager preview mode or the Google Analytics debugger so your device appears in GA4 DebugView, then move through the journey exactly as a customer would.
Three views together give you a reliable answer:
- DebugView shows which events GA4 received and the parameters attached to each one.
- The browser network tab shows the actual request that left the page, which helps when a tag fires but the payload is wrong.
- The Realtime report confirms that the property, not just the debug stream, is receiving traffic.
If GA4 is installed twice, for example through GTM and a hard-coded tag, you will see duplicate page_view events here. Fix that before testing anything else.
3. How do you test GA4 events and key events?
Confirm that each important event only fires after the action succeeds. Check these details:
- The event name is consistent and intentional.
- The event fires once per completed action.
- Required parameters contain real values, not placeholders.
- Ecommerce arrays contain the expected items.
- Personally identifiable information is not sent to GA4.
- Consent state is available before tags make a decision.
For ecommerce, compare the purchase event with Google’s recommended ecommerce parameters. A missing or reused transaction_id is one of the most common causes of duplicate GA4 transactions.
Then open the GA4 admin and confirm the right events are marked as key events. Google renamed GA4 conversions to key events in 2024, so older guides and dashboards may still use the old name. Google explains the difference in Conversions vs. key events.
Pay special attention to single-page interactions. Route changes, modal submissions, and dynamically rendered confirmations can cause an event to fire too early or more than once.
4. Are UTM parameters and campaign context preserved?
The conversion event is only part of the journey. Your landing page also needs to preserve the information that explains where the visitor came from.
Test a URL containing the campaign parameters you actually plan to use. Confirm that the landing page loads without stripping them, that redirects keep the full query string, and that navigation does not accidentally replace the session context.
If traffic moves between domains, such as a separate checkout or booking tool, test the complete journey and confirm cross-domain measurement is configured. A clean event at the end is not enough if the session was split in the middle.
5. Does GA4 match the source of truth?
GA4 is a measurement system, not your order database or CRM. Before launch, compare test events against the system that confirms the actual outcome.
For purchases, match transaction IDs, totals, discounts, tax, and shipping logic. For leads, match a form submission or booking ID to the CRM record. The goal is not to make every interface show the same count instantly. The goal is to prove that each measured event maps to a real business record.
Some gap between GA4 and your backend is normal once real traffic arrives, because consent choices and browser restrictions remove part of the signal. I explain how to judge that gap in why ad platforms report different conversion totals.
6. Is Google Ads optimizing toward the right key event?
Confirm that old or test events are not still marked as key events, and then review the linked advertising account.
If you import GA4 key events into Google Ads, check that the same action is not also tracked by a Google Ads conversion tag set as primary. Two primary conversion actions for one purchase make bidding optimize on a doubled number.
Make sure the campaign is using the intended conversion action, not a page visit, button click, or legacy event with a similar name. A technically correct GA4 event can still be useless if the advertising platform optimizes toward the wrong action.
7. Keep a launch record
Save a short validation note with the test date, environment, consent state, test transaction or lead ID, screenshots, and the person who verified the setup.
This record makes future debugging much faster. When performance changes, you can separate a measurement regression from a real change in user behavior.
The minimum launch standard
Before paid traffic begins, you should be able to answer five questions confidently:
- What exact user action creates the conversion?
- Does the event fire only after success?
- Are its important parameters complete and correct?
- Can it be matched to a real backend or CRM record?
- Is the advertising platform optimizing toward this exact action?
If any answer is unclear, the campaign is not measurement-ready yet. If you want a second pair of eyes before launch, a GA4 and conversion tracking audit follows this same path. A GA4 implementation covers rebuilding the events properly when the audit shows deeper problems.
Frequently asked questions
How do I check if GA4 is working on my website?
Open GA4 DebugView, enable debug mode with Google Tag Manager preview or the Google Analytics debugger, and complete a real journey on the site. You should see page_view and your important events arrive with the expected parameters. Then confirm the same events in the browser's network tab and in the Realtime report.
What are key events in GA4?
Key events are the GA4 events you mark as important to your business, such as purchase, generate_lead, or a booked call. Google renamed GA4 conversions to key events in 2024. The word conversion now refers to the conversion actions that Google Ads uses for bidding.
How do I import GA4 key events into Google Ads?
Link the GA4 property to the Google Ads account, then create a Google Ads conversion action that imports the GA4 key event. Before you do, check that the same action is not already counted by a Google Ads conversion tag, or bidding will optimize on a doubled number.
Why are UTM parameters not showing in GA4?
The most common causes are redirects that strip the query string, cross-domain journeys without linking, inconsistent parameter casing, and checking standard reports before processing finishes. Test the exact campaign URL, watch the landing page URL in the browser, and confirm the session source in DebugView.
How often should you audit GA4?
Run a focused audit before every major campaign launch and after any website release that touches checkout, forms, consent, or tag configuration. Outside of those moments, a quarterly review catches slow drift in events and settings.