AMP is an open-source initiative to improve the mobile web experience by allowing web pages to load instantly on mobile devices.
In order to track your AMP articles please implement the following script on every AMP page:
<amp-analytics config="https://1e32b3109a3889d6eb04-114932bc2bae9698d2e445432680b599.ssl.cf1.rackcdn.com/amp.json">
<script type="application/json">
{
"vars": {
"id": "ID",
"postid": "POSTID"
}
}
</script>
</amp-analytics>
id parameter has a fixed value for a single domain. If the Insights tracking script is already implemented, you can get it from the console by typing _ain.id on any article page.
postid must match _ain.postid value from the desktop version of an article.
These two parameters are required so the Insights component could attribute the traffic to the corresponding article on the regular website.
If for some reason there are only AMP articles, without their website pair, you should also specify additional parameters, as you would do for the regular JavaScript tracker.
Then the example from above should look somewhat similar to this:
<amp-analytics config="https://1e32b3109a3889d6eb04-114932bc2bae9698d2e445432680b599.ssl.cf1.rackcdn.com/amp.json">
<script type="application/json">
{
"vars": {
"id": "1234",
"postid": "article-5678",
"title": "Article Title",
"pubdate": "YYYY-MM-DDTHH:MM:SS",
"authors": "Author 1, Author 2"
"sections": "Section>Subsection",
"tags": "tag1,tag2,tag3"
}
}
</script>
</amp-analytics>
Once AMP tracking has been implemented, you will be able to see google-amp as a new referrer.
AMP referrer URLs will show various sources of AMP traffic.
Notes:
At the moment AMP data is excluded from the Engagement and Loyalty CPIs, in order to prevent a significant impact of AMP traffic on those components.
It is possible to implement AMP tracking through the Google Tag Manager (GTM) if you have a dedicated AMP container set for this purpose. We kindly encourage you to contact our Support team and they can set the required tags, triggers, and variables for you in the short term.
After successful implementation, you will be able to see the results in the Insights dashboard, by filtering the traffic from the channel called Accelerated Mobile Pages.