Plain-English definitions for the terms you'll see across Tracely dashboards, reports, and settings.
Product design emphasis on counts and distributions rather than per-user replay; see Privacy & non-goals.
Automated flag when traffic deviates from recent patterns; see Anomaly Detection (fixed window in subtitle).
One hosted snippet and Site settings per domain or property; Tracely does not require a particular framework—add sites and install the script wherever you need first-party analytics.
Heuristic based on short single-page sessions; improves when Visit duration and engagement signals are on. Not identical to every other vendor’s definition. Exact math: Metric reference.
A group defined by a shared starting condition (e.g. signed up on a given week); retention tables show return rates by cohort.
Tracely is designed to work with GA4, exports, warehouses, and your consent layer (optional data sources, Bearer APIs, CSV), not only as a standalone island.
In-app checklist (HTTPS, ingest hostname rules, SRI, API tokens, public link password, etc.) with a copyable report for security or procurement reviews—not a penetration test. See Workspace tools.
Compares a list of expected paths (from Site settings) to page views in the last 7 or 30 days; surfaces paths with no traffic in that window. See Workspace tools.
Data from connected sources such as GA4 shown in labeled cards; not merged into first-party headline totals on Overview unless the UI states otherwise.
Optional attribution signal stored from the first visit (when the First-touch UTM toggle is on); see Campaigns and Retention.
Ordered steps (pages or events) measuring drop-off between steps.
A conversion counted when a named event occurs (often a custom event you send with tracely()).
Aggregate click counts per screen grid cell; not a video replay.
Campaign/source fields taken from the current page URL for that hit (default for many tables).
Catalog of formulas and stable metric IDs (App\Support\Metrics\MetricCatalog); in-app “i” buttons on stats link to help.
One recorded URL load. SPAs can emit extra views on route changes when SPA / history tracking is enabled in Settings.
Read-only share link for aggregates; no login.
Filters on path, UTM, country, etc., that limit which hits count before an alert fires.
Activity grouped in time windows; used for paths, entry/exit, and some reports. Cross-subdomain linking may use optional session bridge features (see Tracking events).
Time-limited cryptographic link (used for live snapshot).
A tracked property with a domain, tracking ID, and settings.
Overview card: heuristic score (e.g. out of 100) from traffic, JS errors, LCP—complements but does not replace Performance detail.
Mini seven-day pageview bar chart on Your Sites cards.
A workspace inside an organization; sites belong to a team.
Too few visitors or events in the selected window for stable rates (noisy funnels, empty cohort cells). See Understanding metrics.
Public identifier embedded in the script; sent as sid to ingest. Keep it in the snippet—not a password, but don’t publish it in public repos without understanding bot noise.
utm_source, utm_medium, utm_campaign, etc., on URLs; shown under Campaigns and related reports.
A stable-ish hashed bucket for a browser context (network + user agent + site). Not the same as a logged-in user in your product unless you explicitly tie them with custom events (usually avoided for privacy).
See these metrics on your own traffic
Explore everything Tracely tracks or see how it compares to Google Analytics.