That's an interesting thought, but makes sense and it's also shorter. We ought to specify the format and encoding in the tracker protocol specification. Would you already limit the type of content to be sent through the wire there or deal with that only when it's ETL time? The single `properties` argument looks and acts like it can take any JS object now and there's no *validation* that someone doesn't start sending up nested object.

(The original names were coming from the canonical event specification which was already available at the time. These shorter names of course make a lot more sense so I'm making these changes as we speak.)

Btw, this is also the reason I updated the example for `trackUnstructEvent` so that it is limited to certain field types.