Skip to main content

Analytics

Analytics lets you query your own payment data directly and turn it into reports — from a quick look at last month's payouts to a scheduled export that feeds your accounting or BI system.

Where the portal lists and the standard reports answer fixed questions, Analytics answers your questions: you write a query, get a CSV, and can have that query run again on a schedule.

info

The most common use is payout analytics — reconciling what was paid out, when and for which transactions, and breaking it down by period, payment method, currency or space. If that is what you need, start with the payout example below.

What you can do with it​

CapabilityWhat it means
Query your data in SQLAnalytics runs PrestoDB SQL. You write a query against the tables your permissions give you access to.
Export as CSVEvery result can be downloaded as a CSV file, ready for Excel, your accounting system or a BI tool.
Schedule queriesRun a query automatically — daily at a given time on chosen weekdays, or monthly on chosen days, with a last-day-of-month fallback.
Automate deliveryPush the results to your own SFTP server instead of downloading them by hand. See (S)FTP Connection.
Use it from the APISubmit queries, poll their status, fetch the results and cancel running queries through the REST API — see Web Service API.

Payout analytics​

The most frequent reason merchants use Analytics is to understand their payouts in more detail than the standard views allow. Typical questions:

  • Which transactions are contained in a specific payout, and what fees were deducted?
  • How do payouts develop per week, per month, per currency or per space?
  • Which payment methods contribute how much to each settlement?
  • Where is the difference between what was sold in a period and what was actually paid out?

The portal answers the first level of these questions without Analytics — see Payouts for the balance overview, Balance Report and Statements and Transaction Reports for the standard reports, and Pending Settlement Overview for what is still open.

Use Analytics when you need to slice that data yourself, combine it differently, or deliver it somewhere automatically every month.

How a query works​

  1. Write the query in the portal, against the tables shown in the assets panel. The panel lists the tables and views your permissions give you access to, in alphabetical order.
  2. Submit it. Queries run asynchronously: the query first has the status PROCESSING and then becomes SUCCESS, FAILED or CANCELLED.
  3. Fetch the result. A successful query produces a CSV file. The response also tells you the size of the result file and how many bytes the query scanned.
  4. Repeat it on a schedule if you need the same figures regularly, or hand the export to an SFTP connection.
warning

Result files are provided through a temporary download link that is valid for roughly 5 minutes. Generating a link counts as a download attempt, so scripts should fetch the file immediately rather than storing the link.

Packages and costs​

Analytics is available in more than one package. The Advanced Analytics package is what unlocks automated delivery to your own server through SFTP Dispatch.

Usage is charged: each generation of a result file counts as a download attempt and is billed, and queries are billed according to the amount of data they scan. Writing selective queries — restricting the period and the columns you actually need — therefore keeps both the runtime and the cost down.

info

Which package is active for you, and what your queries and downloads cost, depends on your plan. You find your plan and the associated costs under your account — see User, Account and Space and Account & Billing, or ask our support team.

Permissions​

Which tables and views you can query is controlled by your user's permissions — two users in the same account can therefore see different data in the assets panel. See Users, Roles and Invites if a table you expect is missing.