Post by account_disabled on Feb 22, 2024 5:54:45 GMT
The too. One of the reasons we did the handcoded version was to get handson experience with AMP coding. Were working on a better custom implementation of the AMP by Automatic pages in parallel. Bonus challenge AMP analytics Aside from the actual implementation of AMP there is a second major issue to be concerned about if you want to be successful the tracking. The default tracking in Google Analytics for AMP pages is broken and youll need to patch it. Just to explain what the issue is lets look at the following illustration The way AMP works and one of the things that helps with speeding up your web pages is that your content is served out of a cache on Google.
When a user clicks on the AMP link in the search results that America Mobile Number List page lives in GooglesThats the web page that gets sent to the user. The problem occurs when a user is viewing your web page on Googles cache and then clicks on a link within that page say to the home page of your site. This action means they leave the Google.com page and get the next page delivered from your server in the example above Im using the StoneTemple.com server. From a web analytics point of view those are two different websites.
The analytics for StoneTemple.com is going to view that person who clicked on the AMP page in the Google cache as a visitor from a thirdparty website and not a visitor from search. In other words the analytics for StoneTemple.com wont record it as a continuation of the same session itll be tracked as a new session. You can and should set up analytics for your AMP pages the ones running on Google.com but those are normally going to run as a separate set of analytics. Nearly every action on your pages in the Google cache will result in the user leaving the Google cache and that.
When a user clicks on the AMP link in the search results that America Mobile Number List page lives in GooglesThats the web page that gets sent to the user. The problem occurs when a user is viewing your web page on Googles cache and then clicks on a link within that page say to the home page of your site. This action means they leave the Google.com page and get the next page delivered from your server in the example above Im using the StoneTemple.com server. From a web analytics point of view those are two different websites.
The analytics for StoneTemple.com is going to view that person who clicked on the AMP page in the Google cache as a visitor from a thirdparty website and not a visitor from search. In other words the analytics for StoneTemple.com wont record it as a continuation of the same session itll be tracked as a new session. You can and should set up analytics for your AMP pages the ones running on Google.com but those are normally going to run as a separate set of analytics. Nearly every action on your pages in the Google cache will result in the user leaving the Google cache and that.