GA4 Event Tracking Audit:
How to Verify Every Event
Is Firing Correctly

Before verifying individual events, confirm that GA4 is only being loaded once per page. Duplicate tag loading — where both a GTM-managed GA4 tag and a hardcoded <script> snippet are present — is the most common cause of doubled event counts. Every event fires twice. Every conversion is counted twice. Revenue appears doubled.

Open Tag Assistant on your site's homepage. Look at the tags panel. You should see exactly one GA4 configuration tag associated with your measurement ID. If you see two GA4 tags — one from GTM and one from a direct script — you have duplicate firing.

Also check for multiple GTM containers. A site with two active GTM containers can result in GA4 events firing from both — particularly if a migration left the old container active. Tag Assistant shows all GTM containers present on the page.

Go to Admin → Events. This is your master list of every event GA4 has recorded in your property. Work through it systematically with three questions for each event:

1. Is this event still needed? Properties accumulate events over time — old experiments, deprecated features, renamed events that were replaced but never removed. An event list with 40+ events is almost always carrying dead weight that adds noise to reports.
2. When did it last fire? The event list shows last-activity dates. Any event that hasn't fired recently on an active site — particularly any event marked as a conversion — needs investigation.
3. Is the naming convention correct? GA4 recommends snake_case. Scan for camelCase, spaces, hyphens, or mixed capitalisation. Each naming variant creates a separate event in GA4 even if it represents the same user action.

Build a simple inventory as you go — event name, expected trigger, last fired date, marked as conversion (yes/no). This becomes the checklist you verify against in DebugView.

With your event inventory ready, activate DebugView and work through each event manually — performing the user action and confirming what GA4 receives. Open Admin → DebugView in one browser tab. In another tab, navigate to your site with the debug parameter active or the GA Debugger extension enabled.

For each event, verify four things:

1. It fires when it should. Perform the trigger action — click the button, submit the form, reach the page. The event should appear in DebugView within a few seconds. If it doesn't appear after 15–20 seconds, the tag is not firing.

2. It fires only once. Watch the DebugView stream carefully after performing a single trigger action. If the same event appears twice within a few seconds of each other, you have duplicate firing. Check GTM for multiple triggers on the same tag, and check for both a GTM-managed and hardcoded version of the same event.

3. It fires only when it should. Navigate to pages where the event should NOT fire and verify it doesn't appear in DebugView. A purchase event that fires on the homepage is a serious problem. A form_submit event that fires on page load rather than on submission is counting every page view as a conversion.

4. All required parameters are present and correct. Click the event in DebugView to expand its parameter list. Verify every required parameter is present with the expected value. For the purchase event specifically, confirm all of the following:

purchase event — required parameters:
  transaction_id  → unique order ID (string)
  value           → order total (number, not string)
  currency        → ISO 4217 code e.g. "GBP", "USD"
  items           → array with at least one item object
    items[0].item_id    → product identifier
    items[0].item_name  → product name
    items[0].price      → unit price (number)
    items[0].quantity   → quantity (integer)

Conversion events deserve a separate, more rigorous pass because their accuracy directly affects Smart Bidding, campaign reporting, and every CRO decision you make. Go back to Admin → Events and filter for events with the conversion toggle enabled.

The zombie conversion check

For each conversion event, check when it last fired. GA4 doesn't surface this prominently — you need to go to Reports → Engagement → Events, filter for the specific event name, and look at the trend over time. A conversion event that shows consistent activity up to a point and then flatlines is a broken tag. A conversion event that shows no activity at all since it was created was likely never implemented correctly.

The volume sanity check

For your primary purchase or lead conversion event, compare GA4's reported count against your actual business records for the same period. Go to Reports → Monetisation → Ecommerce purchases (or filter by your conversion event in the Events report) and note the total for any recent 30-day period. Compare against your CRM, e-commerce platform, or payment processor for the same dates.

The Smart Bidding signal check

If Google Ads is connected, go to your Google Ads account and check which conversion actions are active and receiving data. A GA4 conversion event that's imported into Google Ads as a conversion action but has stopped firing is silently degrading Smart Bidding performance. The campaign continues to spend. The algorithm continues to optimise. But the signal it's optimising against is weeks or months out of date.

If your site has e-commerce functionality, the full event funnel requires seven events in sequence. Each missing event is a funnel step you cannot analyse. Work through each one in DebugView by navigating the purchase journey on your site:

Any missing event means you have a blind spot in your funnel analysis. You can see that users are abandoning somewhere between add_to_cart and purchase — but without each intermediate event, you cannot determine where.

Go to Admin → Events and sort the event list alphabetically. Scan for naming inconsistencies — the same conceptual event appearing under multiple names due to casing differences, formatting variations, or incremental naming changes that weren't cleaned up.

Common examples of fragmented events:

For historical variants that can't be re-tagged, use GA4's event renaming feature in Admin → Events → Modify event to consolidate them going forward. For new implementation, enforce snake_case as the standard across your entire team before anything is deployed.