Skip to content

Guide 167 · Events · GA4 + Tag Manager

See events in Realtime: the Event count by Event name card and the last 30 minutes

Checked 11 November 2026 · Verification: event reference validated structurally (event, parameters, rules, worked example); worked example recomputed · Steps traced to Analytics Help, opened 11 November 2026 · 6-minute read

The Realtime report is the check that works within minutes: its Event count by Event name card shows each triggered event and the number of times each was triggered in the last 30 minutes, and clicking an event shows the parameters sent with it. This guide uses it to confirm the quote_requested event after publishing, with the limits that keep it a confirmation tool and not a reporting tool.

Expected signal

After the test, the Realtime report shows the visit within a minute, the Event count by Event name card lists quote_requested with a count of 1, and clicking the event shows product_category set to Windows.

Download the reference: the Realtime events reference (JSON) (1600 bytes, MD5 c8f94e02ac694276a298d0965681085a). It lists the worked example — one visit and its events in the last 30 minutes — the card and what it shows, the 30-minute window, and the rule that standard reports take 24 to 48 hours. The report itself is not in the file: it lives in Analytics.

What you need

  • A published tag to test. Here it is the GA4 - quote_requested tag, published as a version. Preview tests a draft; Realtime tests the published site.
  • A normal browser window. Open the site in a normal window with no ad blockers, and click through a few pages. Ad blockers and debug tools change what arrives, and the test should match a real visit.
  • Viewer access or above at the property level. The Realtime report is read-only; no role above Viewer is needed to read it.

The worked example

The check below is one test visit in the last 30 minutes. The number that matters is the total: eleven events, of which one is the quote request.

Event (last 30 minutes)Event count
page_view7
session_start3
quote_requested1
Total events in the card11
Quote requests as a share1 / 11 = 9.09%

Those figures were recomputed here before publication: 7 plus 3 plus 1 is 11 events in the card; 1 divided by 11 is 0.0909, so the quote request is 9.09% of the events in the window. The visit itself is the standard form:

14:00 — open the site, 7 pages viewed
14:04 — click Request a quote
14:04 — quote_requested appears in the card

The trace

  1. Open the site in a normal window. Open the site in a normal browser window, with no ad blockers, and click through a few pages. This step needs no sign-in to the site; the Analytics sign-in comes next.
  2. Open the Realtime report. In Analytics, select Reports, then Realtime overview. The report covers the last 30 minutes: active users in the last 30 and 5 minutes at the top, then cards for users by source and audience, views by page title, event count by event name, and key events by Event name. This step needs a Google sign-in, so it was traced to Google's documentation, not run here.
  3. Find your visit. Your visit should appear in the active users counters within a minute or so. If it does not, the visit did not reach the property: check the Measurement ID in the tag against the web stream first, as the purchase debugging guide's checkpoint 3 covers.
  4. Read the Event count by Event name card. The card lists each triggered event and the number of times each was triggered in the last 30 minutes. In the example, the card shows page_view 7, session_start 3, and quote_requested 1. An event you expect but do not see there means that specific tag or trigger is not working.
  5. Click the event to check its parameters. Click quote_requested in the card to see the event parameters sent with it. product_category must show with the value Windows. The card is the fastest way to confirm the two parameters of the event value guide arrived together.
  6. Stop there. Realtime has limited attribution, so do not use it to judge sources. If the event is in the card, collection works: missing data in standard reports is then about processing time, date ranges, or filters — and standard reports can take 24 to 48 hours.

Dead ends

DEAD END — READING REALTIME AS A REPORT. Realtime covers 30 minutes and has limited attribution. A source that looks wrong in Realtime is not a broken source; it is a window that is too small to judge. Reports are for trends; Realtime is for confirmation.

DEAD END — THE VISIT IS MISSING BECAUSE OF THE FILTER. A Realtime view filtered to a segment or a comparison that excludes your session hides your own visit. Check the comparison at the top of the report before concluding the tag is broken.

DEAD END — WAITING FOR STANDARD REPORTS TO CONFIRM A TAG. Standard reports can take 24 to 48 hours to process data. A tag confirmed in Realtime does not need a day of waiting, and a tag that is broken does not get fixed by waiting either.

End state

One visit, one card, one click. The event shows in the Event count by Event name card within a minute of firing, with its parameters visible on click, and the standard reports pick it up within 24 to 48 hours. The next step after a Realtime confirmation is the Events report — and the step after a Realtime failure is DebugView, which shows the event for one user with its parameters.

Sources

  • Analytics Help — About events — the Event count by Event name card in the Realtime report shows each triggered event and the number of times each was triggered in the last 30 minutes; click an event to see its parameters
  • Analytics Help — Events report — data about an event appears in the report up to 24 hours from when the event was triggered; to verify collection in the last 30 minutes, see the Realtime report
  • Analytics Help — Confirm that you are collecting data — many reports and explorations can take 24 to 48 hours to process data; Realtime and DebugView confirm collection sooner

Checked 11 November 2026. The click paths above are the ones in Google's help and developer pages, opened 11 November 2026. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. What was run: the reference file was validated structurally in Python 3.12.3 — it parses, the event is quote_requested, the card rows are present — and the card total was recomputed: 7 + 3 + 1 = 11 events in the last 30 minutes; 1 / 11 = 9.09% for the quote request. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.