I scoured the forums today looking for the procedure to implement Google Analytics on a 4.20 store and it has turned into the usual egg hunt and goat roping.....
Is there a clear cut procedure somewhere with no grey areas for doing this since it appears that simply slapping the code in the global footer may not be the best plan. ?
*******snip/edit looks like they take care of this part now
I saw in the forums posts about testing for login or not to avoid secure non secure warnings on checkout and all kinds of conditional coding.
Looking at the "new" code from google it appears the script is testing for secure or non secure page possibly, but then it also looks like they are overlooking canonical issues with the www
( i read javasript like a french menu)
per google:
The Google Analytics tracking code is now the same for both secure and non-secure websites. The new tracking code detects the protocol of the page being tracked and matches the security of your web page automatically. Pages with URLs beginning with http:// will download the non-secure version at http://www.google-analytics.com/ga.js and pages with URLs beginning with https:// will load the secure version at https://ssl.google-analytics.com/ga.js. No modification of the tracking code on secure pages is required.
Although the previous version of the tracking code (urchin.js) required you to copy/paste special tracking code into your secure pages, this is no longer necessary if you are tracking your site with ga.js. You can use the same tracking code on both secure (https://) and non-secure (http://) pages.
Is there a clear cut procedure somewhere with no grey areas for doing this since it appears that simply slapping the code in the global footer may not be the best plan. ?
*******snip/edit looks like they take care of this part now
I saw in the forums posts about testing for login or not to avoid secure non secure warnings on checkout and all kinds of conditional coding.
Looking at the "new" code from google it appears the script is testing for secure or non secure page possibly, but then it also looks like they are overlooking canonical issues with the www
( i read javasript like a french menu)per google:
The Google Analytics tracking code is now the same for both secure and non-secure websites. The new tracking code detects the protocol of the page being tracked and matches the security of your web page automatically. Pages with URLs beginning with http:// will download the non-secure version at http://www.google-analytics.com/ga.js and pages with URLs beginning with https:// will load the secure version at https://ssl.google-analytics.com/ga.js. No modification of the tracking code on secure pages is required.
Although the previous version of the tracking code (urchin.js) required you to copy/paste special tracking code into your secure pages, this is no longer necessary if you are tracking your site with ga.js. You can use the same tracking code on both secure (https://) and non-secure (http://) pages.
Comment