Add user_id to your events and LogZuno builds a profile for each person: every event they sent, when they were first and last seen, and the properties you identify them with.
Use a stable ID
Use the ID your own database gives the user, not their email address. Emails change; IDs don't. Before someone signs in, the browser script gives them a random anonymous ID, so their pageviews still count as one visitor.
Send properties
POST /v1/identity sets properties on a user. Properties merge: sending plan again replaces the old plan and leaves the other properties alone.
curl -sS -X POST "${LOGZUNO_ENDPOINT:-https://api.logzuno.app/v1}/identity" \
-H "Authorization: Bearer $LOGZUNO_API_KEY" \
-H "Content-Type: application/json" \
-w "\nHTTP %{http_code}\n" \
-d '{
"user_id": "user-123",
"properties": { "name": "Ada Lovelace", "email": "[email protected]", "plan": "growth" }
}'| Field | Required | What it is |
|---|---|---|
user_id | Yes | Your ID for the user (userId works too) |
properties | No | A flat object, up to 200 keys (data works too) |
group_id | No | Adds the user to a group |
Identify calls don't count toward your monthly event allowance.
Built-in segments
The Users page has six segments built in, each over a period of 1, 7, 14 or 30 days:
| Segment | Who is in it |
|---|---|
| New sign-ups | First seen today, this week or this month |
| Active | Did something in the period (or, if you chose the project's active events, did one of those) |
| Engaged | Did something in the period, most events first |
| Recent | First seen within the period |
| Power | Active in the period and more than one event in total |
| Drifting | Last seen longer ago than the period |
Build your own from properties, computed properties, what people did or didn't do, and first and last seen. Segments can be saved and exported as CSV.