The .track call is used to send user event data to Sherlock. Once a user has been identified, you can begin tracking events, using:

sherlock.track("Login");

So long as you have the Sherlock library set up correctly in your top-level template, then you don't have to include a userID with any .track calls. The library will automatically assign and .track event to the identified user.

Recommended SaaS event tracking

Because every SaaS product is unique, most of the events you track will be unique to your product. However, there are some pretty standard SaaS events that you should be tracking. They include:

EVENT	DESCRIPTION
`Account created`	This is when a new account is created - a new signup, if you will. It is important for you to make and `.identity` and `.group` call at this time as well to record the proper traits.
`Login`	When any user logs into your product. This is a good event to capture to show when a user is active with the product.
`Viewed {dashboard}`	Often, products will not require users to log-in every time they want to use a product. In these cases, it’s a good idea to track the first page that a user “lands” on in the product as a stand-in for a traditional log-in event.
`Team member invited`	This is an important event to track when one of your users invites another user to the account. This event is assigned to the user who actually does the inviting.
`Team member signup`	This event tracks when a new user invited to an account actually accepts the invitation and creates his/her own user account.
`Account upgraded`	\| Track when user upgrades his/her account. You could break this into two or more events to track different types of upgrades as well. For example, `Account upgraded to paid` for a user who converts from trial to paid and `Account upgraded plan` for a user that moves from one paid account to a larger one. It is also important to record a `.group` call with this event in order to update the appropriate account traits.
`Account downgrade`	Same as above, but for downgrades. It is also important to record a `.group` call with this event in order to update the appropriate account traits.
`Account canceled`	A very important event to track. It is also important to record a `.group` call with this event in order to update the appropriate account traits.