Completion rate is the number every LMS shows first, and for a customer academy it's the least useful one on its own. A customer who finishes every lesson and still opens three tickets a week didn't get what you built the academy for. The questions that justify the budget are about the product: do trained accounts activate faster, file fewer tickets, adopt the feature the course covers and renew more often?
Learnomy can't answer those by itself, because the answers live in your product analytics, help desk and billing system. What it gives you is the training side of the join, per person:
- Who enrolled, who finished and who passed. Course reports and the student lists show this, and both export to CSV.
- Events as they happen. Outgoing webhooks fire on enrolment, lesson and course completion, quiz results and certificates, so your CRM or data warehouse can tag the account the moment a customer finishes. See Outgoing Webhooks.
- Trends over time. Learnomy adds analytics for enrolments, completions and revenue by period.
A simple setup that works: send course completion to your CRM as a tag or property on the customer's account, then compare trained and untrained accounts on ticket volume and renewal after a quarter. Pick one course and one product metric to start, rather than trying to prove the whole academy at once.
Be careful with causation. Customers who take training are often the ones who were already going to succeed. A fair comparison matches accounts by plan and size, or tests a nudge on a random half of new signups.