


Hollihop report: leads, students, payments
Reportkey reads leads, students and payments from Hollihop CRM and builds a report for the learning center director: which ad source brings leads, how many of them became students, how much was paid for tuition and how much was refunded.
- The authkey and subdomain are entered once for every project.
- Leads, students, study requests by UTM, payments and refunds by branch.
- The learning center shares one report with Yandex Direct, VK Ads and Metrica, plus AI insights and branding (not on every plan).


Hollihop integration: take the authkey from Settings, Integration, API and enter it with your CRM subdomain once on the Reportkey integrations page. Leads, conversion to students, study requests by UTM, payments and refunds by branch arrive on schedule as a link or PDF.
Learning center reporting on Hollihop CRM
Language schools, exam preparation centers and after-school studios sell courses and memberships, and their advertising is seasonal: late summer, January and spring before exams. In Hollihop the client path is a lead with an ad source, a series of status changes, conversion to a student, a study request and payments. Reportkey reads this through the API and builds a section of a recurring report for the center director, a branch manager or an agency client.
Hollihop integration: authkey and subdomain
Every Hollihop CRM has its own subdomain on t8s.ru, and API calls are signed with an authkey from Settings, Integration, API. Reportkey only reads leads, students, statuses and payments; schedules and cards stay untouched.
The subdomain and key are entered once on the integrations page as a shared connection. An agency with several centers adds one connection per center. If the key is reissued, the connection is flagged for re-authorisation while project settings remain.
Lead sources for a learning center
The first block uses leads. Hollihop stores the creation date, the ad source from the school’s list, status, branch and assignee:
- New leads in the period;
- Successful leads that reached a successful status;
- Unsuccessful leads lost or refused;
- Conversion to student as the share of successful leads;
- Breakdowns by ad source, branch, assignee and period.
Status types come from the CRM itself, so a school can rename statuses freely; the report follows the type, not the label.
When a lead became a student
The current status says where a lead is now, not when it got there. For accurate monthly conversion the report takes the date from status history, which records when and from which status each lead moved. A lead converted three weeks after the first contact counts in the week the change happened.
Study requests by UTM tags
Hollihop keeps campaign tags on the student’s study request rather than on the lead, along with referrer and the original lead link. A separate block counts study requests by utm_source, utm_medium and utm_campaign, which tells the ads contractor which campaigns produce requests that reach the CRM.
Student payments and refunds
Payment types cover tuition, materials, sections and tuition refunds, each with a state and a paid date. Income includes only confirmed payments with a paid date; refunds have their own line. Breakdowns cover branch, payment type, payment method and period, with UTC dates converted to the project time zone.
Learning center and ads in one report
CRM leads read best next to Yandex Direct, VK Ads, the school’s VK community, trial-lesson forms in Yandex Metrica and Calltouch calls. See the freelancer demo report, more niche systems on the CRM integrations page, and plans on pricing.
What goes into the Hollihop report
These are the metrics that the Hollihop integration already brings into Reportkey reports.
Hollihop reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Why teams connect Hollihop to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from Hollihop in client reports.
- Before the school year a language school launches ads but cannot say which channel produced students rather than trial-lesson calls.
- Front desk staff move leads to students, yet the conversion date gets lost because the card shows only the current status.
- Tuition, textbook payments and refunds share one export, and the accountant separates refunds from income by hand.
Each branch is shown separately. Every Monday the chain director sees new leads by ad source, leads that became students and confirmed payments for each school.
The contractor shows study requests by utm_campaign next to Yandex Direct and VK Ads spend. The client sees requests that reached the CRM and what happened to them, not just clicks.
The season is short, so speed matters. The director tracks lead-to-student conversion by assigned manager and refunds after the first trial month.
How Hollihop appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.

A table of ad sources with new, successful and unsuccessful leads and student conversion, beside bars of confirmed payments and refunds by branch.
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
Frequently asked questions
Short answers about how the integration works in Reportkey today.
What do I need to connect Hollihop?
Why are UTM tags missing from the leads block?
How does the report know a lead became a student?
Which payments count as paid?
Why can dates differ from the CRM interface?
How often is the data refreshed?
Often connected together
Working sources that teams usually add to the same report.
Hollihop report: leads, students, payments
Sign up, enter the key and CRM subdomain and pick a project. Your first report in 5 minutes.


