Update an event (does not work — do not use)
Do not use this endpoint. It does not update anything.
Despite the name and the PUT verb, it creates a new event, so calling it duplicates the conversion instead of editing it.
Recorded events cannot currently be edited. It is documented only so that nobody discovers it in the spec and assumes otherwise.
Authorization
ClientBearer Client-scoped key as a Bearer JWT; always pinned to your own client.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X PUT "https://example.com/tracking/events" \ -H "Content-Type: application/json" \ -d '{ "coupon": null }'{ "message": "Event recorded", "recorded": true}List your events GET
Every event recorded on your account, as a flat array. This endpoint takes **no parameters** — there is no filtering, ordering or paging, and anything you send is ignored. Filter on your side, and expect the response to grow with your account.
List your conversions GET
The conversions on your account. This is the read-back of what you record through [the events endpoint](/docs/api-reference/tracking/createtrackingevent). Filter by a `from`/`to` time range, `metricIds` or `type`, and page with `limit` and `skip`.