Skip to main content
POST
cURL

Overview

Associate a visitor with a known person when they sign in, submit a form, or provide their email address. Use the same visitorId in that visitor’s page and custom events so their activity can be associated with their identity.

Examples

Set UNIFY_WRITE_KEY to the event source’s write key and use an allowed origin in the Origin header. Replace the example visitor ID and timestamp with those from the actual event. See Analytics authentication for setup.
Use person and company to provide record attributes. For additional attributes, use their API names and values that match their types in Unify.

Authorizations

X-Write-Key
string
header
required

Use the event source’s write key. Requests also require an allowed Origin header.

Headers

Origin
string<uri>
required

Website or application origin allowed for the event source. Required for browser and server-side requests.

Body

application/json

An identify event is used to send information about a visitor.

type
enum<string>
required

The type of analytics event being sent.

Available options:
identify
visitorId
string
required

Unique identifier for the visitor that triggered this event.

timestamp
string<date-time>
required

Timestamp of the event (in UTC).

context
object
required

Contextual information about the client behind the event.

sessionId
string

Unique identifier for the session in which this event occurred.

sentAt
string<date-time>

Timestamp at which the request was sent (in UTC). May differ from the event timestamp if sending was delayed.

traits
object
deprecated

Traits for the identify request payload.

company
object

Information about the company associated with the visitor.

person
object

Information about the person associated with the visitor.

Response

The request has succeeded.