GA4 Tracking Audit Checklist: Find Missing Events, Broken Conversions, and Attribution Gaps

Overview

Good web analytics depends on more than installing a tracking tag. Your measurement setup also needs clear event definitions, reliable data collection, correctly configured key events, and reporting that matches the actions your business cares about. A page can appear to be receiving traffic while important form submissions, purchases, calls, or checkout steps are missing from GA4.

An audit is a structured comparison between what users do and what your analytics property records. Start with a written tracking plan that lists each important action, its event name, relevant parameters, business purpose, destination reports, and owner. If you need a starting point, the website tracking plan template can help document this information before testing begins.

Use a test account or clearly labeled test activity where possible. Record the date, page or workflow tested, device and browser, consent choice, expected result, actual result, and any follow-up task. This makes the audit repeatable and gives developers or campaign owners enough detail to investigate a problem.

Checklist by scenario

1. Core GA4 setup and data collection

• Confirm that the intended GA4 data stream is connected to the correct website or app.
• Check that the measurement ID is consistent across the pages and environments that should be tracked.
• Test the homepage, key landing pages, product or service pages, forms, checkout pages, and confirmation pages.
• Look for duplicate page views or multiple tag installations that could inflate sessions and events.
• Verify that internal development, staging, and preview traffic is handled according to your reporting requirements.
• Review enhanced measurement settings and confirm that enabled features match the site experience.

Do not assume that an active data stream proves the setup is complete. It only shows that some data is arriving. Compare the collected activity with the actions listed in your tracking plan.

2. GA4 event tracking

• List the events expected for navigation, engagement, forms, downloads, video interaction, searches, and transactions.
• Check event names for consistent spelling, capitalization, and meaning.
• Confirm that important parameters are sent with the event, such as form name, button label, content type, item identifier, or value where appropriate.
• Make sure the same user action does not trigger multiple events through overlapping tags, listeners, or plugins.
• Test interactions on desktop and mobile, including menus, accordions, sticky buttons, pop-ups, and embedded forms.
• Use real-time or debugging views to confirm that events fire at the intended moment rather than on page load.

Event collection and conversion measurement are separate checks. An event may arrive correctly but still be absent from the conversion reports because it has not been marked as a key event or because the reporting configuration is incomplete.

3. Conversion tracking

• Define the conversion action precisely: submitted form, completed order, qualified lead, booked call, account creation, or another measurable outcome.
• Confirm that each primary conversion has one dependable trigger, preferably tied to a successful outcome rather than a generic button click.
• Check that confirmation pages cannot be refreshed repeatedly to create false additional conversions.
• Compare GA4 conversion counts with the source system, such as a CRM, order database, booking platform, or form tool.
• Review whether value, currency, transaction ID, and product details are passed when revenue or transaction analysis is required.
• Separate primary conversions from supporting actions so reports do not treat every interaction as equally valuable.

Small differences between systems can have several causes, including time zones, attribution rules, consent choices, duplicate submissions, and different definitions of a conversion. The purpose of the audit is not always to force identical totals; it is to understand and document the differences.

4. Forms, buttons, and landing pages

• Test successful submissions, validation errors, abandoned forms, and forms that open in modal windows.
• Check whether a form event fires when the form is displayed, when a user starts typing, or only after a valid submission.
• Track important call-to-action clicks without counting every repeated click as a completed lead.
• Verify that button labels and form names are readable enough to use in reports.
• Review landing page dimensions such as entrances, engagement, form starts, submissions, and downstream conversions.

For conversion rate optimization, distinguish between a micro-conversion and the business outcome. A click can help diagnose friction, but it should not replace a completed lead or sale in performance reporting.

5. UTM parameters and campaign attribution

• Check that campaign URLs use a consistent naming convention for source, medium, campaign, content, and term where relevant.
• Use lowercase conventions if that is how your organization avoids duplicate campaign values.
• Confirm that redirects, link shorteners, consent tools, and landing page scripts do not remove UTM parameters.
• Test links in email, paid media, social posts, partner placements, and offline QR codes.
• Check that campaign values are visible in the expected acquisition reports and are not being overwritten unexpectedly.

