analytics-tracker

Batch user analytics events and POST them to /api/analytics/batch.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Arnutt-N/hr-ims --skill analytics-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-tracker
Source: https://github.com/Arnutt-N/hr-ims/tree/main/.claude/skills/analytics-tracker
Command: npx skills add https://github.com/Arnutt-N/hr-ims --skill analytics-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects and batches user analytics events for HR-IMS to provide reliable insights without impacting app performance.

Core Features & Use Cases

  • Client-side event queuing: batches analytics events and sends them to the server in regular intervals or when thresholds are met.
  • Page view & event tracking: captures page views and user interactions across frontend and API layers.
  • Reliability & fault tolerance: includes retry logic, session management, and graceful handling of network failures.
  • Admin analytics access: exposes data that can be consumed by dashboards and admin APIs for reporting.

Quick Start

Integrate the analytics-tracker by initializing the client in your frontend to start batching events to the analytics API.

Frequently Asked Questions about analytics-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch user analytics events to avoid impacting app performance?

Batching user analytics events uses a client-side queue to group page views and interactions, sending them via batched POST requests at regular intervals or when thresholds are met to prevent performance degradation.

What is client-side event queuing for user behavior tracking?

Client-side event queuing for user behavior tracking collects page views and interactions in memory, dispatching them together to an analytics API endpoint to optimize network requests and ensure reliable insight collection.

How do I implement retry logic for analytics tracking during network failures?

Retry logic for analytics tracking handles network failures by gracefully retaining queued events and reattempting the batched POST transmission, ensuring no user behavior metrics are lost during connectivity drops.

Can I track both frontend page views and backend API events with one analytics tracker?

Yes, this analytics tracker applies to both frontend interactions and backend processing, capturing page views, user events, and performance metrics across the entire application stack into a unified batched API.

Does the event tracking system include built-in session management?

Yes, the event tracking system includes built-in session management that maintains user context across multiple batched POST requests, ensuring analytics data remains correlated to the correct user session.

What is the best way to expose batched analytics data to admin dashboards?

Exposing batched analytics data to admin dashboards requires server endpoints for analytics storage, which process the queued user behavior events and make them available via admin APIs for reporting.