--- title: Analytics subtitle: Understand the current analytics, reporting, and monitoring surfaces in OrcaPulse slug: documentation/analytics --- # Analytics This page documents the current analytics and reporting surfaces in OrcaPulse: Command Center totals, recent activity views, workflow analytics, lead execution monitoring, admin dashboard metrics, system health checks, and revenue reporting. ## What Analytics covers OrcaPulse already includes real analytics endpoints and operational dashboards. The product is not limited to message sending or workflow execution. It also exposes summary metrics, recent activity data, workflow performance counts, execution-state monitoring, system health checks, and revenue visibility. The current project splits this analytics story into two main layers: user-facing Command Center reporting under the dashboard routes, and deeper platform-wide analytics inside the admin routes. ## Command Center summary The dashboard controller already provides a Command Center summary endpoint that aggregates lead totals, successful calls, delivered SMS counts, sent emails, outbound WhatsApp traffic, and an overall success-rate percentage based on evaluated leads. It also returns a chart series for recently contacted leads across a configurable date range, which makes the analytics layer useful for day-to-day operator visibility rather than only back-office reporting. - Lead totals: total lead count is available directly from the summary response. - Messaging totals: SMS, email, and outbound WhatsApp counts are combined into message totals and also returned separately. - Success rate: evaluated leads with `successEvaluation` drive a percentage view of overall positive outcomes. ## Recent activity and workflow views The current dashboard layer also returns recent operational data. That includes the most recent leads, recent calls, and recently created workflows, plus workflow-level lead counts showing how many records were successful inside each workflow sample. This matters because OrcaPulse analytics is not only aggregate reporting. It is also a review surface for recent operational activity so teams can inspect what actually changed. - Recent leads: the dashboard includes recent lead records with status, source, workflow, and success evaluation fields. - Recent calls: call rows include lead linkage, dialed number, status, duration, and timestamps. - Workflow snapshots: recent workflows are paired with workflow-specific totals and successful lead counts. ## Admin and platform analytics The admin routes go further than the standard dashboard. They already expose a platform overview, per-user analytics, workflow analytics across all users, live-user visibility, and revenue analytics for the whole system. In practice this means OrcaPulse already has a real split between operator analytics and platform analytics. Day-to-day teams can review execution outcomes, while admins can view platform-wide growth, usage, and customer-level activity. - Dashboard overview: admin metrics include total users, active users, workflows, leads, calls, revenue, credits, and live users. - User analytics: admins can inspect one user’s workflow counts, lead status totals, call stats, transactions, and credit usage over time. - Workflow analytics: the admin layer groups workflows by status and shows workflow-associated lead counts across executing, pending, completed, and total states. ## Health and execution monitoring Analytics in the current project also includes runtime monitoring rather than only historical reporting. The admin execution monitor exposes currently executing leads, upcoming pending leads in the next hour, grouped execution-status counts, and a simple completion rate per hour. There is also a system-health endpoint that checks database connectivity, database response time, failed leads, failed calls, memory usage, API response time, and uptime. - Execution monitor: admins can see what is executing now and what is scheduled next. - Error visibility: failed leads and failed calls over the last 24 hours contribute to operational health awareness. - Performance metrics: response time, memory usage, and uptime are already part of the health payload. ## Revenue and credit visibility The analytics layer is also tied to billing behavior. Revenue analytics already calculate total revenue, revenue today, revenue this week, revenue this month, revenue over time, credits added over time, top customers, and grouped credit statistics. That means OrcaPulse reporting is not only about lead conversion. It also gives the platform team a way to understand purchases, customer spending, and credit movement. - Revenue windows: reporting is already grouped into day, week, month, and rolling time-series views. - Customer ranking: top customers are derived from completed purchase history. - Credit movement: the system tracks credits added, credits spent, and total credits in circulation. ## Current project shape The important thing to document honestly is that the analytics system is currently endpoint-driven and operationally focused. The backend already exposes strong summary and monitoring data, but the project does not yet show a large dedicated analytics module with deep custom segmentation, attribution modeling, or polished reporting-builder tooling. So today, Analytics is best understood as a practical visibility layer over leads, calls, workflows, revenue, and system health. It is already very useful for operations, and it gives the platform a clear base to expand later. ## Next steps After Analytics, the next useful Operations page is usually Templates / Workflow Library, because it explains how reusable workflow assets are structured before teams scale usage across multiple launches.