Moyklass Requests by source, enrollments, and payments
Moyklass report: requests, enrollments, payments
Reportkey reads group enrollments, clients, invoices and payments from Moyklass CRM and builds a report for a school or club: which sources bring requests, how many enrollments reached classes, how much was invoiced and how much actually came in.
Sign up, add the company API key and pick a project. Your first report in 5 minutes.
- The Moyklass company key is entered once and the token renews itself.
- Requests by source and UTM, enrollments by status, payments and refunds.
- The school shares one report with Yandex Direct, VK Ads and Metrica, plus AI insights and branding (not on every plan).
TL;DR
Moyklass integration: take the company API key from the CRM integrations and API settings and enter it once in Reportkey; the token then renews automatically. Requests by source and UTM, enrollment outcomes, payments, refunds and invoices by branch and course arrive as a link or PDF.
Moyklass CRM reporting for schools and clubs
Moyklass is used by language schools, kids’ clubs, art studios and sports sections where students join groups for a course. Enrollment comes in waves, before September, after the winter holidays and before summer, and the school pays for ads in each wave. The core CRM unit is a group enrollment with a course, status, price, ad source, creation method, tags and manager. Reportkey reads enrollments together with clients, invoices and payments and builds a section of a recurring report.
Moyklass integration with a company API key
The connection works at company level, not per employee. Take the API key from the Moyklass integrations and API settings and enter it once on the Reportkey integrations page. The service exchanges it for a company token and renews it; Reportkey only reads data and never changes groups, schedules or cards.
An agency serving several schools adds one connection per school. If the key is reissued in the CRM, the connection is flagged for re-authorisation and project settings stay.
Request sources: ad source and creation method
Two enrollment fields are often confused. The ad source is where the person heard of the school: search, social media, a referral, a street sign. The creation method is how the request entered the CRM: a website form, a widget or manual entry. The new requests block shows both, plus campaign tags:
- New group enrollments by creation date;
- New clients created in the period;
- Breakdowns by ad source, creation method, UTM, branch and period.
The school defines source values, and tags arrive from website forms. Phone requests saved without a source end up on their own row, which the report makes visible.
Enrollment outcomes
The second block answers how many of them actually study. Enrollments are grouped by the school’s own statuses, and the status change date is stored on the enrollment. That gives the share reaching classes by course and branch: which course fills up, where requests stall, where many sign up but few attend a first class.
Payments, refunds and invoices
Moyklass splits money by operation type: income, write-off and refund, with negatives stored as minus amounts. The report counts payments from income only, shows refunds separately and lists invoices as a third line. An invoice is an amount with a due date, not money. Breakdowns cover branch, payment type and period.
Club CRM analytics next to ads
Show enrollment next to Yandex Direct, VK Ads, the VK community, website forms in Yandex Metrica or Roistat if end-to-end attribution already runs there. See the freelancer demo report, more niche systems on the CRM integrations page, and plans on pricing.
Metrics
What goes into the Moyklass report
These are the metrics that the Moyklass integration already brings into Reportkey reports.
New requests
New clients
Enrolled
Payments
Refunds
What this integration adds to the report
Requests by source, enrollments, and payments
Pricing
Moyklass reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Use cases
Why teams connect Moyklass to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from Moyklass in client reports.
Pain points
- An English school sees dozens of requests a week in the CRM but cannot separate those from ads from those an administrator logged after a phone call.
- Invoices and payments blur together in owner meetings: a big invoiced total sounds like revenue even though less money arrived.
- Refunds for missed classes shrink the till, yet nobody shows them separately in the weekly summary.
Moyklass
A chain of kids' clubs and studios
The chain director gets a per-branch report: new group enrollments by ad source, share that reached classes by course, payments and refunds. It is clear at once which course fills up and which one stalls.
Moyklass
An English school for adults
The marketer separates requests from the website, from the widget and those created by staff. Ad spend sits alongside, so cost per request counts only requests that truly came from campaigns.
Moyklass
An agency with several school clients
Each school has its own Moyklass key and report schedule. The client sees UTM campaigns and enrollment results without CRM access, and the contractor adds a short conclusion to the numbers.
Report preview
How Moyklass appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.
A table of ad sources and creation methods with new group enrollments, an enrollment status funnel by course and tiles for payments, refunds and invoices issued.
How to connect
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
01
Connect the account
Save the Moyklass connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the Moyklass account and pipelines that should supply leads, deals, and sales to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ
Frequently asked questions
Short answers about how the integration works in Reportkey today.
What do I need to connect Moyklass?
The company API key from the Moyklass settings, in the integrations and API section. You enter it once on the Reportkey integrations page; the service obtains and renews the company token itself, so no staff login or password is needed.
How is the ad source different from the creation method?
Moyklass keeps them in two separate lists. The ad source says where the person heard about the school. The creation method shows how the request entered the CRM: website form, widget or manual entry by an administrator. The report can split requests by both fields.
Why is the invoiced total higher than payments?
An invoice is an amount issued with a due date, not a payment. Clients pay in parts or late, and some invoices stay unpaid. Invoices and payments are therefore separate lines in the report and never added together.
How are refunds and write-offs handled?
Moyklass payments carry an operation type: income, write-off or refund, with write-offs and refunds stored as negative amounts. Payments count income only, and refunds have their own line so they do not disappear inside a net figure.
What student data does the report see?
The company token grants broad access, but the report uses only aggregates of requests and payments. Grades, individual attendance and student cards are not shown.
How quickly is data refreshed?
Enrollments and payments are read for the chosen dates when the report is built. Moyklass allows up to seven requests per second and returns up to 500 records per page, so even a multi-branch chain loads without delay.
Related integrations
Often connected together
Working sources that teams usually add to the same report.
Moyklass report: requests, enrollments, payments
Sign up, add the company API key and pick a project. Your first report in 5 minutes.