Transactions
Transactions in the Business area (Revenue) — route /business/transactions.
Transactions lives in the Business area of the dashboard, under Revenue.
At a glance#
| Dashboard route | /business/transactions |
| Area | Business (business) |
| Group | Revenue |
| Platforms | Available for every app platform. |
What it does#
The revenue ledger: every purchase event with its amount, type, currency, linked user and transaction id. It has a date range, a sortable table and one export path producing CSV or JSON from the same columns you see.
When to use it#
When you need the individual rows rather than an aggregate: reconciling against your payment provider, investigating one customer's charge, or exporting revenue data for a finance process.
It is also the page that answers "where does that number come from?" for every other revenue figure in the dashboard — they are all aggregates over this ledger.
Workflow#
Set the date range before exporting
The export follows the table, so the range is the filter.
Match on transaction id when reconciling
It is the identifier your payment provider also knows, which makes it the join key.
Check currency before summing
A ledger with mixed currencies cannot be totalled without conversion. Read the column.
Follow the linked profile for context
A charge is more interpretable next to what the customer was doing — see Profiles.
Permissions and prerequisites#
Requires revenue-bearing tracked events carrying amount, currency and a transaction id. See Events.
Limits and edge cases#
Client-reported, so it can be fabricated. An SDK key is extractable from your app, which means revenue events can be forged. Server-side reporting is the answer where that matters.
Refunds are separate — see Refunds.
Duplicates are visible, not silently merged. Purchases shows the accepted / rejected / duplicate status per event.
Subject to retention.
Troubleshooting#
Total does not match the payment provider. Expected to some degree; the gap is missing client events and duplicates. Compare by transaction id to find which.
Revenue missing for a known purchase. The event did not arrive. Check whether the purchase completes on a server callback your client never learns about.
Where the data comes from#
Served by
Subscriptions