Pros & Cons of Cookie Analytics

The current build has two modes of tracking:

  • Visible (Via user control & GIF request to Google Analytics server): The user control creates a standard html image request (with the necessary parameters) to the Google Analytics server. Output is a single transparent pixel. No client side javascript required.
  • Invisible (Via user control, Global.asax or HTTP Module): You can call the tracking methods from your Global.asax file (or the new HTTP Module) to perform invisible tracking of all page requests. Or add the user control to your templated pages with the invisible tracking option set. No client side javascript, or image requests required (See limitations below).

Highlights (at time of writing):

  • Report current visitor page activity
  • Report hits to pdf, zip & other file types – No need to manually add GA tracking push to each link
  • Report user agents
  • Report referrers
  • Report client locale (ie en-us / en-GB etc)
  • Report visitor location (Via user control only)
  • Block a single IP address from being tracked (set via web.config, suitable for website owners doing tests)
  • Prevent reporting of folder locations / files (set via web.config, suitable for blocking RSS feeds or Admin areas)
  • Support for Content Management Systems running MS SQL (Suitable for CMS with single table storing page ID and urls) – Now supports pass-thru of querystrings.
  • Very basic browser fingerprinting for use when Session variables are unavailable. This is only used to match file downloads to most likely visitor.
  • (NEW) Enable support of extensionless urls (Tested on Umbraco 5)
  • (NEW) Debug mode logs request URL in IIS site logs
  • (Updated) Spider / bot filtering (Requires monitoring)

Limitations

  • Geo-location of visitor is unavailable for invisible tracking. If you wish to know visitors approx location use visible mode via user control. This is due to GA only reporting via client IP for ga.js or utm.gif requests
  • As the ga.js file is not used, advanced features like site speed and “In Page Analytics” will not function.
  • This version requires classic Google Analytics properties, not the new Universal Analytics.