Skip to main content
POST
Track

Authorizations

auth_token
string
query
required

Body

application/json
identity
object

A valid JSON hash containing the keys id and email used to identify the user for which the event is being tracked. Both email and id must be less than 255 characters and email must be a valid email address.

event_name
string

The name of the event tracked. Must be less than 255 characters. Capitalized and lowercase letters and spaces and underscores will be treated the same by Vero's API. For example, Purchased Item, purchased item, and purchased_item will all be matched as one event in Vero's backend.

Example:

"Viewed product"

data
object

A valid JSON hash containing key value pairs that represent the custom user properties you want to track with the event. All keys are freeform and can be defined by you.

Example:
extras
object

A valid JSON hash containing key/value pairs that represent the reserved, Vero-specific created_at and source properties. Refer to the note on "deduplication" above.

Response

OK

status
integer<int32>
Example:

200

message
string
Example:

"Success."