As AMP turns three, we can’t help but look back with nostalgia on how far along we’ve come along in our mission – Build the best open web technology that lets publishers create fast and secure pages without compromising on user-experience. That is why we built the analytics infrastructure in AMP that allows for “collect once, notify many” architecture for metrics on the page. This allows for AMP Analytics to be fast and accurate while using fewer resources on mobile devices.
AMP Analytics’ interface allows third-party analytics partners to easily integrate with the service. Websites building with AMP can choose from over 55 analytics providers today to get accurate metrics of the page.
We’re continuing to invest in the ecosystem, and wanted to give a shoutout to some of the amazing providers who also continue to invest in AMP. Over the coming few months, you’ll see deeper integrations from the following partners with AMP.
AMP continues to be adopted by Adobe customers, who love the speed that AMP provides and the mobile first approach. Adobe has supported AMP from the beginning with two different analytics templates that customers can use based on their needs. In 2019, Adobe would like to build out more robust ID linking capabilities as well as enhance the current templates to support more events out of the box to make the implementation even easier. For customers interested in implementing AMP they can reference implementation guide.
Bizible is currently in the process of building out their AMP integration. By next year, native event and pageview tracking will be available on AMP-enabled content. Additionally, AMP pageviews will be considered as touchpoints for attribution across the entire customer journey.
Chartbeat was one of the inaugural analytics partners for AMP and continues to provide active support and insight to publishers around AMP traffic. Their AMP integration, as well as their trends and best practices reports, illuminates a major source of traffic for publishers and enables them to understand how engagement compares across platforms. Chartbeat will continue to monitor AMP trends as well as broader platform shifts so they can shed light on the implications that major changes hold for publishers. For more questions about AMP capabilities or initiatives, please reach out at firstname.lastname@example.org.
Many websites use Google Analytics to better understand how well their site is meeting the needs of their users, and some sites also benefit from being able to measure campaign performance in Google Ads and Search Ads 360. Google Tag Manager offers a solution that allows websites to instrument AMP pages with analytics tags once and make subsequent updates without touching code. For those who are not using Google Tag Manager, the recently released global site tag for AMP provides the benefit of having a single implementation for Analytics, Google Ads, and Search Ads 360.
The New Relic Browser allows users to capture and visualize the performance of their AMP pages against their standard webpages. AMP data is captured and visualized through New Relic Insights, New Relic’s dashboard solution, to create detailed and customizable views into AMP page performance.
New Relic has plans to include AMP performance metrics into the New Relic Browser’s product in the first half of 2019. This will provide Browser customers with a clear way to compare AMP to non AMP page performance using New Relic Browser to measure if their investment in AMP is paying through page performance. For more information, please get in touch here.
Nielsen supports measurement of static/text content on AMP as part of Digital Content Ratings, which measures digital content consumption across platforms, in every market globally where the product is available. This enables publishers to get a holistic view of their audience across the variety of distribution channels they may use, as well as the unique reach they achieve on AMP. Nielsen currently supports DCR measurement on various online video platforms and plans to extend support for native amp-video in 2019. This would allow publishers to see audience composition on AMP by content type. For further information on Nielsen’s measurement capabilities, please click here.
Many publishers today use Optimizely to A/B test article headlines, ad viewability, and subscription flows. Optimizely is working with the AMP Project on a solution to support these same powerful experiments in AMP. This solution will allow customers to use Optimizely’s visual editor to build A/B tests and then see them take effect on AMP pages, along with measuring real-time experiment metrics through Optimizely’s Stats Engine.
Parse.ly fully supports measuring audiences on AMP, including the ability to support engaged time. With Parse.ly, content creators are able to see a single, unified view of their audience and content across multiple channels like AMP, mobile apps and website. Soon, Parse.ly will support better AMP breakdowns in their API, including newer standards like AMP Stories. They are committed to support audience measurement on AMP as the standard evolves. Please contact email@example.com if you have any questions.
Tealium is currently working on Tealium Collect AMP Analytics component. Tealium’s Hosted Data Layer (HDL) service recently added JSON support which means that you can leverage this for definition and delivery of AMP JSON. For questions, please go to Tealium’s Learning Community here.
As you can see from these updates, the AMP Analytics format and the number of providers supporting it continue to grow. As updates to the format become available and new providers come online, we will update the community.
Posted by Jeff Jose, Product Manager, AMP, at Google