Skip to main content

​
Overview

People represent the end users in your system. A person is the individual you want to track, analyze, and associate with events. Every event should be tied to a person so you can understand usage, behavior, and outcomes at the user level.
While optional, we highly recommend sending person_id’s so you can analyze user behavior, personas, and search for specific users.

​
Creating a Person

A person ID is a unique identifier for each individual. This can be your internal user ID, an email address, or any other stable unique identifier from your system. The same person ID should always refer to the same individual.

​
Create a Person via SDK

You can explicitly create a person using the SDK by providing a unique person ID and optional metadata. If a person with the same ID already exists, the SDK will return the existing record instead of creating a duplicate.

​
Automatically create a Person when creating an Event

When creating an event, you can provide a person ID directly. If the person does not already exist, it will be created automatically. This allows you to avoid managing person creation separately.

​
Having Users of Users

In some systems, your direct customer may have their own end users. In this case, you can model each end user as a separate person while using metadata to associate them with a parent account, organization, or tenant. This allows you to track activity at both the individual and account level.