Track a sale
Track a sale for a short link.
Authorizations
Default authentication mechanism
Body
The unique ID of the customer in your system. Will be used to identify and attribute all future events to this customer.
1 - 100The amount of the sale in the smallest unit of currency — cents for two-decimal currencies, the full integer for zero-decimal ones (e.g. 1437 JPY), thousandths for three-decimal ones (e.g. 1437 KWD fils).
x >= 0The currency of the sale, as an ISO 4217 code. Reporting is always in USD: non-USD sales are converted at the exchange rate of the day the sale is recorded, and the original amount and currency are kept on the event. The rate is not re-applied later, so reported totals do not move with the exchange rate.
The name of the sale event. Recommended format: Invoice paid or Subscription created.
255"Invoice paid"
The payment processor via which the sale was made.
stripe, shopify, polar, paddle, revenuecat, custom, manual 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.
Additional metadata to be stored with the sale event. Max 10,000 characters when stringified.
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 for a link-customer combination, which is the default behavior). For direct sale tracking, this field can also be used to specify the lead event name.
"Cloned template 1481267"
[For direct sale tracking]: The unique ID of the click that the sale conversion event is attributed to. You can read this value from cq_id cookie.
[For direct sale tracking]: The name of the customer. If not passed, a random name will be generated (e.g. “Big Red Caribou”).
100[For direct sale tracking]: The email address of the customer.
100[For direct sale tracking]: The avatar URL of the customer.

