Overview
Store playback events and query analytics.
Use the Analytics Server to store playback events and turn them into reports. You can use Chunkify's hosted service or run your own server.
View reports in the Chunkify dashboard, query them through the API, or connect an agent through MCP.
How it works
- The playback tracker attaches to your player and measures playback.
- Its Chunkify adapter sends events to your Analytics Server with a public player key.
- The server stores the events and calculates reports.
- You explore the results in Chunkify, query the Analytics API, or connect an agent through MCP.
Your player can be Chunkify Player, native HTML video, or another supported player. Use any stable videoId to associate events with your video. A Chunkify Asset ID is optional; using one from your Chunkify Project lets the dashboard also show its title, poster, and timeline thumbnails when available, with a link to the Asset.
Choose hosting
| Option | What you manage |
|---|---|
| Hosted by Chunkify | Add a server in your Project's Analytics Settings, configure your website origins, and connect the tracker. Chunkify manages the service and its storage. |
| Self-hosted | Run the service, manage credentials, storage, retention, and backups. Add its URL and a read-only key to Chunkify to use the dashboard. |
Each analytics project has separate events and credentials. A hosted connection provisions its analytics project for you. A self-hosted installation can contain several analytics projects, independently of your Chunkify Projects.
Explore the data
| Need | Report |
|---|---|
| Understand usage | Playback attempts, unique viewers, watch time, trends, and popular videos. |
| Find playback problems | Startup delays, buffering, playback scores, and observed errors. |
| Understand engagement | Watch-time distributions, progress reached, and sections actually played. |
| Compare audiences | Browser, OS, device, approximate location, and page breakdowns. |
| Inspect an attempt | A session timeline, rendition changes, background playback, and retained events. |
| Use data elsewhere | Analytics API queries, CSV reports, and read-only MCP tools. |
Browser analytics are best effort. A view is a playback attempt; it can fail before playback begins. Viewer counts use the anonymous viewer ID the tracker generates for each browser. See metric definitions.
APIs and credentials
The playback tracker sends events from the browser. Your backend uses the Analytics Server SDKs to read reports with a private analytics key.
The Chunkify API manages saved connections and hosted connection keys. Those operations use the main Chunkify SDK and Chunkify access tokens.
Analytics queries use a separate API and credentials. Chunkify access tokens do not replace an analytics key.
Next steps
- Setup: connect a hosted or self-hosted server and send events.
- Chunkify dashboard: explore reports in Chunkify.
- Configuration: manage servers, keys, browser access, and storage.
- SDKs: install an Analytics Server SDK and make your first query.
- Query reports: understand metrics, filters, and CSV exports.
- API reference: coming soon; access the OpenAPI specification in the meantime.
- Connect with MCP: explore analytics with an AI client.
- Administration: manage retention, credentials, backups, and upgrades.