A consistent campaign naming system is easier to audit than ad hoc labels. Use the UTM parameter builder and campaign naming guide to establish rules before launching a new campaign.

6. Cross-domain journeys

• List every domain or subdomain involved in the conversion path, including booking, payment, checkout, support, or form platforms.
• Move through the full journey from the original landing page to the final confirmation.
• Check whether the journey remains associated with the same user and session where the setup is intended to preserve continuity.
• Look for referral traffic from your own domains that may indicate a broken cross-domain configuration.
• Confirm that the final conversion is recorded once and assigned to a useful campaign source.

Cross-domain tracking should be tested after changes to checkout providers, booking tools, consent systems, or domain structure. A workflow that worked before a vendor or platform change may need to be reviewed again.

What to double-check

After testing individual actions, review the data as a reporting user. Open the acquisition, engagement, and conversion reports used for regular decisions and ask whether the dimensions and metrics answer the questions your team actually has.

• Data freshness: Identify which reports are expected to update quickly and which may require processing time before comparison.
• Attribution scope: Confirm whether a report uses user, session, event, or conversion-level attribution. These perspectives can produce different results.
• Consent effects: Note whether users who decline or limit consent are represented differently from users who allow analytics storage. Treat unexplained gaps as a measurement limitation, not automatically as a traffic problem.
• Filters and exclusions: Review internal traffic rules, developer traffic exclusions, referral exclusions, and other settings that can change totals.
• Time zones: Check the property time zone before comparing daily figures with ad platforms, CRM exports, or financial systems.
• Revenue and lead quality: A conversion count alone does not show whether leads are qualified or orders are profitable. Connect analytics with downstream business data where possible.

For ongoing reporting, document the definitions behind your main metrics. A marketing dashboard template can provide a useful framework for connecting traffic, funnel stages, conversions, and campaign outcomes without treating every available metric as a KPI.

Common mistakes

1. Auditing only the homepage: Tracking often breaks on forms, checkout steps, embedded tools, or newly published landing pages.
2. Counting clicks as completed conversions: A click indicates intent, not necessarily a successful outcome.
3. Changing event names without a migration plan: Renaming events can split historical and current reporting or cause key events to stop working.
4. Ignoring duplicates: Multiple tags, repeated submissions, and refreshed confirmation pages can make performance appear stronger than it is.
5. Using inconsistent UTMs: Variations in capitalization, spelling, or medium names fragment campaign attribution.
6. Comparing platforms without defining the comparison: GA4, advertising platforms, CRMs, and order systems may use different attribution windows, time zones, and counting rules.
7. Testing only one device: Responsive layouts and mobile form behavior can change whether events fire.
8. Failing to record the fix: Without a change log, the same tracking problem can return during a redesign or tag update.

If you find a serious discrepancy, preserve the evidence before changing the setup. Save example URLs, timestamps, screenshots, debug output, and the expected-versus-actual result. Then assign an owner and retest after the fix.

When to revisit

Run a lightweight tracking review at a regular interval and a deeper audit whenever the underlying inputs change. At minimum, revisit the checklist:

• before seasonal planning cycles or major campaign launches;
• after a website redesign, CMS migration, checkout change, or form replacement;
• when adding a new advertising platform, analytics tool, or consent workflow;
• after changing event names, key events, reporting filters, or UTM conventions;
• when conversion totals diverge noticeably from CRM, order, or booking records;
• when a dashboard suddenly shows a sharp increase, decrease, or unexplained change in traffic or conversions.

Use a simple recurring schedule: review critical conversions and campaign links before each launch, test the main funnel monthly or at another practical interval, and complete a broader audit during planning cycles. Keep a dated audit log with findings, severity, owner, resolution, and retest result.

For a final pre-launch pass, combine this checklist with the campaign attribution checklist. If the setup needs a broader configuration review, use the GA4 setup checklist as a companion. The practical goal is not perfect data; it is trustworthy enough measurement, clearly stated limitations, and a repeatable process for finding problems before they influence decisions.