Facts reviewed: 2026-10-21

Sign in at the [Owleye Analytics console](https://app.owleye.dev/), complete email verification, and create an app. First-run onboarding offers two-factor authentication after app creation; you can choose “Skip for now” and enable it later in Profile. If you already enabled 2FA, sign-in still requires it. Each app has a public **Tracking ID** for the SDK. Your organization groups apps, billing, and shared allowances.

## Start collecting

Copy the Tracking ID from **Overview** or **Settings** and follow the [SDK quickstart](/docs/quickstart/) or [CDN guide](/docs/cdn/). Allowed origins are optional: an empty list permits any origin; a configured list restricts collection to the matching origins. Use separate apps for production and testing when you want separate reports.

## Find the right page

| Page | Use it for |
| --- | --- |
| Overview | Traffic totals, trends, pages, geography, devices, browsers, and referrers |
| Live | Recent activity, approximate active visitors, and pausable updates |
| Pro View & Funnels | Custom dashboards, saved views, and ordered conversion steps |
| Campaigns | Tagged visits and campaign breakdowns from automatically captured bounded UTM tags in SDK 1.0.3 |
| Web Vitals | Opt-in LCP, INP, CLS, FCP, and TTFB measurements, sample counts, and preliminary percentiles |
| AI | Questions about retained data, with supporting evidence and shared credits |
| Rules | Configure browser interactions collected by the optional rules module |
| API Keys | Create and revoke server ingestion keys |
| Events | Search and inspect collected events |
| Users | Manage app membership and roles |
| Settings | App configuration, allowed origins, ingestion pause, developer access, sharing, and deletion |
| Profile | Account, organization name, authentication, and available plan controls |

Some features depend on your plan and role. The interface uses the permissions returned by the server; hiding a control is not the security boundary.

## Roles

Owners manage app settings and developer access. Owners and admins can manage tracking rules and eligible memberships. Read-only members can inspect permitted reports. Owner membership cannot be removed through ordinary member management.

## Read a report

Select the correct app, choose a date range, and use the refresh icon to fetch updated data. Query failures show an error; they are not replaced with zeroes or sample traffic. Country data may be unavailable for some visits. The globe remains usable when a range has no country traffic.

Unique visitors are pseudonymous estimates, not a list of identified people. Daily and wider-range distinct counts are not interchangeable. Compare ranges and sample counts before drawing conclusions.

## Next steps

- [Live activity](/docs/live/)
- [Custom dashboards, sharing, and funnels](/docs/pro-view/)
- [Tracking rules](/docs/rules/)
- [AI analyst](/docs/ai/)
- [Developer access](/docs/developer-access/)

## How the Overview counts activity

- **Page views** count accepted `pageview` events, including tracked navigation.
- **Estimated sessions** count distinct visitor and fixed 30-minute time buckets containing at least one page view. These are not inactivity-based browser sessions. Returning within a bucket can merge visits; crossing a boundary can split one visit. Custom-only and duration-only activity does not add an Overview session.
- **Tracked events** count page views and custom or rule actions in the selected population. Duration segments and performance measurements are excluded. Verified bot page views can appear when **Hide bot views** is off, but never count toward billable usage.
- **Visible page segments** measure intervals while a page is visible. Switching tabs ends a segment; returning starts another. Their count is not a session count. Inspect them in the event explorer; the Overview displays their average duration in seconds.
- **Unique visitors** estimate distinct site-scoped pseudonyms with at least one page view in the selected range. Headline totals, daily data, public sharing, and audience breakdowns use this same definition. Custom-event-only activity, visible page segments, and performance beacons do not add Overview visitors. Event reports and Pro View can separately measure visitors who performed a selected action.

Changing networks can change a visitor pseudonym, so these counts estimate visitors rather than identify individual people.

A visitor can view several pages in one session. Page views and sessions are therefore not expected to match. Distinct visitor or session totals must be queried across the entire range, not added from daily buckets.

Browser aliases such as Chrome, Chromium, and Google Chrome appear as **Chrome**. Recognized acquisition hosts display names such as **X**, **ChatGPT**, and **Claude**. Unknown referrers retain their host name; a Direct label means no external referrer was supplied, not proof that someone typed the URL.

## Download displayed reports

Overview provides a traffic CSV and Events provides a CSV of the currently displayed aggregate groups on every plan, including Free. These downloads contain the data already loaded for the selected app and filters; they are not a full raw-event archive. Visitor counts in separate time buckets must not be added to estimate unique visitors over the whole range.