The doc is owned and maintained by the Product team. They 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.
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 and API key is stored in Lastpass. If you need access please request from someone on the Product team).
With Segment, we can make three main types of calls for our product data:
When naming our events, we follow a OBJECT-ACTION naming convention. This means our event names take a NOUN-VERB format. We will name the object being acted upon, and then name the action.
Team member invited,
Email deleted, etc.
We don't have a standard naming convention for traits and/or properties, but we do use snake case for them (ie -
As mentioned earlier, this doc serves two purposes:
The columns on the table provides important information about each piece of data. Some additional explanation on each property/column:
When looking for a specific event or to answer a specific question, there are a few ways this table makes thing easy.