Start with the sample workspace
The demo reads a synthetic dataset embedded in its page. Each record represents a date, a browser group, a device group, and three counts: sessions, pageviews, and goal sessions. The full dataset is also available as a local JSON download.
Changing the range selects the last 7, 30, or 90 illustrative days. Changing the device filters that selection. The interface then sums the counts and computes goal rate as goal sessions divided by sessions. Export includes these filters and the resulting browser aggregates.
No visitor tracking script, authenticated account, collection endpoint, or database is supplied by this site. The demonstration is a way to inspect reporting structure, not a connected analytics service.
| Field | Type | Meaning |
|---|---|---|
| date | String | Illustrative date in YYYY-MM-DD format |
| browser | String | One of the six sample browser groups |
| device | String | Desktop, mobile, or tablet sample category |
| sessions | Integer | Recorded sessions represented by the synthetic row |
| pageviews | Integer | Pageview events represented by the row |
| goalSessions | Integer | Sample sessions containing a defined goal |
Use a small event contract
Before implementing collection elsewhere, describe the purpose, exact trigger, approved properties, counting rule, and permitted collection state. The following object is a synthetic planning example. It is not a request to a live BrowserTrack API.
{
"event": "guide_opened",
"schema_version": 1,
"properties": {
"topic": "browser-analytics",
"placement": "resources"
},
"measurement_purpose": "Evaluate guide discoverability",
"data_classification": "synthetic-example"
}Plan transport and storage separately
A production collector needs a real destination, validated input, appropriate permissions, operational monitoring, and documented retention and access rules. A client-side event listener does not supply those components by itself.
MDN’s sendBeacon reference explains a browser method for queuing small analytics POST requests. Queuing is not an application-level confirmation that a report was processed successfully. Review the destination and delivery behavior for your own implementation.
Use the integration patterns and tracking plan guide to document the end-to-end design.