Create an event

POST/analytics/{connection_id}/event

Parameters

fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection

Payload

idstring
created_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
event_type enum
Valid values:
"PAGE_VIEW"
"SCREEN_VIEW"
"CLICK"
"FORM_SUBMIT"
"PURCHASE"
visitor_idstring
points to AnalyticsVisitor
property_idstring
points to AnalyticsProperty
session_idstring
points to AnalyticsSession
page_urlstring
page_titlestring
page_referrerstring
devicestring
browserstring
osstring
countrystring
country_codestring
regionstring
citystring
metadatastring dictionary
valuenumber
currencystring
utm_sourcestring
utm_mediumstring
utm_campaignstring
utm_termstring
utm_contentstring

Returns

Response fieldTypeRequiredDescription
idstringNo
created_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestringNo
event_typeenumNoValues: PAGE_VIEW, SCREEN_VIEW, CLICK, FORM_SUBMIT, PURCHASE, SIGN_UP, LOGIN, LOGOUT, SEARCH, VIDEO_PLAY, VIDEO_COMPLETE, FILE_DOWNLOAD, SCROLL, SESSION_START, FIRST_VISIT, CUSTOM
visitor_idstringNopoints to AnalyticsVisitor
property_idstringNopoints to AnalyticsProperty
session_idstringNopoints to AnalyticsSession
page_urlstringNo
page_titlestringNo
page_referrerstringNo
devicestringNo
browserstringNo
osstringNo
countrystringNo
country_codestringNo
regionstringNo
citystringNo
metadatamap (string dictionary)No
valuenumberNo
currencystringNo
utm_sourcestringNo
utm_mediumstringNo
utm_campaignstringNo
utm_termstringNo
utm_contentstringNo

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'POST',
  url: 'https://api.unified.to/analytics/5de520f96e439b002043d8dc/event',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?