Purchase Events

Send sales transaction data to Kevel for attribution processing.

Path Params
string
required
Query Params
string
required

multiple userKey values are accepted, representing the userKey(s) this customer was seen on in previous ad requests. If you don't have a solution for gathering and sending the different relevant userKey(s) you can leverage Kevel Audience for this purpose. To send multiple user keys, repeat this param in your request: .../purchase?userKey=annonymous1&userKey=loggedin1&userKey=guest1

string
required

Product identifier, used to lookup product meta data in the Kevel Catalog

date
required

ISO 8601 (eg. 2017-01-19T16:27:20.974Z) or unix epoch time

int32
required

The quantity of items in this transaction (line item of an order)

float
required

The product price of the line item. The total amount for the line item will be quantity * price

string

The transaction identifier

string

Optional merchant identifier, used in Marketplaces to identify the seller

int32

the expected additional quantity of items sold to this customer. As a Retailer, you can decide to send the quantity of the particular item in the line item, or it can be representative of the prorated future number of total items expected to be purchased by the customer

float

the expected additional sales value sold to this customer. As a Retailer can decide to send the sales value for the specific product in the line item or it can be representative of the prorated future value expected to be spent by the customer. This will not be multiplied by ltvQuantity, it is the total value

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
LoadingLoading…
Response
Choose an example:
application/json
text/plain