Hacker News Reader

Comment by zvrba | Hacker News Reader

I was seriously considering to make a browser plugin which would scrape pages for Google Analytics unique IDs, make a local database of them and randomly mix them up. Like this:

  0. [page visited]
  1. Does the page contain GA tracking ID?
    no: do nothing
    yes: add it to the database and replace it with another randomly chosen ID from the database

View on HN

Haha thats great. You definatly should. Hell i think i juat found a project to screw around with this weekend!

Wouldn't referral headers give this away? Unless you change those too of course.

You seem to have more clue about web development than I do (my only experience with web are Perl/CGI scripts of early 2000s).

Can you describe in more detail how google could detect that the GA identifier has been swapped and how to prevent detection?

I'm by no means an expert, but usually when a web browser makes a request for a resource it includes a referral header which tells the server where it came from. This header is probably sent both to the initial javascript request and to the tracking pixels it requests to send new info to Google. At a first glance I feel like if you change the tracking id, and the referrals, you may have some success messing with their system.

But again, not an expert and I could easily be missing something crucial.

Too late to edit now, but also I would not be suprised if the javascript they use records the url that is visited and reports that back as well.

Would pay for that.

Please do this!

IDs are tightly coupled with domains, no?

I wonder if Google would get them banned if this happened.

Reply on news.ycombinator.com