Visitors arrive, but signups do not follow. A pageview chart shows the traffic; the next useful question is which action or step needs attention.

Owleye Analytics connects that question to a workflow. Install page analytics and the optional rules entrypoint once. Then create supported click, form-submit, and section-visible rules from the dashboard. With a stable selector already in place, each new rule does not need another application release. New tracker starts and page loads fetch saved changes; open tabs retain their loaded catalog.

Build an ordered funnel from the recorded events to see where activity drops off. A submit event measures an attempt. Use an explicit application event for a confirmed signup or payment, so the final step describes the outcome you actually care about.

On eligible paid cloud plans, when AI is enabled and available, ask questions about the retained data and inspect the supporting report. It cannot reconstruct uncollected events or prove that a source caused a signup.

The browser SDK has separate entrypoints for page analytics, rules, and performance measurements. Start and stop them according to your site's collection decision. No cookies or browser storage from the visitor script; the [privacy reference](/docs/privacy-compliance/) explains the server-side pseudonyms and other boundaries.

Owleye Analytics manages the API and reporting infrastructure. ClickHouse holds analytics facts; SQLite holds account and configuration data. Authentication, allowances, retention, and data-rights workflows are enforced by the service.

[Start free](https://app.owleye.dev/) with one useful event and a funnel toward a confirmed signup. The [quickstart](/docs/quickstart/) covers installation and verification.