entered_details

The buyer entered their details in the checkout: an email, a phone number, a name.

The step that makes an abandoned basket reachable. The email and phone become identifiers with role buyer and a claimed edge to the device (anyone can type an address); the name is an attribute observation at weight 20, a form's weight. Banner-exempt: it is an explicit action that carries its own identifier, so it is sent before analytics consent, without an anonymous id; whether the address may be mailed about the basket is the CRM's consent resolution, not ingest's.

Sent with	browser, server, platform 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 (buyer), strength 20, claimed device ↔ phone (buyer), strength 20, claimed
Before consent	yes: the browser SDK may send it before analytics consent, without an anonymous id

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 with role buyer; it leaves features	An email address; it becomes an identifier and leaves features.
first_name	string	no, may be null	becomes the first_name attribute observation (weight 20) on the buyer; it leaves features	The person's first name, as answered.
last_name	string	no, may be null	becomes the last_name attribute observation (weight 20) on the buyer; it leaves features	The person's last name, as answered.
locale	string	no, may be null	becomes the language attribute observation (weight 20) on the buyer; it leaves features	The language and region of the buyer's session, such as nl_NL.
order_id	string	no, may be null	stays in features	The order in the ticketing system, as its own id. The same value on every activity derived from one order, so they can be joined.
phone	string	no	becomes the phone identifier with role buyer; it leaves features	A phone number; it becomes an identifier and leaves features.
shop_id	string	no, may be null	stays in features	The shop the basket is in.

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-2047-7ef7-8000-2047ef7a0000",
      "activity": "entered_details",
      "ts": "2026-10-17T20:00:00+02:00",
      "anonymous_customer_id": "evx_web_8f21c0",
      "features": {
        "order_id": "1f2d3c4b-0000-4000-8000-000000000001",
        "shop_id": "shop_01M4XVBYC3FGXCPFRZEPGV20RZ",
        "email": "ana@example.com",
        "phone": "+31624681357",
        "first_name": "Ana",
        "last_name": "de Vries",
        "locale": "nl_NL"
      }
    }
  ],
  "debug": true
}

Try it

Sends this request from your browser. The key and the endpoint are kept in this browser only.

ServiceWrite key

POST /v1/activities{ "batch": [ { "activity_id": "0192f1a4-2047-7ef7-8000-2047ef7a0000", "activity": "entered_details", "ts": "2026-10-17T20:00:00+02:00", "anonymous_customer_id": "evx_web_8f21c0", "features": { "order_id": "1f2d3c4b-0000-4000-8000-000000000001", "shop_id": "shop_01M4XVBYC3FGXCPFRZEPGV20RZ", "email": "ana@example.com", "phone": "+31624681357", "first_name": "Ana", "last_name": "de Vries", "locale": "nl_NL" } } ], "debug": true }

Versions

Version	Mode	Key classes	Change
1 (current)	strict	browser, server, platform	first version

A published version never changes; a change is a new version, and every stored row says which version it was checked against.