Use these 12 practical tests to find missing events, duplicate tracking, attribution errors, and broken conversions in Google Analytics 4.
A green status icon in Google Analytics does not prove that your data is correct. GA4 can receive page views while missing form submissions, double-counting purchases, mislabeling traffic sources, or sending the wrong conversions to Google Ads.
This guide gives you a practical way to check whether GA4 is working correctly. It is designed as an initial health check, not a replacement for a full implementation review.
1. Confirm the GA4 Tag Loads on Every Important Page
Open Google Tag Manager Preview mode or Google Tag Assistant, connect your website, and visit the homepage, service pages, contact page, and any checkout or booking steps. The GA4 configuration tag should load once on each page. A tag that is missing from templates or fires twice immediately makes the rest of your reporting unreliable.
2. Check Realtime Reporting
Open GA4 Realtime and visit the website from a device or browser that is not excluded as internal traffic. You should see your session, page views, and interactions within seconds. If nothing appears, check the measurement ID, consent state, browser extensions, and tag firing rules.
3. Use DebugView to Inspect Events
Realtime confirms that some data arrives. DebugView shows what each event contains. Submit a form, click a phone number, play a video, and complete other important actions. Confirm that the expected event appears once and carries useful parameters such as form name, page location, product ID, or value.
4. Look for Duplicate Page Views and Events
Duplicate tracking often happens when GA4 is installed both directly in the website code and through Google Tag Manager. It can also happen when a trigger fires on the initial action and again on a confirmation page. Compare one controlled action with DebugView: one action should normally create one intended event.
5. Test Every Key Event Yourself
Do not assume a conversion works because its name exists in GA4. Complete the actual journey from the website. Test every form, booking, call click, sign-up, checkout, and purchase flow. Confirm that the event appears, is marked as a key event where appropriate, and is not triggered by failed or abandoned actions.
6. Check Event Names and Parameters
GA4 event names are case-sensitive. Events called generate_lead, Generate_Lead, and form_submit appear separately even if they describe the same outcome. Use consistent names and make sure important parameters are registered as custom dimensions when your reports need them.
7. Compare Leads With Your CRM or Inbox
Choose a recent period and compare GA4 lead counts with received forms, booked calls, or CRM records. The numbers may not match perfectly because of consent and attribution rules, but large differences point to missing triggers, duplicates, spam, or a definition problem.
8. Compare eCommerce Revenue With the Store
For eCommerce websites, compare transaction count and revenue against the commerce platform. Check currency, tax, shipping, refunds, coupon data, and unique transaction IDs. Repeated transaction IDs or missing purchase values can make return-on-ad-spend reporting dangerously misleading.
9. Review Direct and Unassigned Traffic
A large increase in direct or unassigned traffic can indicate missing UTM parameters, redirects that strip campaign information, cross-domain problems, or events sent without valid session context. Review acquisition reports alongside recent website and campaign changes.
10. Look for Self-Referrals and Payment Gateways
Your own domain, checkout domain, booking platform, or payment provider should not appear as a major referral source. If it does, sessions may be breaking during the journey and the final conversion may be credited to the wrong channel.
11. Verify Internal Traffic and Consent Behavior
Check whether staff visits are excluded and whether the filter is active rather than merely defined. Test the cookie banner with both accepted and rejected consent. Tags should respect the user's choice, and Consent Mode should reflect the correct state throughout the session.
12. Check Google Ads and Search Console Links
Confirm that the correct properties and advertising accounts are linked. Review which key events Google Ads imports and make sure bidding is not optimizing toward low-value actions such as page views. Search Console integration should use the correct web property.
What to Do When a Test Fails
Document the failing journey, the expected result, the actual result, and the date tested. Avoid changing several tags at once: fix one issue in a test environment, validate it in Preview and DebugView, then publish with a clear version note.
A short health check can catch obvious faults. A full GA4 audit goes further by reviewing property settings, attribution, integrations, privacy, eCommerce, and data quality as one system. If the setup needs rebuilding rather than isolated fixes, see our GA4 migration and implementation service.
For the complete implementation sequence, read our GA4 setup guide. If you need hands-on diagnosis and reporting support, speak with a Google Analytics consultant.