It's actually an internal website, so the admin hits can be important; I think.
I'm also looking to do some of my own tracking, for how tools are used, which will include what happens on the 'admin skin' pages.
For my interest in tracking WAY more info than I need to; I've never done tracking of information on users on the site, I, personally, don't know what is needed or what is worthless or where is best to track (or how), ect. So I expect the first few ittereations of my own tracking creation to be a huge bloated beast that eats my DB. Basically I'm a novice in this area, so I'm playing around with it.
The google thing was mostly my way of being clear of wanting to track stats and the module not being on the page.
The solution I came up with that I think I am going to be running with (still months out) is to create a user control loaded into the page, basically invisible, set to, or just 1px big, which launches a thread, looks for itself in the page controls, if it finds an instance of the same tracking control that is not itself, it terminates and tracks nothing. If the first tracking control is found that is itself, then it will track some data. That might be confusing, but I think it will work.
Much testing will figure out if it does or not.