Redshift tables: content, engagement & events

Manages and delivers a wide range of educational resources, supporting learning, engagement and content management. It defines individual pieces of content — articles, videos, documents, courses and other resources — that users can access.

Fuse uses it to: deliver learning materials and resources; organise content by type, topic or audience; support search, filtering and recommendations; let admins create, edit and manage content; and track usage, completion and engagement.

For reporting: composite_id + composite_type is the polymorphic link to the underlying asset (a video, a file, an article) — filter by composite_type before joining to videos. required_view_percentage is what determines whether a view counts as a completion. The signature_* columns cover digital signature configuration, but signature completion data itself is not exposed through Universal Analytics.

Organises and categorises information, making it easier for users to find relevant content and take part in discussions on specific subjects. A topic can be associated with content, questions, communities and other entities.

Fuse uses it to: categorise and organise content, discussions and learning materials; let users filter, search and browse by topic; help admins curate topics for engagement and relevance; and support reporting on topic usage and popularity.

Organises course content into structured sections, supporting effective learning, navigation and progress tracking. It defines the segments of a larger course or module, breaking content into manageable parts.

Fuse uses it to: structure courses into chapters for easier navigation; display chapter content as users progress; support progress tracking, completion status and analytics at chapter level; and let admins create, edit and organise chapters.

For reporting: ancestry encodes the chapter hierarchy as a path string — parse it if you need parent/child chapter levels. weight controls display order.

The source spreadsheet merged this table with comments into a single row. Description added here for clarity. The join table placing items of content inside a chapter, with an explicit ordering.

For reporting: use this to build a content-to-chapter-to-topic hierarchy, and to count how many items a topic contains — which is the denominator behind topic progress percentages. weight gives you the intended sequence, useful for drop-off analysis across a structured pathway.

Organises and connects chapters within courses, supporting structured learning paths, navigation and prerequisite management. It defines relationships between chapters — sequencing, prerequisites or navigation links.

Fuse uses it to: control the flow and navigation between chapters; enforce prerequisites or recommended learning paths; display related chapters or suggest next steps; and let admins organise chapter relationships.

Highlights specific content for different audiences, supporting flexible and targeted promotion. It is a join table linking a "featureable" item — usually content, but also topics or events — to a "target" such as a company or community, where that item should be promoted.

Fuse uses it to: display a curated list of featured content for a company or community; manage the order featured items appear in via position; support admin interfaces for selecting and organising featured items; and enable dynamic, context-specific promotion.

For reporting: this is the table that lets you answer "does featuring content actually drive views?". Join featured periods against views by content and date to measure lift. Note it is doubly polymorphic — both the target and the featured item need their *_type filtered before joining.

Manages and delivers video content, supporting learning, engagement and multimedia experiences. It defines each video resource, including metadata, file location and associations with other content.

Fuse uses it to: deliver video for training, learning or communication; organise videos into courses, learning plans or communities; track engagement such as views and completion; and let admins and users upload, manage and search videos.

For reporting: duration is essential for any watch-rate calculation — pair it with video_view_progresses.value to work out what proportion of a video was actually watched. state tells you whether a video has finished encoding; unencoded videos will show no view data.

Monitors and reports user engagement with video content, supporting personalised learning, compliance and analytics. It records user progress for individual videos so the application can resume playback, monitor engagement and report completion.

Fuse uses it to: resume videos where users left off; track and report video completion for learning plans, compliance or analytics; support engagement features such as badges or certificates; and let admins monitor which videos are watched and by whom.

Provides accessible and multilingual media experiences by managing subtitle files for video and audio content. It tracks the files providing subtitles or captions, supporting accessibility and multilingual delivery.

Fuse uses it to: display subtitles or captions during playback; support accessibility for hearing-impaired users; enable multilingual support; and let admins upload, manage and approve subtitle files.

For reporting: counting distinct label values per content item gives you subtitle-language coverage — a useful accessibility and localisation KPI.

Monitors and analyses user interactions with content, supporting engagement tracking, analytics and personalised experiences. It records each instance of a user viewing something — a course, article, video or profile.

Fuse uses it to: analyse user engagement and content popularity; generate activity feeds, recommendations and personalised dashboards; support reporting for admins and content creators; and trigger notifications or achievements based on views.

For reporting: filter viewable_type before joining to any dimension. request_type distinguishes how the view was made, which is useful for separating genuine consumption from incidental page loads.

Supports social engagement by tracking user approval of content, helping drive interaction and feedback across the platform. It records each instance of a user liking something, enabling popularity metrics, feedback and engagement tracking.

Fuse uses it to: display like counts and engagement on content, posts and comments; let users see what they have liked; support sorting, filtering and recommending popular items; and drive notifications and activity feeds.

The source spreadsheet merged this table with chapter_items. The description below is the comment-related half. Supports user interaction and feedback on content and chapter items, fostering engagement and collaborative learning. It tracks user-generated comments, supporting discussion, collaboration and review.

