Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So I always tell my clients to not create new Google accounts just for their site analytics, because Google tracks all kinds of shit in there.

But they don't get it. So when they inevitably give me that account, I go and delete and disable the search history.

But let me tell you. To disable the search history I first need to open that page, and I've seen a bunch of searches I honestly wish I wouldn't have.



Wait, you go and delete the search history from someone else's account? And it's your client? Wow. And then you complain about what you see when you're in there?


It's not creepy if you're the one doing it, apparently?


An account specifically created to host a site analytics group, and which clients always accidentally remain logged into.

I think I'll get above your cheap outrage and say I did the right thing by going in and disabling the search history.


I wouldn't go so far as to say outrage. Let's call it confusion. You advocate deleting the history to your clients, they don't do it, so you go ahead and do it anyway. And along the way, you get bothered by what you see when going into the history pages. If I were in your situation, I'd figure that maybe the client has an unstated reason for not wanting to delete the history and consider it none of my business.


I don't advocate deleting the history of my clients, do you have problem with reading comprehension?

The thing I "advocate" happens to be the best practice recommended by Google (if you'd care to dig into the docs, and no one does) for sharing the administration and viewing of Site Analytics groups (they're called Site Analytics "accounts" which are inside Google "accounts" so you can imagine that many folks get confused over what is what).

The best practice is not to create a new Google account and not to share that account's password with strangers (or even friends). There's a method for sharing just analytics with other Google Accounts, buried in the Site Analytics admin panel.

With that setup, the client will be creating a Site Analytics account within his personal Google account, and sharing said Site Analytics with my personal account. And I won't be able to see, let alone delete or disable their search history. Alas, that's not how things usually go.

People just don't get it, so they create new Google accounts over my head, share it with everyone, and everyone's search history ends up in the shared accounts. So when that accounts gets to me, I delete & disable search history. I know for a fact no one who ever logged into this shared account intended to share their browsing history with people.

Exacerbating the problem is the fact Google accounts are intentionally designed so that you log in and forget you're logged in. Google wants to know who you are. The accounts are also designed so that if you want a standalone account for analytics, it's a full-blown Google account, so you end up with people's search history in there (and a bunch of other services no one asked about, like email, docs etc.). And people don't understand the implications of sharing a Google account they've been logged into.

By the way, thanks for twisting my words and intent out of shape like you did. Now that I've had to waste the time to explain my original post as if to an imbecile, I'm sure everyone reading this will gain clarity about the situation I was describing. Cheers.


Your reasoning for not wanting the history saved makes perfect sense. It's making that decision for someone else's account that I don't really understand. Oh well, I guess we disagree, and you have the comfort of not being an imbecile. Cheers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: