Menu
We have an ajaxy sort of html based app framework thing and want google analytics to work with it. And I believe we have set things up properly to manually call _trackPageview where needed.
However things don't seem to be getting reported. Now either I don't have it working right, or GA tracking from javascript with a file:// protocol on the url silently violates some cross domain policy I'm not aware of.
So does GA work with local html via file://? Or is there something wrong with my GA usage?
Note that the domain we are using doesn't actually exist. We want to use something like the mobile app tracking but from JavaScript rather than a native library. And in order to do this, it looks you setup a fake domain, and tell the tracker what domain it should be reporting as.
At the end of my <head>:
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-XXXACCOUNTID-XX']);
_gaq.push(['_setDomainName', 'myfake.domain.com']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = 'http://www.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
And in our JS framework we call:
_gaq.push(['_trackPageview', '/some/path/here']);
917
Once the plugin is installed, PDF downloads will be tracked as events in your Google Analytics dashboard. The good news with some of these plugins is that you don't need to do any more work than download and install it. They'll do all the hard work to ensure you can track each and every download in Google Analytics.
utm_source : Identify the advertiser, site, publication, etc. that is sending traffic to your property, for example: google, newsletter4, billboard. utm_medium : The advertising or marketing medium, for example: cpc, banner, email newsletter. utm_campaign : The individual campaign name, slogan, promo code, etc.
Google now supports disabling the protocol check task by setting it to null, allowing you to track analytics from a file:// url:
ga('create', 'UA-XXXXX-Y', 'auto');
ga('set', 'checkProtocolTask', null); // Disable file protocol checking.
ga('set', 'checkStorageTask', null); // Disable cookie storage checking.
ga('set', 'historyImportTask', null); // Disable history checking (requires reading from cookies).
ga('send', 'pageview');
A couple of tweaks are necessary:
Cookies cannot be used as there's no domain in action, so we need to prevent GA from trying to use them.
This is done by setting 'storage': 'none' in creation config (documentation).
By default, GA aborts if the protocol (in our case file) is not http or https.
Disable this check using the corresponding task: ga('set', 'checkProtocolTask', null)
Since there is no domain, GA fails to derive a path denoting the active page.
It can be configured manually by using the page URL modification feature: ga('set', 'page', 'foobar')
A subsequent ga('send', 'pageview') will then show up in data as a visit on /foobar.
With cookies disabled, users are not tracked across page loads, so each refresh will trigger detection of another unique visitor.
However, we can provide custom client ids on create by setting 'clientId': localStorage.getItem(someKey), which looks for previously stored client ids.
Storing ids is done by
ga(function(tracker) {
localStorage.setItem(someKey, tracker.get('clientId'));
})
Combining all above steps, we end up with something like the following:
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-XXXXXXXX-Y', {
'storage': 'none',
'clientId': localStorage.getItem('ga:clientId')
});
ga(function(tracker) {
localStorage.setItem('ga:clientId', tracker.get('clientId'));
});
ga('set', 'checkProtocolTask', null);
ga('set', 'page', 'myPage');
ga('send', 'pageview');
OK, I think I have this one solved. It's been dogging me for a few days.
According to Google Analytics Help Center,
Visitors must have JavaScript, images, and cookies enabled in their browsers in order for Analytics to report their visit.
Here's my theory: In my tests on Mac OS X Snow Leopard, documents run from file:// are not able to set cookies. This is because cookies are proprietary to HTTP, and when you run something from file://, you're not using the HTTP protocol.
Since you're not able to set cookies, ga.js refuses to send the _utm.gif request to Google's servers. No cookies get set; no request is sent to google, so nothing is logged in GA.
Solution: Use a development environment where you can set your domain as http://localhost (something like MAMP, if you're on a Mac and need a LAMP stack)
(Weird footnote: I observed some weird behavior where the GA cookies would set as third-party cookies of the domain of an unrelated imported script from a third party non-CDN domain. This could be because since the server sends HTTP cookies with the file, ga.js is attaching itself to that domain. However, this won't serve as a backdoor, since it still won't send the _utm.gif hit to Google's servers ).
========
EDIT:
You could try one of the various work arounds people have created for cookie-less GA tracking.
You might get some success out of this tool: http://code.google.com/p/google-analytics-js/downloads/list, explained here: http://remysharp.com/2009/02/27/analytics-for-bookmarklets-injected-scripts/
Instead of all of that GA code, you would include the script, and then call it using the following code:
gaTrack('UA-XXXACCOUNTID-XX', 'myfake.domain.com', '/some/path/here');
Its designed for bookmarklet/injected script tracking, but if I put in a file:// type setup, its able to successfully send the __utm.gif hit, meaning it SHOULD track successfully in GA.
The drawback is that cookieless means that it won't be able to track visits accurately, just page-view level data.
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
