A couple of pointers on the naming: The event title doesn't need to say "Track Event" as all this module does is track events. And the label is an optional field to add more clarity if required. 
For example: ```analytics.event("Quit");``` is fine.
Or if you had two ways to quit, you could say: ```analytics.event("Quit" , {label: "Close Icon");``` and ```analytics.event("Quit" , {label: "Text Link");``` (that is a made up example to show how the label works).
@Pomax : it is useful to hardcode the values if these are likely to change (e.g. with localization). That way the usage of an interface element is aggregated across languages. But if they don't change often, the generic solution is fine too.

@admix : You can see examples of how we have named other events in this etherpad: https://etherpad.mozilla.org/webmaker-ga-events-naming-convention