> Google Analytics thrives on developers' laziness in my opinion.
It's almost never "developers" who are deciding to use GA; it's middle managers or marketing departments.
It's almost never "developers" who are deciding to use GA; it's middle managers or marketing departments.
So it's not hard to imagine marketing wanting it; presumably it provides them a lot of value that wouldn't be easy to recreate in-house.
That maybe no option...
GA is rather deep, with tons of integration and ways to slice and segment data.
Yeah, maybe in a few weeks you can get _something_ that'll give you something that'll make some manager not too unhappy. Seems like a terrible value prop for almost all companies since, unfortunately, approximately no one cares (or they run adblock anyways).
Not hard to track page hits, time on, time off, and arbitrary events.
EDIT:
Seriously? Folks, it's a table for analytics events, a few SQL queries to do basic reporting (at least in Postgres), a little bit of client-side JS to post the events, and a bit of server-side code to create the routes and maybe display the report page.
I guess if it doesn't include Kafka, Mesos, Kubermetes, Neo4j, and Docker, it isn't delivering business value.
ffs.
People are prematurely optimizing if they fear is "but but but mah datamoose".
Also, it's not prohibitively costly if you do even slight batching of the events, say batch load between every five minutes or an hour.
I'd love to hear somebody with war stories chime in though!
You're missing the point of why "rolling your own shitting [sic] implementation" is worth it: it's not the speed, it's the privacy.