Revenue and transactions
Send revenue events
Record purchases from the browser, app, server, or a custom webhook.
Last updated August 20, 2026
Before you start
- A stable external transaction ID
- A visitor, session, customer, or supported attribution key when available
How to do it
- 1
Choose the browser, SDK, Events API, or custom webhook path that owns the payment event.
- 2
Send amount, currency, revenue type, and the stable provider identifier.
- 3
Retry safely with the same external ID, then inspect the transaction in Transactions.
What to check
- Provider retries do not create duplicate revenue
- The event links to the intended visitor or remains clearly unattributed