Hacker News new | ask | show | jobs
by tixocloud 3769 days ago
The best practice is to identify which key metrics are the most meaningful for your business goals. Without knowing where you're headed, it's difficult to know what to measure.

Then figure out what's the cost of tracking everything? Does it affect UX? Does it affect your storage capacity? Do you have an analytical team that can work with all that data?

In theory, great idea to track everything (personally I would too). But it may save you more time just to focus on the ones that matter instead of ones that don't.

1 comments

Yeah I agree with specifying which are more meaningful for the app/product. For my larger team we've done just that but the GA specialist is pretty gung-ho about tracking everything -- the cost is developer time and effort -- and for me, working with the analytics team to decipher the output from tracking it all -- a lot of event tags (descriptors) to keep in your head!
Exactly! Ran into same issue taking a long time trying to parse the output of everything. If tracking and storing everything doesn't add significant cost, I'd do just that but come analysis, I'd only limit it to a few unless there's something that you need to dig deep when problems arise.