Skip to main content
Track
curl --request POST \
  --url 'https://api.getvero.com/api/v2/events/track?auth_token=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "identity": {
    "id": 1000,
    "email": "test@example.com"
  },
  "event_name": "Viewed product",
  "data": {
    "product_name": "Red T-shirt",
    "product_url": "http://www.yourdomain.com/products/red-t-shirt"
  },
  "extras": {
    "source": "Segment.com",
    "created_at": "2023-05-30T04:46:31+0000"
  }
}
'
{
  "status": 200,
  "message": "Success."
}
Deduplication: We will automatically deduplicate events that are sent to our API with the same event_name, the same properties and that are tracked against the same user id within a three minute window. This is designed to solve issues related to Javascript event handling and retries. You can force Vero to ignore deduplication and track every event by including a property within data with a unique timestamp. This will ensure the event is not seen by the Vero system as a duplicate due to the unique data.

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:
{
  "product_name": "Red T-shirt",
  "product_url": "http://www.yourdomain.com/products/red-t-shirt"
}
​
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."