Track Events
The track API call is how you record any actions your leads or customers perform, along with any properties that describe the action.
Each action is known as a website event. Each website event has a name, like Registered, and properties, for example a Registered event might have properties like plan or accountType.
Here’s the payload of a typical track call:
deeploop.track("Registered", {
plan: "Pro Annual",
accountType: "Facebook"
});
| Field | Type | Description |
|---|---|---|
| event | String | Name of the action that a lead or customer has performed. |
| properties | Object (optional) | Free-form dictionary of properties of the event, like revenue |
Event
Every track call records a single user action. We call these “website events”. We 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.
To keep things simple, avoid using nondescript names like Event 12 or QVF. Instead, use unique but recognizable names like Video Recorded, Order Completed or Demo Requested.
Properties
Properties are extra pieces of information you can tie to events you track. They can be anything that will be useful while using the events later in the sales process. We recommend sending properties whenever possible because they give you a more complete picture of what your leads or customers are doing.
