GetCourse report: orders, payments, revenue

GetCourse online school report for producers and experts

An online school runs on launches: ads lead to a webinar or a lead magnet, some viewers place an order and some of them pay. The expert and the producer want to see that chain end to end, not just clicks. GetCourse splits it across sections: users in one place, orders in another, payments in a third. Reportkey pulls all three through the school API and builds a section of a recurring report that the client receives as a link or PDF.

Ad accounts and web analytics sit in the same document, so the post-launch call is about the cost of a paid order instead of where the numbers came from.

GetCourse integration: API key and school address

You need two things: the school address on getcourse.ru and a secret key. The owner or an admin with the right to configure the account issues it under Profile, Account settings, API. GetCourse offers read-only or read and write mode; the report needs only the first, and Reportkey never changes anything in the school.

The key and address are entered once on the Reportkey integrations page and become a shared connection. An agency with several experts adds one connection per school and picks the right one in each project. If the key is deleted in school settings, the connection is flagged for re-authorisation; you paste a new key in the same place and project settings stay intact.

Exporting GetCourse orders through the API

Order data arrives through the same export as the regular CSV from the admin panel: status, price, amount paid, offer and tags. The export can be limited by creation, payment, completion or status change date, so the block settings define which event to count. Launch reports usually use the creation date; financial summaries use the payment date.

The export feeds the orders block:

• Orders placed in the period;
• Paid orders that reached full payment;
• Order amount for the offers sold;
• Payment conversion as the share of paid orders;
• Product and offer split showing which course or tier people buy.

Incoming payments versus order totals

The most common argument after a launch is the gap between order totals and money in the bank. Payments arrive in parts, in instalments, from a user balance or get refunded later. Incoming payments therefore form a separate block built from the payment export, filtered by date and payment status. The producer sees both demand and real revenue.

GetCourse orders by UTM source

For the media buyer the key question is which campaign brought payments. Since order tags and user tags differ, the UTM block uses order tags and shows orders, paid orders and amount paid for each source and campaign pair, with a caption naming the tag type.

Sign-ups at the top of the funnel

The user export filtered by creation date gives new registrations by day, week or month. Together with orders this forms one funnel: people who joined, people who ordered, people who paid. Placed next to ad spend, sign-ups show the cost per registration before sales start.

Export limits and paid plans

Exports run on paid GetCourse plans only, one at a time, within 100 requests per two hours per account. A large school is therefore built from sequential exports and takes longer than an ad account. Guaranteed history depth is not published, so connect early if you plan year-over-year comparisons.

End-to-end school analytics next to ads

Orders make sense next to costs. The same report usually includes Yandex Direct campaigns, VK Ads, goals in Yandex Metrica and the school’s VK community. If attribution already lives elsewhere, add Roistat. See a multi-channel example in the context agency demo report, browse other niche systems on the CRM integrations page, and check the 14-day free trial on pricing.