That’s right – tested this out and was able to have a site on my local VM that I made up a name for (dev.schroeder.local – not resolvable outside the VM itself) successfully work with Google Analytics tracking.
Official word from Google on this: http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55510
The important caveats are:
-
You must use the latest version of their tracking code.
- The latest version is the good async stuff, so this is a good move regardless.
-
The site must be accessed with a fully qualified domain name (FQDN).
- I tried to trick it using the _setDomainName method in the client API, but no dice.
- If your site does not support access via FQDN, you may need to:
- Add an alternate access mapping to the site in Central Admin
- Update DNS
- Redirect the partial name (http://intranet) to the FQDN (http://intranet.company.local)
- The URLRewrite Module may be able to help you do this: http://www.iis.net/download/URLRewrite
- Could also go low tech: Add some script to default page to redirect if document.location is NOT the FQDN (though pages accessed directly would obviously bypass this measure)
- Maybe move that script to the masterpage…
Very much helpful! Google Analytics is definitely a useful tool that intranets can use measuring how many visits/view an intranet has giving a hint if intranets are actually being used by the employees or not. Making an intranet exciting is one solution to get employees to check on the intranet daily. Here is how: http://www.simpplr.com/blogs/2015/10/exciting-intranet-is-it-possible/.
ReplyDelete