Documentation
Build your first integration, learn what reports mean, and find the contracts you need as your application grows.
Start with your application
Use the .NET library
Create an engine, record visits and purchases, and read traffic and revenue reports.
ExploreIntegrate a web host
Collect website activity and expose reports through your ASP.NET Core application.
ExploreRun the dashboard
Explore traffic, audience, acquisition, events, and funnels in a ready-to-use interface.
ExploreExplore by task
| Section | Use it when you need to |
|---|---|
| Getting started | Install the packages and complete your first integration |
| Concepts | Understand events, visitors, time ranges, and privacy |
| Practical guides | Build reports, analyze behavior, or adapt collection |
| Performance | Explain a query plan or choose aggregation and indexes |
| Operations | Configure, deploy, maintain, and observe a dataset |
| Reference | Look up APIs, settings, query semantics, and HTTP contracts |
Choose the right package
ZoneTree.Analytics provides tracking, storage, queries, and typed web reports. ZoneTree.Analytics.AspNetCore adds dependency injection, request and browser tracking, and reporting endpoints.
The dashboard is a separate application built on those packages. Its host settings are not the core library defaults.
Build a useful report
Once collection is working, choose a workflow close to your application:
- Website: Traffic, acquisition, and engagement.
- Product: Purchases, revenue, and checkout completion.
- Service or worker: Volume, errors, and latency.
Each guide connects the recorded fields to the questions the report answers. Use the query reference when you need the exact contracts.
Read at the right depth
Start with a guide to accomplish a task. Use concepts to understand the model behind the result. Use reference pages for exact defaults and behavior.
For your first report, follow installation, first events, and web reports.
For performance work, follow query planning, secondary indexes, and benchmarking.
For measured results, see the 5M-event query benchmark: annual reports, filtered queries, p95 timings, and the recorded environment.