identified
A visitor told the site who they are: a login, or an email typed into a form.
The SDK's identify() call becomes this. The address or number becomes an identifier and a claimed edge to the device, strength 20: anyone can type a stranger's address, so a claim attaches a new identifier to a person but never merges two existing people. A verified source (an order, a confirmed subscription, a clicked mail link) promotes it.
| Sent with | browser, server keys (see write keys) |
| Mode | strict: exactly the declared fields; an undeclared key, a wrong type or a missing required key quarantines the event |
| Version | 1 (_schema_version on the stored row) |
| State | active |
| Required fields | none |
| Revenue | none: the revenue block is refused |
| Identity evidence | device ↔ email, strength 20, claimeddevice ↔ phone, strength 20, claimed |
| Before consent | no |
Fields
The activity's own fields, sent as features. Identifier and attribute fields are moved out of features by the processor; see identifiers and attributes.
| Field | Type | Required | What happens to it | Meaning |
|---|---|---|---|---|
email | string | no | becomes the email identifier; it leaves features | An email address; it becomes an identifier and leaves features. |
phone | string | no | becomes the phone identifier; it leaves features | A phone number; it becomes an identifier and leaves features. |
Example
One activity in a batch to POST /v1/activities, with debug so the answer says what the processor made of it. The envelope page explains every top-level field.
{
"batch": [
{
"activity_id": "0192f1a4-9f88-7ac9-8000-9f88ac9b0000",
"activity": "identified",
"ts": "2026-10-17T20:00:00+02:00",
"anonymous_customer_id": "evx_web_8f21c0",
"features": {
"email": "ana@example.com",
"phone": "+31624681357"
}
}
],
"debug": true
}
Try it
Sends this request from your browser. The key and the endpoint are kept in this browser only.
Versions
| Version | Mode | Key classes | Change |
|---|---|---|---|
| 1 (current) | strict | browser, server | first version |
A published version never changes; a change is a new version, and every stored row says which version it was checked against.