Google Analytics collector-as-a-service (using GA measurement protocol).
The ga-beacon.appspot.com instance is a demo instance, good for prototyping and proof of concepts. If you intend to use this in production for your application, you should deploy your own instance of this service, which will allow you to scale the service up and down to meet your capacity needs, introspect the logs, customize the code, and so on.
Deploying your own instance is trivial: fork this repo, modify the project name in app.yaml, and follow the normal GAE deploy instructions. You should be up and running in less than five minutes.
First, log in to your Google Analytics account and set up a new property:
UA-XXXXX-XID on next page
Next, add a tracking image to the pages you want to track:
UA-XXXXX-Xshould be your tracking ID
insert/any/pathis an arbitrary path. For best results specify a meaningful and self-descriptive path. You have to do this manually, the beacon won't automatically record the page path it's embedded on.
Example tracker markup if you are using Markdown:
If you prefer, you can skip the badge and use a transparent pixel. To do so, simply append
?pixelto the image URL. There are also "flat" style variants available, which are available when appending
?flat-gifto the image URL. And that's it, add the tracker image to the pages you want to track and then head to your Google Analytics account to see real-time and aggregated visit analytics for your projects!
You may also auto-calculate the tracking path based in the "referer" information of the image. To activate this simple add
?useRefererto the image URL (or
&useRefererif you need to combine this with the
?flat-gifparameter). Although they are some odd browsers that don't always send the referer header, the amount of traffic coming from those browsers is usually not relevant at all. Of course that if you need to measure the traffic from those odd browsers you should not use this method.
How does this work? Google Analytics provides a measurement protocol which allows us to POST arbitrary visit data directly to Google servers, and that's exactly what GA Beacon does: we include an image request on our pages which hits the GA Beacon service, and GA Beacon POSTs the visit data to Google Analytics to record the visit. As a result, if you can embed an image, you can beacon data to Google Analytics.
Why do we need to proxy? Google Analytics supports reporting of visit data via GET requests, but unfortunately we can't use that directly because we need to generate and report a unique visitor ID for each hit - e.g. some pages do not allow us to run JS on the client to generate the ID. To address this, we proxy the request through ga-beacon.appspot.com, which in turn is responsible for generating the unique visitor ID (server generated UUID), setting the appropriate cookies for repeat hits, and reporting the hits to Google Analytics.
Do I have to use ga-beacon.appspot.com? You can if you want to - it's free, but there are no capacity or availability promises. For best results, deploy your own instance directly on Google App Engine: clone this repository, change the project name, and deploy your own instance - easy as that. The project is under MIT license.
Can I use this to track visits to my GitHub README and other GitHub-served content? No, you cannot - see https://github.com/igrigorik/ga-beacon/commit/6acd8627bb7be36f24f5516e9873c92719a50e55