Tracking AMP Pages

Tracking a mobile site's traffic is key to understanding how users interact with the site and what can be done to increase visits and engagement by optimizing content and delivery.

Differentiating AMP sessions from the other sessions coming from a Marfeel Progressive WebApp (PWA) is also important.

At Marfeel, we use the same analytics systems and traffic is consolidated on the same accounts. 

How Google AMP audience is tracked

A publisher's Google AMP audience is tracked on any of the analytics vendors that are supported by AMP pages including:

  • Adobe Analytics
  • AFS Analytics
  • AT Internet
  • Burt
  • Chartbeat
  • ColAnalytics
  • Clicky Web Analytics
  • comScore
  • Cxense
  • Google Analytics
  • INFOnline / IVW
  • Krux
  • Linkpulse
  • Lotame
  • Médiamétrie
  • mParticle
  • OEWA
  • Parsely
  • Piano
  • Quantcast Measurement
  • Segment
  • SOASTA mPulse
  • SimpleReach
  • Snowplow Analytics
  • Webtrekk
  • Yandex Metrica.

Marfeel hosts the pages in the same way it hosts their mobile site. From an analytics perspective, if it's an AMP page, it doesn't really change anything; the attribution of the audience still goes to the publisher's analytics vendor.

Marfeel already has a segment created in Google Analytics: https://analytics.google.com/analytics/web/template?uid=2H9cF8xiR1-UzONlYMsPIQ and the variable is data-source: marfeel_amp.

We can also add tracking pixels that provide basic page view tracking.

For more information on AMP analytics, see the AMP project documentation