Google Ads Automatic Event Detection: What It Collects and How to Audit It

If one Google tag serves both GA4 and your Google Ads account, Google is now watching more of your website than it was at the start of the year. Scroll depth, outbound clicks, form starts, video progress and file downloads used to be GA4's territory through enhanced measurement. Since 4 February 2026 the same detections also feed Google Ads.

The change arrived in the Tag Manager release notes rather than a product announcement. Google's wording: "Google Ads will help advertisers measure more effectively and gain deeper insights with less manual configuration, by automatically collecting a broader range of event data from their websites. Advertisers may notice additional network requests to Google domains when these events are transmitted."

Nothing was added to your container. No tag was edited, no trigger changed, and no deploy happened on the client side. That is what makes it worth an hour of your time. A measurement change that ships itself into every account with a Google tag is also a compliance question, because those events now leave the browser for an advertising destination as well as an analytics property.

What actually changed

The Google tag has always been able to detect interactions by itself. Until this year, those detections were surfaced mainly in GA4, where they appear as enhanced measurement events. Google Ads received the conversions and remarketing signals it had been configured for, and not much else from the automatic layer.

The February release extends the automatic detection layer to Google Ads event collection. Google describes the result as broader event coverage without configuring every action on the site, and it gives one observable symptom: more network requests to Google domains as those events are transmitted.

You can confirm the shape of it without any Google-side access. Open the site in a clean browser profile, open DevTools, filter the network panel to the Google collection endpoints, then move through the page as a visitor would: scroll to the bottom, click an external link, start typing in a form, play an embedded video. The detections that fire tell you what this build actually sends, which no dashboard will show you.

The switch that controls all of it

The control lives in the Google tag settings, not in GTM and not in the Ads conversion screen. Google publishes four routes to the same panel:

• Google Ads: Tools icon, then Data Manager, then Manage under the Google tag heading.
• Google Analytics: Admin, then Data Streams, then click the stream.
• Google Tag Manager: the Google tags tab, then click the tag name.
• Campaign Manager 360: Data manager under Floodlight, then Manage under the Google tag section.

Inside, click Show all to reveal the full settings list and find "Manage automatic event detection". Google's description is short: "Select which types of events your Google tag should automatically detect for measurement in associated destinations. By default, all event types are turned on."

The settings table on that page marks the toggle as relevant to Google Analytics and Google Ads, and not used by Campaign Manager 360. So the same switch that governs the GA4 side of the tag also governs what Ads receives, which is the detail most teams have not noticed.

Seven event types, and one you cannot switch off

All types are enabled by default. Here is what each one detects, in Google's own terms:

• Page views: a page view event each time a page loads. Google states plainly that you cannot disable this event type.
• Page views on browser history change: a page view each time the site changes the browser history state, useful for single-page applications.
• Scrolls: a scroll event each time a visitor reaches the bottom of a page.
• Outbound clicks: a click event each time a visitor leaves your domain. Links to domains you configured for cross-domain measurement are excluded.
• Form interactions: an interaction or submission event each time a visitor touches a form on the site.
• Video engagement: play, progress and complete events for embedded videos, and by default for YouTube embeds with JS API support enabled.
• File downloads: a download event when a link with a common document, archive, application, video or audio extension is clicked.

The page views line is the one to read twice. There is no configuration in the Google tag that stops page views reaching a linked Ads account. Every other switch is optional. That one is not, which sets a floor under what the audit can achieve.

GA4 enhanced measurement is a separate switch

This is where most setups drift. GA4's own documentation on enhanced measurement events says it directly: "If you use the Google tag on your website, you also need to make sure that each event is enabled for automatic event detection for your Google tag. By default, all event types are enabled."

In practice that means switching off a measurement option inside GA4 stops GA4 collecting that event. It does not stop the Google tag detecting the interaction and passing it to other destinations that use the same tag. If a client asked you in 2023 to stop tracking scroll depth, and you turned it off in the data stream, that is no longer a complete answer.

The two lists are not identical either. The tag setting adds a dedicated switch for page views on browser history changes and carries no equivalent of GA4's site search option, which Google Analytics does list as an enhanced measurement event. A like-for-like mapping between the two panels does not exist.

Turning it off is a whole-tag decision

Google's note on the toggle matters more than the toggle itself: "If you turn off automatic event detection, no products or accounts that use this Google tag will receive associated data. You may want to consider turning off collection of these events in your destination instead."

One tag ID is often shared. A single Google tag can sit across a client's GA4 property, their own Ads account, a second Ads account run by another agency, and more than one domain. One switch, one decision, every destination. The same help page warns that changes made in these settings could affect other Google tags loaded on the same page.

That makes inventory the first step, not the last. Google documents containers carrying Google Ads and Floodlight tags loading a Google tag first before sending events, so a container can hold more than one tag even when nobody set one up deliberately.

What UK law says about the events now leaving the browser

The ICO's guidance on storage and access technologies, finalised on 29 April 2026, covers this without ambiguity: "The use of storage and access technologies for online advertising purposes requires consent."

Advertising measurement does not need its own consent dialog, because the ICO treats it as part of the advertising consent you already gather: "The measurement does not require a separate consent, as the collection of information for measuring the effectiveness of campaigns is intrinsically linked to the purpose of online advertising." What matters is that the consent you hold covers advertising, and that the information you give people is clear about it.

The exemption agencies ask about is the statistical purposes exception, and it is narrow. It covers storage for the sole purpose of collecting statistics about the use of your service, and it requires clear information plus "a simple means of objecting, free of charge". The ICO also states that no advertising purposes meet the strictly necessary exception. An event whose destination is Google Ads is doing advertising measurement, so the analytics exception does not carry it.

The transparency duty moved in February even though nothing appeared in the container. Form interactions and file downloads are a different kind of interaction from a page view, and a cookie policy written before those events could reach an ads destination does not describe them. The ICO's guidance asks what happens when your use of these technologies changes, and the answer is that the information you give people has to change with it.

Consent mode is the other half, and it is not the same control. The tag settings panel carries its own "Set consent mode override" and "Manage default consent settings" options for default signals and regional overrides. The event detection toggle does not touch either. It decides what the tag looks for, not whether the visitor agreed to it. Turning detection off is not a consent fix, and a working CMP is not a substitute for deciding what the tag detects.

A 30-minute audit you can run on any account

1. Inventory the tags. In GTM use the Google tags tab. In Google Ads use Tools, Data Manager, Manage. Write down every tag ID you find.
2. Map destinations and domains per tag. Ask the client's ads and analytics owners, because a tag shared with a former agency or a staging domain still counts.
3. Open Manage automatic event detection on each tag. Record the state of every switch and screenshot it with the date. That screenshot is your baseline for the next audit.
4. Decide event by event. Page views are fixed, so the decision applies to the other six. Tie each yes or no to how the event is actually used in reporting or bidding.
5. Test what fires before consent. Load the site in a clean profile, do not touch the banner, and watch requests to Google domains. Anything arriving before a choice is a finding to report.
6. Reconcile the documentation. Compare the cookie and privacy notices against what you just observed. If form interactions or downloads can be sent, the notice should name them.
7. Write the decision down. What is on, what is off, who approved it, and why. This is the record that answers an ICO query or a client security review without a scramble.

Leave it on, or turn it off

Leave detection enabled where a working CMP and consent mode are in place, a single Google tag covers owned domains, and the team genuinely uses interaction data in Ads reporting or bidding. Form starts and scroll depth are useful signals on a lead generation site when the consent chain is solid.

Narrow it where form interactions sit on top of sensitive input. A finance, health or legal site that collects special category data through forms is trading real risk for an event that rarely changes a bidding decision. The same goes for publishers with heavy outbound linking, and for accounts where the majority of visitors reject advertising consent, since the events arrive without much usable attribution value.

There is a middle path worth naming, because it is usually the honest recommendation. If nobody has looked at scroll or form events in Ads reporting since February, the collection is cost and exposure with no return, and turning one switch off is cheaper than defending it.

The short version

Google Ads has been collecting a broader set of automatically detected website events since 4 February 2026, and the only control is Manage automatic event detection inside the Google tag settings. It is enabled by default, page views cannot be turned off, and switching anything off affects every product and account that uses that tag.

The measurement upside is real on a compliant site. The compliance work is specific: inventory the tag, decide event by event, check what fires before consent, and update the documentation that describes it.