Enhanced measurement lets you measure interactions with your content by enabling options in the Google Analytics interface. No code changes are required. When you enable these options for a web stream, your Google Analytics tag starts sending events right away.
Before turning on the enhanced measurement feature, be sure you understand each option and what data will be collected. You can also turn off specific measurement options. Per our terms, you must ensure that no personally-identifiable information is sent to Google when you collect the data described in the following table.
The following table explains which data is collected by each option.
These measurement options are currently in BETA, and may be adjusted.
|Measurement option||When events are triggered||Data collected from page elements|
|Page view||A page_view event is triggered each time the page loads or the browser history state is changed by the active site.
This event is collected automatically. You cannot turn off collection.
An advanced setting on this option controls whether the event will be sent based on browser history events. This measurement option listens for pushState, popState, and replaceState.
|The following information about the page is included as event parameters:
|Scrolls||A scroll event is triggered the first time a user reaches the bottom of each page (i.e. when a 90% vertical depth becomes visible).||No additional information is collected from page elements.|
|Outbound clicks||A click event is triggered each time a user clicks a link that leads away from the current domain.||The following information about the link element is included as event parameters with the click event:
|Site search||A view_search_results event is triggered each time a user performs a site search, indicated by the presence of a URL query parameter.
By default, the event will be triggered based on the presence of one of the following 5 parameters in the URL:
|Information from Page URL query parameters is included as event parameters: ‘search_term’ and optionally ‘q_<additional key="">’ (where <additional key=""> matches an additional query parameter you specify to be collected under advanced settings)|
|Video engagement||For embedded YouTube videos that have JS API support enabled, the following events are triggered:
||The following information about the video is included as event parameters with the video events:
|File downloads||A file_download event is triggered when a user clicks a link leading to a file (with a common file extension) of the following types:
||The following information about the link element is included as event parameters with the file_download event: