This is a html view of the json schema please take the json schema as reference DOWNLOAD THE JSON SCHEMA

User Request

Type: object

This object describe a user/customer behaviour. For example, the marketing team would like to trigger a journey whenever a Cart is deemed to have been abandoned.

Type: object

This object is used to describe some technical meta information related to the event

Type: enum (of string)

The application source of this event

Must be one of:

  • "OPCO"

Type: enum (of string)

The version of the json format event

Must be one of:

  • "v1"

Type: enum (of string)

The user behaviour type

Must be one of:

  • "ABANDONED_CART"

Example:

"ABANDONED_CART"

Type: object

Type: string

User's email.


Example:

"geert@electracontractors.be"

Type: string

User's title.


Example:

"Dhr."

Type: string

User's firstname.


Example:

"Geert"

Type: string

User's lastname.


Example:

"Corijn"

Type: object

Type: string

OpCo's organizatinal customer number that uniquely identifies its account. In the case of OpCo organised with a regional model or commercial organisation this should be suffix by '{orgId}'. if the accountId is 13563 and the orgId is OVIA so this field should contains 13563OVIA


Examples:

"1234567"
"1234567_OVIA"

Type: string

VAT number or Siret number.


Example:

"GM4837192941"

Type: string

Name of the organizational customer.


Example:

"Independent Electric"

Type: string

Optional field, needed by OpCo organised with a regional model or commercial organisation. It can be used to filter or route based on the orgId.


Examples:

"org123"
"SNE"

Type: array

Additional information

No Additional Items

Each item of this array must be:

AdditionalInformation

Type: object

Object representing an additional information of the behaviour

Type: string

Name of the additional information


Examples:

"message"
"companyName"

Type: string

Value of the additional information


Example:

"Super Elec"