2/12/2016 12:25:56 PM
Google Analytics Measurement Capabilities Now Available for Accelerated Mobile Pages
Google Analytics,JavaScript,Batching Network Requests,Accelerated Mobile Pages
App Developer Magazine

Google Analytics Measurement Capabilities Now Available for Accelerated Mobile Pages

Stuart Parkerson Stuart Parkerson in HTML5 Friday, February 12, 2016

The Google Analytics team has released new Google Analytics measurement capabilities for Accelerated Mobile Pages (AMP) facilitating the ability to identify the best content and optimize user experiences.

The Accelerated Mobile Pages Project (AMP) is an open source initiative to help enable content to load instantaneously and provide a better web experience. AMP HTML pages are built to prioritize speed and the user experience. One way that AMP provides good page loading performance is by restricting the ability to add custom JavaScript to pages and instead relying on built-in, reusable components.

The Google Analytics team announcement coincides with the AMP team’s announcement of the launch of an analytics component that will enable measurement on AMP pages. 

Developers can us amp-analytics to configure multiple endpoints and data sets. AMP then manages all of the instrumentation to come up with the data specified and shares it with all of analytics providers. No matter how many analytics providers are configured, the AMP runtime will only ever do a single measurement to come up with a value. This improves performance by reducing duplication of effort, batching network requests, and streamlining code paths.

Analytics on AMP is handled by an open source, reusable component that the Google Analytics team helped build. The component can be configured with Google Analytics specific configuration parameters to record pageviews, events, and custom dimensions. 

That configuration works with a global event listener that automatically detects triggers like button presses. It removes the need to scatter custom JavaScript throughout page to detect actions that should trigger events and hits. Instead, web developers can define which actions should trigger hits within the configuration section and AMP do the rest.

(Editors Note: Check out our recent article of digital winners and losers for the Super Bowl to see just how critical web performance can be.)

Read more: http://analytics.blogspot.com/2016/01/announcing-g...