GA4 Events Not Showing Data: How to Find and Fix It

When Google Analytics 4 (GA4) events do not appear in your reports, the cause is usually processing latency, incorrect tag configuration, or reporting interface thresholds. Follow this technical troubleshooting guide to locate and resolve the issue.

1. Rule Out the 24-48 Hour Processing Delay

GA4 does not process data in real-time for standard reports. While the Realtime report shows activity from the last 30 minutes, standard reports and the Explorations tool take 24 to 48 hours to fully populate. If you created or triggered an event today, wait 48 hours before troubleshooting configuration issues.

2. Verify Event Firing in GA4 DebugView

If events do not appear after 48 hours, verify that the browser is actually sending the data to Google's servers using GA4 DebugView.

• Install the Google Tag Assistant browser extension or open tagassistant.google.com.
• Connect your website URL to start a debugging session.
• In GA4, navigate to Admin > Data display > DebugView.
• Perform the action on your site that triggers the event.
• If the event appears in the DebugView timeline, your code and tags are working. The issue is reporting latency or data filtering. If nothing appears, the tag is not firing.

3. Inspect Browser Network Payloads

If DebugView is empty, bypass GA4 interfaces entirely and inspect the raw HTTP requests sent by the browser.

1. Open your website and open your browser's Developer Tools (F12 or Right-click > Inspect).
2. Select the Network tab.
3. In the filter box, type collect?v=2 to isolate GA4 network requests.
4. Trigger your event (e.g., click a button or submit a form).
5. Look for a network request. A successful transmission returns a 204 No Content HTTP status code.
6. Click the request and view the Payload. Look for the en parameter (Event Name). For example, en=generate_lead confirms the event name being sent.

If you do not see a collect?v=2 request, your tracking code is not executing. Ensure your gtag.js or Google Tag Manager (GTM) container is properly installed. Here is an example of a correct programmatic event dispatch using gtag.js:

// Correct GA4 event dispatch syntax
gtag('event', 'generate_lead', {
  'currency': 'USD',
  'value': 29.99,
  'lead_type': 'newsletter'
});

4. Register Custom Dimensions for Event Parameters

If the event name appears in your reports but the custom parameters (like lead_type in the example above) are missing, you must register them in the GA4 UI. GA4 discards custom parameters from standard reports unless they are explicitly registered.

• Go to Admin > Data display > Custom definitions.
• Click Create custom dimension.
• Set the Scope (usually "Event").
• Enter the exact Event parameter name as sent in your code (e.g., lead_type).
• Save the dimension. Data will begin populating only from the moment of registration forward; this step is not retroactive.

5. Disable Data Thresholding and Internal Filters

If events are firing but missing selectively from reports, check your filtering and identity settings:

• Internal Traffic Filters: Go to Admin > Data streams > [Your Stream] > Configure tag settings > Define internal traffic. If your IP is filtered out, your test events will not be recorded in production reports.
• Reporting Identity Thresholds: If Google Signals is enabled and your site has low traffic, GA4 hides rows with small user counts to prevent identity reconstruction. To check if thresholding is hiding your events, go to Admin > Data display > Reporting Identity, click Show all, select Device-only, and save. This does not delete data; it changes how reports are displayed.

Need this done fast? order GA4 setup on Kwork.