Google Analytics Tracking *Without* GA Code on the Page

[JD_Toims]

Yup, that's right -- I checked a GA account today and a page I've been working on in a section of the site that's not even part of the main site [only for management] which is brand new and a recoding of the current HTML/CSS to make it more manageable is shown in GA visits.

That would be expected or at least not quite as WTF?! shocking if there were any Analytics or even JavaScript on the page -- There isn't a bit of either code on the page. It's all CSS and HTML that's being recoded to duplicate the current for look and feel in a more manageable way before any JavaScript function or tracking is added.

Anyone else seen anything like this before and if so is there any speculation on where they're getting the numbers from?

[JD_Toims]

I should add: I don't have the FoolBar installed, because I quit caring how much "Green Google Dust" it reported for a page years ago -- I also don't use Chrome, so those aren't the answer and for this page to show up in GA is definitely a bit of a head-scratcher.

[phranque]

have you tried using a request header checker or a network analyzer such as Wireshark?

[JD_Toims]

Headers shouldn't make a difference between my browser and the server, unless Google is "sniffing the Internet", because the page in question doesn't run through Google or have GA code presented in any way.

Also, unless Google is sniffing, packet delivery shouldn't matter either. It *should* be between my browser, the upstream connections and the site -- GA should have a thing to do with those requests, even if Google has an upstream [or even downstream] relay.

There is nothing that references GA on the page, so to have GA data for the page means Google's getting it from a source other than GA, which is actually a bit concerning, imo, since if I wanted GA to log/track stats or accesses to the page I would have put the GA code on the page itself, rather than omitting it.

[lucy24]

The obvious first guess is logs. Is there any possibility the server administrator flicked the wrong switch, so yoursite.com/logs/ (or whatever the URL would be) is publicly accessible?