Segment

We are currently tracking all route changes inside ember. This covers normal page views as well as ember's push-state URL changes. The five events in the story, https://www.pivotaltracker.com/story/show/80575808, are tracked server-side.

Questions:
- move all these analytics calls into one file? This would allow us to write one-liners in the rest of the code.
- any feedback on the event names? `event: 'Paper#updated (submitted=true)',`
- any other data you think we should be recording for any of these tracking calls?

We did not commit this, but we created segment projects for development, staging, and production. Google analytics segment adapters for each of these projects are not set up. Heap analytics segment adapters are set up for development and production but not staging.

— RW + DT
The braces here aren't necessary: `Analytics.track(user_id: current_user.email, event: 'Logout')`.

Is it a good idea that we use email as user ID?

What happens when a user can have multiple emails? I suppose we can use whatever the user designates as their default email.

What happens when a user changes their email? Will our analytics see them as a completely new user?

We're also potentially leaking sensitive information.

Is there a reason why `current_user.id` is a bad idea? Should we give each user a random unique ID for tracking purposes, maybe?