placed_basket

The buyer placed the basket: the shop created the order and sends the browser to the payment. Replaces started_order.

Sent just before the payment redirect, the last moment this browser is certain to be the one that placed the order. It links the device to the order id; it is an association, not identity evidence. Banner-exempt, because the order has its own lawful basis. The completed_order from the ticketing system follows when the payment reaches paid, with the same order_id.

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	order_id
Revenue	none: the revenue block is refused
Identity evidence	none
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
event_ids	array of string	no	stays in features	The events the order's tickets are for; an order can span events, so completed_order itself has no _event_id.
order_id	string	yes	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.
payment_method	string	no, may be null	stays in features	How the order was paid, in the payment provider's terms (ideal, creditcard, …).
shop_id	string	no, may be null	stays in features	The shop the basket is in.
source_system	string	no, may be null	stays in features	The system the order is being made in, when the shop is not Eventix's own.

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-dc80-7200-8000-dc8020080000",
      "activity": "placed_basket",
      "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",
        "event_ids": [
          "3a114ef5-6105-48fd-aafc-0ae609d0536c"
        ],
        "payment_method": "ideal",
        "source_system": null
      }
    }
  ],
  "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-dc80-7200-8000-dc8020080000", "activity": "placed_basket", "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", "event_ids": [ "3a114ef5-6105-48fd-aafc-0ae609d0536c" ], "payment_method": "ideal", "source_system": null } } ], "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.