Identify Users
The identify endpoint links user traits (such as email, name, plan, and company) to adistinct_id. Once identified, these traits appear alongside events in the Chippy Analytics dashboard, enabling segmentation and cohort analysis.
POST /api/v1/identify
Request Body
Example Request
Response
202 AcceptedError Responses
400 Bad Request: missing traits:Common Traits
You can send any key-value pairs as traits. The following are commonly used and have built-in support in the Chippy Analytics dashboard:Custom traits beyond this list are fully supported. Any key-value pair you send will be stored and available for filtering in the dashboard.
When to Call Identify
Call the identify endpoint at key moments in the user lifecycle to keep traits current:- On signup: set initial traits like
email,name,plan, andcreated_at. - On login: refresh traits in case they changed since the last session.
- When the user profile changes: update specific traits such as
planafter an upgrade, orcompanyafter an org change.
Example: Updating a single trait after a plan upgrade
Each identify call creates a special
$identify event internally. This means you can see exactly when user traits were set or updated in your event timeline.