How to set up Analytics on your AMP page

Original Post: http://feedproxy.google.com/~r/blogspot/tRaA/~3/dZo6fgXICeY/how-to-set-up-analytics-on-your-amp-page.html

In the digital world, whether you’re writing stories for your loyal readers, creating creative content that your fans love, helping the digital community, or providing items and services for your customer, understanding your audience is at the heart of it all. Key to unlocking that information is access to tools for measuring your audience and understanding their behavior. In addition to making your page load faster, Accelerated Mobile Pages (AMP) provides multiple analytics options without compromising on performance.

You can choose to use a solution like amp-pixel that behaves like a simple tracking pixel. It uses a single URL that allows variable substitutions, so it’s very customizable. See the amp-pixel documentation for more detail.

The amp-analytics component, on the other hand, is a powerful solution that recognizes many types of event triggers to help you collect specific metrics. Since amp-analytics is supported by multiple analytics providers, this means you can use 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 these analytics solution providers.

To use amp-analytics, include the component library in your document’s <head>:

<script async custom-element=“amp-analytics” src=“https://cdn.ampproject.org/v0/amp-analytics-0.1.js”></script>

And then include the component as follows (for these examples, make sure to specify your own account number instead of the placeholder):


<amp-analytics type=“googleanalytics”>
<script type=“application/json”>
{
 “vars”: {
   “account”: “UA-YYYY-Y”
 },
 “triggers”: {
   “defaultPageview”: {
     “on”: “visible”,
     “request”: “pageview”,
     “vars”: {
       “title”: “Name of the Article”
     }
   }
 }
}
</script>
</amp-analytics>

The JSON format is super flexible for describing several different types of events and it does not include any JavaScript code which could potentially lead to mistakes.

Expanding the above example, we can add another trigger, clickOnHeader:

<amp-analytics type=“googleanalytics”>
<script type=“application/json”>
{
 “vars”: {
   “account”: “UA-YYYY-Y”
 },
 “triggers”: {
   “defaultPageview”: {
     “on”: “visible”,
     “request”: “pageview”,
     “vars”: {
       “title”: “Name of the Article”
     }
   },
   “clickOnHeader”: {
     “on”: “click”,
     “selector”: “#header”,
     “request”: “event”,
     “vars”: {
       “eventCategory”: “examples”,
       “eventAction”: “clicked-header”
     }
   }
 }
}
</script>
</amp-analytics>

For a detailed description of data sets you can request, as well as the complete list of analytics providers supporting amp-analytics, check out the amp-analytics documentation. You can also see more implementation examples in the Amp By Example site.

If you want to conduct a user experience experiment on your AMP pages,  such as an A/B test, you can use the amp-experiment element. Any configurations done in this element will also be exposed to amp-analytics and amp-pixel, so you can easily do a statistical analysis of your experiment.

There are still plenty of ongoing developments for AMP analytics to help you gain insights as you AMPlify the user experience on your site. Visit the AMP Project roadmap to see a summary of what the team is cooking up. If you see some features missing, please file a request on GitHub.

Posted by Arudea Mahartianto, Google AMP Specialist

Leave a Reply

Your email address will not be published. Required fields are marked *