Fuse uses it to: display comments and discussions; support feedback, peer review and collaborative learning; let admins and moderators manage and moderate comments; and enable notifications and activity feeds from new comments.

For reporting: ancestry encodes threaded replies — a null ancestry means a top-level comment, so you can separate original comments from replies. anonymous flags comments posted anonymously where the community allows it; these still carry a user_id, so be careful not to expose it in any report. Filter deleted_at is null for live comments.

Lets users distribute content and resources, supporting collaboration, engagement and dissemination. It records sharing actions — when a user shares a course, article, event or other entity with another user, group or external recipient.

Fuse uses it to: enable users to share content for collaboration, learning or engagement; track and report sharing activity for analytics and notifications; support permissions and access control for shared items; and let admins monitor sharing across the platform.

For reporting: shared_from_id + shared_from_type capture the origin of the share, which lets you trace a chain of resharing and identify your genuine internal amplifiers. notifications_sent tells you whether the share actually reached anyone.

Supports social and personalised features by tracking who or what users are interested in, driving engagement and connectivity. It records who is following whom or what, enabling activity feeds, notifications and personalised recommendations.

Fuse uses it to: notify users about new activity from people or content they follow; build personalised feeds and recommendations; support social features; and let users manage what they follow.

Watch out: the field list exposed through the connector shows content_id rather than the polymorphic followable_id / followable_type pair described elsewhere. Treat this table as content follows for reporting purposes. Filter deleted_at is null to exclude unfollows — an unfollow soft-deletes the row rather than removing it, so deleted_at is actually a useful unfollow-date field for churn analysis.

Manages and displays user participation in gamified features, supporting engagement, motivation and recognition. It records activities contributing to a user's progress in gamified elements — earning points, badges, completing challenges or reaching milestones.

Fuse uses it to: update user profiles with achievements, badges and points; display progress, leaderboards and rewards; trigger notifications or unlock new gamification features; and analyse engagement and participation.

Monitors, analyses and reports on user activity, supporting platform optimisation, security and compliance. It tracks events such as logins, page views, content access and other actions for auditing, analytics and troubleshooting.

Fuse uses it to: analyse engagement and application usage patterns; support auditing, compliance and security monitoring; troubleshoot by reviewing user actions and system events; and generate activity reports for administrators.

Manages and displays scheduled activities, supporting user engagement and collaboration around time-based occurrences. It tracks the individual events that users or groups can attend, organise or interact with.

Fuse uses it to: display upcoming or past events; let users RSVP, register or participate; support notifications, reminders and calendar integrations; and let admins or organisers create, edit and manage events.

For reporting: this is a dimension, not a fact. Count rows here for "how many events exist"; go to event_occurrences for anything about when they ran or who came. learning_plan_id links an event into a learning plan, which is how attendance can contribute to plan completion.

Manages and displays individual sessions of events, supporting recurring schedules, attendance tracking and user engagement. It stores each occurrence of an event — a specific date and time when a recurring event takes place.

Fuse uses it to: display all upcoming or past sessions to users; manage registration, attendance and notifications per occurrence; support recurring events so users sign up for specific sessions; and let organisers edit, cancel or reschedule individual occurrences.

Organises and controls user participation, supporting approval workflows and tracking participation history. It connects users to the occurrences they have asked to take part in.

Fuse uses it to: invite users to participate; track which users have requested or been invited; manage and display the status of participation requests; and support workflows for accepting, declining or completing participation.

Tracks approvals for event occurrences. Use participation_requests to get the occurrence_id for the event and trace back to the event itself.

Fuse uses it to: manage and track participation requests needing approval; enforce access control for activities requiring vetting; let admins or organisers review, approve or reject requests; and display approval status to users.

For reporting: approver_role tells you whether the creator, the manager or a specified approver handled it — this is how you measure approval bottlenecks by route. The gap between participation_requests.created_at and participation_approvals.updated_at gives you approval turnaround time. declined_subject and declined_message hold rejection reasons.

Manages and enforces event requirements, ensuring users meet the necessary conditions before participating. It links events to their prerequisites — required training, completed assessments or other conditions.

Fuse uses it to: enforce that users complete certain actions before registering or attending; display prerequisite requirements on event pages; check eligibility during registration; and support reporting on prerequisite completion and event readiness.

For reporting: combine with participation_requests.prerequisite_learning_completed to quantify how much prerequisite friction is suppressing event attendance.

Connects events with relevant knowledge resources, supporting event preparation, learning and participant engagement. It is a join table linking events to knowledge items, indicating which resources are associated with or required for an event.

Fuse uses it to: display related resources or materials on event pages; ensure participants can access necessary information before, during or after an event; support preparation, follow-up and learning objectives; and let organisers attach relevant items to events.

For reporting: useful for testing whether events with supporting material see better attendance or better post-event assessment scores than those without.