Analytics and Tracking

Automatically Collected Event

Also called Default events, auto events

Events GA4 records the moment the tag loads — first visit, session start, page view — with no configuration.

Quick facts: Automatically Collected Event

Category
Analytics and Tracking
Also called
Default events, auto events
Level
Beginner
Affects
Users, sessions, page views, engagement rate
Where to see it
GA4 (Reports, Realtime, DebugView)
In this article4
  1. How automatically collected events work
  2. Why automatically collected events matter
  3. Common mistakes with automatically collected events
  4. How to act on it

How automatically collected events work

As soon as the Google tag is on a page, GA4 begins recording a small set of events without being asked. They include the first visit by a browser, the start of a session, each page view, and a periodic signal that the person is still engaged with the page rather than parked on it. You cannot rename them, and for the most part you cannot switch them off.

They are the foundation the standard reports are built on. Users, sessions, page views and engagement rate all come from this group, which is why a brand new property shows meaningful reports within minutes of the tag going live and before anyone has configured anything at all.

Why automatically collected events matter

Because they set the floor. Even a site with no tagging plan and no developer time still gets traffic volumes, landing pages, sources and basic engagement. For a small business that has just launched, that is genuinely useful and costs nothing beyond installing the tag correctly.

They also make the boundary of free measurement clear. Automatic events describe visiting; they say nothing about your business. Nobody enquiring, booking, calling or buying is represented here. That gap is exactly the work a tagging plan exists to fill, and mistaking one for the other is why so many properties look healthy while answering none of the owner’s questions.

Common mistakes with automatically collected events

The first is treating a page view as an outcome. Counting a visit to the thank-you page as an enquiry works until a page is renamed, a form starts loading its confirmation without a page change, or someone bookmarks that page. The event was never a record of the enquiry; it was a record of a page loading.

The second is confusing this group with the optional one. Scroll, outbound click, file download, site search and video engagement are not automatic — they belong to enhanced measurement, which is switched on per data stream and can be turned off. The third is a single-page site or app where content changes without a real page load, so the page view event fires once and the rest of the journey is invisible.

How to act on it

Take the automatic events as given, confirm they are arriving cleanly, and then be honest about what is missing. List the actions that represent money or intent in your business — an enquiry, a call, a booking, a quote request — and tag each one deliberately rather than inferring it from a page address.

Check the engagement side too, because sessions counted as engaged rest on this group and a site with slow pages or an aggressive consent banner will look worse than it is. If the automatic events are your only measurement today, the sensible next step is a proper GA4 setup that adds the handful of business events on top.

Do and do not

Do

  • Confirm the basic events arrive before building any report
  • List the business actions these events do not cover
  • Send a page view yourself on single-page sites

Do not

  • Treat a thank-you page view as an enquiry record
  • Confuse these with the optional enhanced measurement group
  • Assume the standard reports answer business questions

Questions people ask about this

Can I turn off automatically collected events?

Largely no, and you should not want to. This group is what produces users, sessions, page views and engagement in the standard reports, so removing it would empty most of GA4. What you can control is the optional enhanced measurement group, which is toggled per data stream, and whether the tag fires at all before a visitor gives consent.

Is a page view enough to track an enquiry?

It is fragile. Relying on a visit to a thank-you page breaks the moment that page is renamed, the confirmation appears without a page load, or someone reaches the page directly. It also counts refreshes. Tag the form submission itself as its own event, and treat the thank-you page as a backup signal rather than the record of the enquiry.

Why does my single-page site only record one page view?

Because the automatic page view event fires when a page loads, and on a single-page site or app the content changes without a new load. The visitor moves through several screens and GA4 sees one. The fix is to send a page view event yourself whenever the view changes, usually through Tag Manager listening for the site's own navigation signal.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.