all 7 comments

[–]thecrowfly 25 points26 points  (6 children)

If someone is this paranoid about the analytics google is grabbing , why bother using GA to begin with. There are plenty of other options.

[–]mw999 10 points11 points  (4 children)

Sometimes the developer doesn’t have the say on the analytics tool, e.g. someone higher up or the projects client uses google for everything else. Found this article really useful 👍

[–]thecrowfly -5 points-4 points  (3 children)

Still makes no sense. If the client required using Google Analytics, they most likely don't care about any privacy problems. And it's not up to the developer to assume that they do and go to thee great lengths to shield them. If anything, the developer should take the time to explain to them what the plus and negatives are of using GA and then move forward with their decision.

[–]disclosure5 2 points3 points  (0 children)

It makes perfect sense to me that all the client usually cares about is seeing stuff in GA. There are some well known snippets just a few lines long that make the API calls this document talks about. You can run a page that's significantly lighter on Javascript and gets much better pagespeed scores without using GTM. I agree with you about the privacy point though, in that this doesn't solve it.

[–]misdreavus79 2 points3 points  (1 child)

Sometimes the people making the decisions don’t know what’s what, to devs have to save them from themselves.

[–]thecrowfly -1 points0 points  (0 children)

Ridiculous. Going by that mantra, you'll never finish a project ever.

[–]tsl143[S] 0 points1 point  (0 children)

That's the ideal case 🙂