Concepts

Fastmon's data model is small on purpose. Get these resources, and you've got the whole product.

Organizations

Top-level account container. Owns applications, members, tokens.

Applications

One tracking snippet: its hashes, settings, and the sites it serves.

Sites

One domain under an application, with its own dashboard and overrides.

Sessions

A short window of page-views from the same browser. Anonymous by construction.

Releases

A versioned deploy marker. Used for before/after comparisons.

Tracker settings

Presets and the per-setting configuration: what the beacon does in the browser.

How the pieces fit together

Organization
 ├── Members (with roles)
 ├── API tokens
 ├── Notification rules
 └── Applications
      ├── source_hash + collector_hash   (beacon URLs)
      ├── Tracker settings (preset, collector, site_policy)
      ├── Releases
      └── Sites (domains)
           ├── domain
           ├── Per-domain overrides (retention, store_stitch, …)
           └── Tags

Beacon data goes straight from the visitor's browser into our analytics store, ready to be queried from the dashboard or the API.

Reading order

If you're new, read in this order:

Organizations: what an account actually is.
Applications: the tracking snippet and everything it owns.
Sites: the domains under an application.
Tracker settings: what the beacon does in the browser.
Sessions: how page-views group.
Releases: for before/after deploys.