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.
