Institutional Analytics

Overview

Institutional Analytics covers platform-wide reporting and data access for administrators — enrollment trends, completion rates, course catalog performance, and organization-level learner data. This is analytics at the platform/institution level, distinct from course-level instructor analytics.

The primary modern solution is Aspects (ClickHouse + Superset), which provides both instructor-level and institutional dashboards through the same analytics infrastructure.

Current State (2026)

• Aspects: Primary analytics solution — institution-level dashboards in Superset show enrollment trends, active learners, completions, and program metrics across the platform
• Enterprise data: edx-enterprise-data provides enterprise-specific reporting; enterprise-integrated-channels syncs data to external HR/LMS systems
• Data exports: Platform supports bulk data exports via REST APIs; institutions may extract to their own data warehouses
• Event stream: Raw events available via event-routing-backends to ClickHouse; enables custom reporting

Architecture

• Aspects: openedx-aspects Tutor plugin installs ClickHouse + Superset; aspects-dbt transforms events into metrics; institution-level dashboards pre-built
• Enterprise reporting: edx-enterprise-data Django service with REST API for enterprise analytics; aggregate enrollment and completion data
• Integrated channels: enterprise-integrated-channels syncs learner completion data to external systems (Degreed, SAP SuccessFactors, Canvas, Cornerstone)
• Raw access: ClickHouse is directly queryable by data teams; events include enrollment, completion, and assessment data

Relevant Repositories

Repository	Role in This Feature	Activity Level	Notes
openedx/openedx-aspects	Aspects analytics Tutor plugin	High	Primary analytics
openedx/aspects-dbt	dbt transformation models	High	Data modeling
openedx/event-routing-backends	Event pipeline to ClickHouse	Medium	Data ingestion
openedx/enterprise-integrated-channels	Syncs data to enterprise HR/LMS systems	Medium	External integrations
openedx/edx-enterprise-data	Enterprise analytics service	Medium	B2B reporting

Recent Changes

• Aspects becoming the standard institutional analytics approach
• Enterprise integrated channels expanding coverage of external systems

History

Origin

• Year introduced: ~2014–2015 (institutional reporting emerged with edX's enterprise growth)
• Initial implementation: edX Insights (Hadoop/Hive pipeline); institutional reporting via Django admin and data downloads
• Context: As edX moved from open MOOCs to institutional partnerships, administrators needed aggregate reporting

Key Milestones

Year	Milestone	Teams / People Involved
~2014	edX Insights launched for institutional analytics	Unknown
~2016	Enterprise data service developed	Unknown
~2022–2023	Aspects project initiated as Insights replacement	Unknown
~2024	Aspects becomes recommended solution	Unknown

People Who Shaped This Area

• Engineering: Unknown — open question for interview
• Product: Unknown — open question for interview
• Design: Unknown — open question for interview

Open Questions

• [ ] Who led the original edX Insights institutional analytics product?
• [ ] Why was ClickHouse chosen over other OLAP databases for Aspects?
• [ ] How does the enterprise data service integrate with edx-enterprise?
• [ ] What institutional analytics questions are most commonly asked by platform administrators?
• [ ] How do integrated channels maintain data sync reliability?