Skip to content

Latest commit

 

History

History
26 lines (21 loc) · 13 KB

tracksalerequestbody.md

File metadata and controls

26 lines (21 loc) · 13 KB

TrackSaleRequestBody

Example Usage

import { TrackSaleRequestBody } from "dub/models/operations";

let value: TrackSaleRequestBody = {
  amount: 816230,
  paymentProcessor: "stripe",
};

Fields

Field Type Required Description Example
externalId string This is the unique identifier for the customer in the client's app. This is used to track the customer's journey.
customerId string : warning: ** DEPRECATED **: This will be removed in a future release, please migrate away from it as soon as possible.

This is the unique identifier for the customer in the client's app. This is used to track the customer's journey.
amount number ✔️ The amount of the sale. Should be passed in cents.
paymentProcessor operations.PaymentProcessor ✔️ The payment processor via which the sale was made.
eventName string The name of the sale event. It can be used to track different types of event for example 'Purchase', 'Upgrade', 'Payment', etc. Purchase
invoiceId string The invoice ID of the sale. Can be used as a idempotency key – only one sale event can be recorded for a given invoice ID.
currency string The currency of the sale. Accepts ISO 4217 currency codes.
metadata Record<string, any> Additional metadata to be stored with the sale event.
leadEventName string The name of the lead event that occurred before the sale (case-sensitive). This is used to associate the sale event with a particular lead event (instead of the latest lead event, which is the default behavior). Cloned template 1481267