Insights and reports
Insights turn platform events — enrollments, completions, quiz attempts, and verified purchases — into indicators for academic and financial decisions. The dashboard separates those two worlds into two distinct views so each team reads the numbers from its own context.
Overview
Insights live in Dashboard → Insights. The screen opens directly on the Financial view, and a selector at the top switches between the two views:
| View | What it answers | Source |
|---|---|---|
| Academic | Who is enrolling, progressing, completing, and how they score on quizzes. | Enrollments, completions, and quiz attempts. |
| Financial | How much came in, how many purchases, refunds, and average ticket. | Verified purchases (Stripe Checkout). |
Each paid content or content with learners also has its own deep dive, in the Insights tab of the content editor — see Per-content deep dive.
Who can see Insights
Any organization member can open the Academic and Financial views and the per-content deep dive — reading requires only membership in the organization. Actions that move money have a higher requirement:
| Action | Requirement |
|---|---|
| View Insights (org and content) | Organization member |
| Issue a refund | Finance/admin role on the owning team, or organization owner/admin |
See Payments & payouts for the full refund flow.
Financial indicators
The Financial view gathers revenue and purchases over time. Every row comes from the purchases table, which is only written after Stripe Checkout confirms the payment — the platform never creates a purchase without a verified charge.
Indicator cards (last 30 days)
| Card | What it shows |
|---|---|
| Revenue · 30d | Sum of non-refunded purchases created within the window. |
| Purchases · 30d | Count of paid (non-refunded) purchases within the window. |
| Avg ticket | Revenue divided by the number of purchases in the window; shows — when there were no purchases. |
| Refunds · 30d | Count of purchases in the window that were refunded. |
Charts
| Chart | Reading |
|---|---|
| Revenue | Daily area: what verified checkouts collected, day by day. |
| Purchases | Bars: paid checkouts per day. |
| Refunds | Bars: refunded purchases per day. |
"Revenue by content" table
A cumulative list, net of refunds, of the paid content that had sales — sorted from highest to lowest revenue. Columns: Content, Purchases, and Revenue (in each content's currency). Each row opens the content directly on the pricing tab.
Installments and access
Purchases can be paid in full (one_time) or in installments (installments, a Stripe subscription with a limited number of charges). The installment status governs access:
| Status | Effect |
|---|---|
active | Access granted. |
past_due | Charge failed — access is frozen until the next invoice is paid. |
canceled | Plan ended, access revoked. |
A refund flags the purchase, revokes the learner's access (the enrollment becomes refunded, but the row and the history remain), and deducts one redemption from the coupon used (never below zero).
Academic indicators
The Academic view tracks the learning funnel: enrollment, progress, completion, and quiz performance.
Indicator cards
| Card | What it shows |
|---|---|
| Enrollments · 30d | Enrollments created in the last 30 days. |
| Completions · 30d | Completions (entire course finished) within the window, counted on the completion day. |
| Quiz attempts | Volume of the organization's quiz attempts. |
| Avg quiz score | Average score of attempts with valid questions, or — when there are no attempts. |
Charts
| Chart | Reading |
|---|---|
| Learners | Daily area with two series: new enrollments and completions per day. |
| Quiz performance | Daily area: average score (in %) of that day's attempts. |
"Learners by content" table
A cumulative list of the content with at least one enrollment, sorted by number of learners. Columns: Content, Learners, Completed, and Rating (average star rating). Each row opens the content on its Insights tab.
A completion is the entire course
An enrollment only counts as completed when the content's full tree (the root content and all referenced modules) is finished for the first time — that moment is what stamps the completion date. Reopening a learner's progress resets the completion but preserves the quiz history. See Progress and certificates.
Quiz and mastery signals
Beyond the averages, quizzes feed adaptive signals that appear to the learner and help production see where difficulty lies. Two cutoff lines govern these signals:
| Signal | Cutoff | Behavior |
|---|---|---|
| Needs review | Below 70% | Direct modules of the course whose last quiz score fell below the threshold become a review recommendation. |
| Test-out | 80% or above | On a leaf module (no sub-content), hitting the mark on the last attempt lets you skip the module. |
The per-question history is re-graded against the current published answer key: removed questions simply drop out of the count, and questions that still exist regroup right and wrong answers to guide the adaptive sampling of future attempts.
Per-content deep dive
The Insights tab of a content's editor offers a focused reading of that content, with its own cards and blocks.
Cards
Enrolled, Completed, Reviews, Quiz attempts, Avg quiz score, and Avg rating.
Blocks
| Block | What it shows |
|---|---|
| Reception | Average score highlighted, star distribution (5 to 1 with counts) and, with two or more months of ratings, the monthly score trend. |
| Hardest questions | Up to 8 questions sorted from lowest to highest correct-answer rate; each shows the prompt, the % correct, and the number of responses. The bar turns amber when correctness is below 70%. |
| Polls | For each poll, the options with percentage and vote count. |
When there are no attempts, votes, or ratings yet, the block shows the message that analytics will appear as soon as learners start interacting.
Using data with context
Questions that Insights help answer:
- where learners drop off in the experience and how much time separates enrollment from completion;
- which content concentrates enrollments, completions, and the best ratings;
- which questions concentrate errors and warrant a content review;
- how revenue, purchases, and refunds move over time;
- what the average ticket is and which content drives revenue.
Share only the data you need, and respect each team's access scope.