If you're particularly paranoid about security, you may want to avoid importing 3rd party JS files into pages displaying sensitive information... which means yo

If you're particularly paranoid about security, you may want to avoid importing 3rd party JS files into pages displaying sensitive information... which means you either have to manage your own analytics service entirely, or make server-side calls. Or, depending on the complexity of your webapp, you may have events you'd like to track that aren't known on the client side -- e.g., in your UI a user can invite someone else to link them by providing an email, and there's just one flow; on the server-side, this may trigger an invitation sent to an email address unknown to you, or to an existing user of your service unrelated to the active user, or to someone who is already linked (directly, 2nd-level, etc.) to the active user. This kind of thing can be important to capture, but the info is unavailable in the front end. Again from the security perspective -- in the example above, it may be important that you don't reveal to the active user whether the invitee is already in the system, because that could be sensitive information (imagine a journalist joining an drug addiction support forum, then inviting lots of politicians' email addresses to see if they're members...).