Skip to content
CursareDocs
Sign in

Start here

  • Overview
  • Getting started
  • Platform concepts

Create

  • Content
  • Editor and blocks
  • Block reference

Publish & access

  • Publishing and access
  • Custom domain & white-label

Learners

  • Learner experience
  • Learners and enrollments
  • Progress and certificates

Teams & cohort

  • Teams
  • Cohorts

Sales

  • Offers & checkout
  • Payments & payouts
  • Affiliates
  • Insights and reports

Admin

  • Organization & security
  • Plans, trial & billing
  • Appearance
  • Members & roles
  • Audit log

Developer

  • Integrations
  • API keys & webhooks
  • MCP server
  • API reference
Explore the API
Sales

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:

ViewWhat it answersSource
AcademicWho is enrolling, progressing, completing, and how they score on quizzes.Enrollments, completions, and quiz attempts.
FinancialHow much came in, how many purchases, refunds, and average ticket.Purchases verified by the connected payment provider.

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.

Different windows side by side

The indicator cards and charts use a rolling window you pick in the Insights header — 7, 30, or 90 days, defaulting to 30. The tables ("Revenue by content," "Learners by content") are cumulative (all-time) whatever range is selected. Don't compare a windowed number with a cumulative total without adjusting the period.

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:

ActionRequirement
View Insights (org and content)Organization member
Issue a refundFinance/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 the connected provider proves the payment — the platform never creates a purchase from a browser redirect alone.

Indicator cards (selected window)

The suffix on each card label follows the range picked in the header.

CardWhat it shows
Revenue · 7d / 30d / 90dSum of non-refunded purchases created within the window.
Purchases · 7d / 30d / 90dCount of paid (non-refunded) purchases within the window.
Avg ticketRevenue divided by the number of purchases in the window; shows — when there were no purchases.
Refunds · 7d / 30d / 90dCount of purchases in the window that were refunded.

Charts

ChartReading
RevenueBuyer-paid revenue by day.
PurchasesBars: paid checkouts per day.
RefundsBars: 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 Offers tab.

Amounts and currency

Amounts are stored in the currency's smallest unit (cents) and displayed divided by 100. Formatting uses Intl.NumberFormat in the viewer's locale with each purchase's own currency, so separators and symbol placement follow that locale (English renders R$1,234.56, Portuguese R$ 1.234,56) and whole amounts drop the decimals (R$100). When an organization has sales in more than one currency, the top cards and charts fall back to a plain unlabelled number, while the per-content table stays in each content's own currency. Revenue is always net of refunds: revenue queries ignore refunded purchases.

How refunds enter the chart

In the bar chart, a refund is counted on the day the purchase was created and only appears if the purchase was created within the selected window. An old purchase refunded yesterday won't show up as a refund in the current window.

Installments and access

Purchases can be paid in full (one_time) or, when the connected provider supports it, in installments (installments). The installment status governs access:

StatusEffect
activeAccess granted.
past_dueCharge failed — access is frozen until the next invoice is paid.
canceledPlan 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 campaign (discount code) used (never below zero).

Academic indicators

The Academic view tracks the learning funnel: enrollment, progress, completion, and quiz performance.

Indicator cards

CardWhat it shows
Enrollments · 7d / 30d / 90dEnrollments created within the selected window.
Completions · 7d / 30d / 90dCompletions (entire course finished) within the window, counted on the completion day.
Activity attemptsVolume of graded-activity sessions (quizzes, matching, ordering, flashcards).
Avg activity scoreAverage score of attempts with valid questions, or — when there are no attempts.

Learning charts

ChartReading
LearnersDaily area with two series: new enrollments and completions per day.
Quiz performanceDaily 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.

Enrollments include history

Enrollment counts (card, chart, and the Learners column) count all enrollment rows for the content, including refunded or past_due rows kept for history — not just learners with active access. Revenue, on the other hand, excludes refunded purchases. That's why "enrollments" and "net purchases" don't always match.

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:

SignalCutoffBehavior
Needs reviewBelow 70%Direct modules of the course whose last quiz score fell below the threshold become a review recommendation.
Test-out80% or aboveOn 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, Activity attempts, Avg activity score, and Avg rating.

Blocks

BlockWhat it shows
ReceptionAverage score highlighted, star distribution (5 to 1 with counts) and, with two or more months of ratings, the monthly score trend.
Hardest questionsUp 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%.
PollsFor 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.

Attempt read limits

The organization's quiz average is computed over up to 2,000 recent attempts; the per-content deep dive reads up to 500 attempts. Both grade against the current answer key, so reworking or removing questions changes what the per-question history means from then on.

Using data with context

A metric is not a diagnosis

An indicator shows that something changed. Combine academic data, financial data, and qualitative feedback before you conclude why it changed. A drop in revenue may reflect less traffic, a shift in conversion, payment unavailability, or a change in the makeup of the offer.

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.

Next steps

Payments & payoutsInstallments, refunds, and payouts behind the financial numbers.Learners and enrollmentsHow enrollments are created, approved, and feed the academic indicators.Progress and certificatesWhat counts as a completion and how progress is recorded.
PreviousAffiliatesNextOrganization & security

Your privacy choices

Necessary cookies keep Cursare working. Analytics and marketing technologies are optional and stay off until you choose them. Privacy Policy.

Sign-in, security and core platform functions.

Audience measurement such as Google Analytics.

Tag Manager and campaign attribution.