Skip to main content
The track API call is how you record any actions your users perform, along with any properties that describe the action. Each action is known as an event. Each event has a name, like User Registered, and properties. For example, a User Registered event might have properties like plan or accountType. Calling track in one of our connections is one of the first steps to getting started with Innkeepr. Here’s the payload of a typical track call with most common fields removed:
And here’s the corresponding JavaScript event that would generate the above payload:
Beyond the common fields, the track call has the following fields: Example Here’s a complete example of a track call:

​
Identities

The User ID is a unique identifier for the user performing the actions. Check out the User ID docs for more detail. The Anonymous ID can be any pseudo-unique identifier, for cases where you don’t know who the user is, but you still want to tie them to an event. Check out the Anonymous ID docs for more detail. Note: In our browser and mobile libraries a User ID is automatically added from the state stored by a previous identify call, so you do not need to add it yourself. They will also automatically handle Anonymous IDs under the covers.

​
Event names

Every track call records a single user action. We call these “events”, and recommend that you make your event names human-readable, so that everyone on your team (even you, after all that caffeine) can know what they mean instantly. Don’t use nondescript names like Event 12 or TMDropd. Instead, use unique but recognizable names like Video Recorded and Order Completed. Innkeepr has standardized a series of reserved event names that have special semantic meaning. We map these events to tools that support them whenever possible. See the Semantic Events docs for more detail.

​
Properties

Properties are extra pieces of information you can tie to events you track. They can be anything that will be useful while analyzing the events later. We recommend sending properties whenever possible because they give you a more complete picture of what your users are doing. Innkeepr has reserved some properties that have semantic meanings, and handle them in special ways. For example, we always expect revenue to be a euro amount that we send to tools that handle revenue tracking. You should only use reserved properties for their intended meaning. The following are all of the reserved properties Innkeepr has standardized that apply to all events. Check out the Semantic Events docs for properties specific to individual reserved events.