Use the API to retrieve user IDs associated with AMP-page activity and consolidate those with your own representations of those same users on your non-AMP pages. The consolidated information provides a more accurate picture of user journeys and use of your service.<\/p>\n
The API automatically sets the ID and expiration of the ID for each publisher. End users can opt out for individual publishers.<\/p>\n
Setup:<\/h3>\n1. AMP<\/h4>\n
In AMP options Panel, select Google Analytics as the Analytics Type.<\/p>\n
If you are using GTM then enable the GTM support and add ‘googleanalytics’ as\u00a0Analytics Type from AMP options Panel.<\/p>\n
2. NON-AMP<\/h4>\nIf you use Google Tag Manager<\/strong><\/h5>\nThe following steps should be completed on your existing published tag container(s).<\/p>\n
\n- Navigate to\u00a0Tag Configuration > Fields to Set<\/strong>.<\/li>\n
- Set\u00a0
useAmpClientId<\/code>\u00a0to\u00a0true<\/strong>.<\/li>\n- Save the new tag configuration.<\/li>\n
- Submit the tag.<\/li>\n
- Publish the container.<\/li>\n<\/ol>\n
If you use analytics.js<\/h5>\n
Include the following in your Analytics tracking code:<\/p>\n
ga('create', 'UA-XXXXX-Y', 'auto', {'useAmpClientId': true});<\/code><\/p>\nResources:<\/p>\n
Session Stitching, the Advanced Class<\/h3>\n
The above outline to address session stitching should allow you to capture all of your users, but it does leave some issues. What it\u2019s doing is taking data from two different sources and tie them together with a Client ID. At this point, you\u2019ll be abe to see what\u2019s coming through AMP pages vs. regular pages. There are still some shortcomings:<\/p>\n
\n- You can\u2019t see the difference between your own hosted AMP pages vs. Google CDN hosted pages.<\/li>\n
- If you segment to determine transaction sources, the AMP pages will show as a web data source with zero sessions and some transactions.<\/li>\n<\/ul>\n
The following steps will help address those issue.<\/p>\n
1. The first additional step is to make sure that \u2018ampproject.org\u2019 is added into the Referral Exclusion List under the Property Settings in the Admin section of the Google Analytics account. This should remove a majority of self-referrals from the CDN: This does not remove the records in GA. It removes the referral (source\/medium) over-ride from the user moving from CDN to site on 2nd click. Therefore, if the traffic hits the CDN via google\/cpc or google\/organic it remains as that for the cross-Data Source navigation \u2026 rather than being over-ridden by the Referral from the CDN.<\/p>\n
![\"exclude-ampproject-org\"](\"https:\/\/ampforwp.com\/tutorials\/wp-content\/uploads\/2017\/11\/exclude-ampproject-org.jpg\")
<\/a><\/p>\nThis referral exclusion will help e-commerce (and other) sites maintain tracking of a user session from initial entry on an AMP page in the CDN all the way through to checkout.<\/p>\n
2. Google also recommends that you add all subdomains of ampproject.org to your referral exclusion list as well. This step only applies if you\u2019ve got subdomains on your site (or that are being used as PPC landing pages) that are coded in AMP. If the site does not have a need to specifically track\/over-ride the referral currently when navigating between CDN and site then excluding \u2018ampproject.org\u2019 Referral covers any override from the CDN well enough. Google recommends excluding each subdomain but if you have a large number of subdomains in your setup, this may not be practical.<\/p>\n
3. Create a Hit-level custom dimension called \u201cAMPDOC_HOST\u201d in the Google Analytics property: This enables you to segment traffic that started in CDN versus AMP hosted page.<\/p>\n
![\"\"](\"https:\/\/ampforwp.com\/tutorials\/wp-content\/uploads\/2017\/11\/amp-doc-host.jpg\")
<\/a><\/p>\n4. Set the pageview in Google Tag Manager for the AMP Container to include the custom dimension set the \u201cDimension Value\u201d to \u201cAMPDOC_HOST\u201d:<\/p>\n
![\"amp-doc-host-page-tag\"](\"https:\/\/ampforwp.com\/tutorials\/wp-content\/uploads\/2017\/11\/amp-doc-host-page-tag.jpg\")
<\/a><\/p>\nNote: \u201cAMPDOC_HOST\u201d does not need to be defined as a variable in the variable settings. The value can be set just like it is in the above screenshot.<\/p>\n
5. You are then able to view pages served up in the CDN vs AMP pages in the content reports. To view landing pages served up by the CDN, filter by \u201ccdn\u201d by landing page:<\/p>\n
![\"filter-on-cdn-landing-pages\"](\"https:\/\/ampforwp.com\/tutorials\/wp-content\/uploads\/2017\/11\/filter-on-cdn-landing-pages.jpg\")
<\/a><\/p>\n6. Then, finally, exclude \u201ccdn\u201d and include \u201camp\u201d in the filter to view AMP landing pages:<\/p>\n
![\"final-amp-filtering-setup\"](\"https:\/\/ampforwp.com\/tutorials\/wp-content\/uploads\/2017\/11\/final-amp-filtering-setup.jpg\")
<\/a><\/p>\nFinal Notes on Session Stitching<\/h3>\n
Support for AMP by other analytics providers remains a work in progress for most. A Google spokesperson told me that the above outlined solution is available to third party analytics platforms, but that \u201cthe best place for info is still the Google Analytics solution, since the AMP team is still working on getting documentation up for other 3rd parties.\u201d<\/p>\n
Resources<\/h3>\n
https:\/\/www.stonetemple.com\/amp-tech-guide\/<\/a><\/p>\nhttps:\/\/developers.google.com\/analytics\/devguides\/collection\/amp-analytics\/client-id<\/a><\/p>\nhttps:\/\/support.google.com\/analytics\/answer\/7486764<\/a><\/p>\n
The following steps should be completed on your existing published tag container(s).<\/p>\n
- \n
- Navigate to\u00a0Tag Configuration > Fields to Set<\/strong>.<\/li>\n
- Set\u00a0
useAmpClientId<\/code>\u00a0to\u00a0true<\/strong>.<\/li>\n- Save the new tag configuration.<\/li>\n
- Submit the tag.<\/li>\n
- Publish the container.<\/li>\n<\/ol>\n
If you use analytics.js<\/h5>\n
Include the following in your Analytics tracking code:<\/p>\n
ga('create', 'UA-XXXXX-Y', 'auto', {'useAmpClientId': true});<\/code><\/p>\nResources:<\/p>\n
Session Stitching, the Advanced Class<\/h3>\n
The above outline to address session stitching should allow you to capture all of your users, but it does leave some issues. What it\u2019s doing is taking data from two different sources and tie them together with a Client ID. At this point, you\u2019ll be abe to see what\u2019s coming through AMP pages vs. regular pages. There are still some shortcomings:<\/p>\n
- \n
- You can\u2019t see the difference between your own hosted AMP pages vs. Google CDN hosted pages.<\/li>\n
- If you segment to determine transaction sources, the AMP pages will show as a web data source with zero sessions and some transactions.<\/li>\n<\/ul>\n
The following steps will help address those issue.<\/p>\n
1. The first additional step is to make sure that \u2018ampproject.org\u2019 is added into the Referral Exclusion List under the Property Settings in the Admin section of the Google Analytics account. This should remove a majority of self-referrals from the CDN: This does not remove the records in GA. It removes the referral (source\/medium) over-ride from the user moving from CDN to site on 2nd click. Therefore, if the traffic hits the CDN via google\/cpc or google\/organic it remains as that for the cross-Data Source navigation \u2026 rather than being over-ridden by the Referral from the CDN.<\/p>\n
<\/a><\/p>\nThis referral exclusion will help e-commerce (and other) sites maintain tracking of a user session from initial entry on an AMP page in the CDN all the way through to checkout.<\/p>\n
2. Google also recommends that you add all subdomains of ampproject.org to your referral exclusion list as well. This step only applies if you\u2019ve got subdomains on your site (or that are being used as PPC landing pages) that are coded in AMP. If the site does not have a need to specifically track\/over-ride the referral currently when navigating between CDN and site then excluding \u2018ampproject.org\u2019 Referral covers any override from the CDN well enough. Google recommends excluding each subdomain but if you have a large number of subdomains in your setup, this may not be practical.<\/p>\n
3. Create a Hit-level custom dimension called \u201cAMPDOC_HOST\u201d in the Google Analytics property: This enables you to segment traffic that started in CDN versus AMP hosted page.<\/p>\n
<\/a><\/p>\n4. Set the pageview in Google Tag Manager for the AMP Container to include the custom dimension set the \u201cDimension Value\u201d to \u201cAMPDOC_HOST\u201d:<\/p>\n
<\/a><\/p>\nNote: \u201cAMPDOC_HOST\u201d does not need to be defined as a variable in the variable settings. The value can be set just like it is in the above screenshot.<\/p>\n
5. You are then able to view pages served up in the CDN vs AMP pages in the content reports. To view landing pages served up by the CDN, filter by \u201ccdn\u201d by landing page:<\/p>\n
<\/a><\/p>\n6. Then, finally, exclude \u201ccdn\u201d and include \u201camp\u201d in the filter to view AMP landing pages:<\/p>\n
<\/a><\/p>\nFinal Notes on Session Stitching<\/h3>\n
Support for AMP by other analytics providers remains a work in progress for most. A Google spokesperson told me that the above outlined solution is available to third party analytics platforms, but that \u201cthe best place for info is still the Google Analytics solution, since the AMP team is still working on getting documentation up for other 3rd parties.\u201d<\/p>\n
Resources<\/h3>\n
https:\/\/www.stonetemple.com\/amp-tech-guide\/<\/a><\/p>\n
https:\/\/developers.google.com\/analytics\/devguides\/collection\/amp-analytics\/client-id<\/a><\/p>\n
https:\/\/support.google.com\/analytics\/answer\/7486764<\/a><\/p>\n
- Set\u00a0