Where should I put the Google Analytics asynchronous snippet?

The snippet must be on the page itself If the snippet is in an external JS file, the browser will cache the file and the snippet would generate hit only the first loaded page from your site There are more delicated ways to call the snippet API from Javascript if needed - these are mainly used for track special events, like button presses, etc.

The snippet must be on the page itself. If the snippet is in an external JS file, the browser will cache the file and the snippet would generate hit only the first loaded page from your site. There are more delicated ways to call the snippet API from Javascript if needed - these are mainly used for track special events, like button presses, etc.

Thanks Mikko. I am just getting started with Google Analytics, so I appreciate the tip! – cf_PhillipSenn Sep 26 at 1:56 -1.

This is not correct. – yahelc Sep 26 at 3:21 Yahelch is correct. I was mixing with old synchronous script.

However, I cannot delete my own answer as it is currently accepted. – Mikko Ohtamaa Sep 26 at 17:14.

The snippet can be loaded in any way. If you want to include it in an external file, knock yourself out. Google recommends putting it in the to maximize the number of pageviews that get tracked, but you could just as easily load it in the without trouble, or from an external JavaScript file, or even a dynamically injected JavaScript file.

All that needs to happen is that the snippet needs to execute; ga. Js takes care of the rest. Even if your browser caches the code itself, it will still execute ga.

Js (which itself may be cached), but the data it sends to Google Analytics is very heavily cache busted. There's no way your browser could cache that request, even in the strictest of proxy environments. The way your analytics data gets "sent" to Google Analytics is that ga.

Js, after gathering all of the analytics data from the environment, your configurations and the cookies it sets, concatenates all of those values onto a query string on a dynamic image request (requested via JavaScript and never actually injected into the DOM. ) Those requests feature cache-busting parameters, as well as data that is generally unique to each request. Further, the image that is requested specifically instructs the browser to avoid caching it by setting these headers: Cache-Control:private, no-cache, no-cache=Set-Cookie, proxy-revalidate Expires:Wed, 19 Apr 2000 11:43:00 GMT Pragma:no-cache.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.