Who owns the event taxonomy?

The doc is currently maintained by @name . He will be responsible for making sure the document is up-to-date and all data requests pass through here to the Engineering team. The rest of the team - across the org - have access to view and comment on this doc, but not to edit.

How we track data

We track our product data via Segment.com. Segment allows us to track our data once and send it to multiple tools via their platform. (Our Segment credentials are stored in 1Password. If you need access please request).

With Segment, we can make three main types of calls for our product data:

  1. Track call: The track call allows us to track events in the product. For each event, we can set a list of properties to describe the event.
  2. Identify call: Identify is how we identify users in the platform. We make this call everything a user signs up as well as every time the user logs in. We can assign User traits to a user with this call and therefore should make an identify call whenever we want to update the status of a user.
  3. Page call: The page call allows us to track all the pages visited by our users. For each event, we’ll be able to have the URL property of the viewed page.

Our naming conventions

Events naming

When naming our events, we follow the object-action naming convention. We will name the object being acted upon and then name the action. File Created, Signup Success, File Exported.

framework.png

We use Proper Case for event naming, capitalizing each word, eg: File Created

Property naming

For event properties and to better understand to which event they’re attached, we follow the name-type framework, meaning we name the event properties by a combination of the event name and the property type.

Eg: for the event File Exported, if we want to get information about the resolution of the exported file, we’ll have to look at the property called file_exported_resolution.

We use Snake Case for property naming, all words are in lower case and spaces are replaced by “_”, eg: pro_checkout_success_plan