Add the next event. Skip the next deploy.
After the rules collector is installed, configure click, form-submit and section-visible rules from your dashboard. New page loads pick them up.
See how tracking rules workWeb and product analytics
OwlEye records page views and the actions you choose, then shows the measured step where people leave. The visitor script does not write cookies or browser storage.
Use the drop-off to decide what to inspect next.
Free up to 10,000 events a month. Pro from $9. No cookies or browser storage from the visitor script. Compare plans.
From arrival to signup.
Observed source tag chatgpt.com
/pricingsignup_clickedsignup_completedSame-cohort ordered steps. Sample data, not a benchmark or evidence of causation.
WHAT TO INVESTIGATE
How a question gets answered
Add the event, confirm the outcome, then read where people leave.
After the rules collector is installed, configure click, form-submit and section-visible rules from your dashboard. New page loads pick them up.
See how tracking rules workUse custom events where signups or purchases actually succeed. Keep confirmed results distinct from button clicks and form submissions.
Build an ordered funnel from your recorded events. Compare completed steps and drop-offs to decide what to investigate next.
Referrers, countries, and campaigns sit next to the actions you recorded, so a source is something you can inspect.
Load visitor analytics, rule tracking, and performance timing independently. You only ship the surface you need.
On an eligible paid plan, with AI enabled for the app, ask about the traffic and events you already collected. Each answer includes the facts you can check.
Owleye Analytics is hosted web and product analytics for founders, developers, and small product teams. It tracks page views and product actions, then shows where visitors drop off in conversion funnels. Install page analytics first. If you want dashboard-managed clicks, install the rules collector once and point it at stable selectors. New page loads pick up rule changes. A click or form submit is not a completed signup: send a separate event where the signup actually succeeds, then put those steps in a funnel.
From your site to a useful answer
Public event ingestion stays separate from authenticated console APIs. High-volume analytics facts go to ClickHouse. Users, sites, rules, and other application metadata stay in SQLite.
Read the architectureManaged for you. Retention follows your plan.
SDK preview
Add one script tag with your Tracking ID to start recording page views. Use npm for a bundled app, and add custom events where product actions succeed. Load rules or performance tracking when you need them. Arbitrary query parameters stay excluded by default.
Your consent requirements depend on what you collect and how you use it. Read the privacy guide.
useAnalyticsvisitors + custom eventstrackRulesdeclarative interactionstrackPerfexplicit operation timing<script defer
src="https://cdn.jsdelivr.net/npm/@owleye/analytics@1.0.3/dist/owleye.analytics.iife.js"
data-owleye-id="your-tracking-id"
></script>Analytics alternatives
Compare dashboard events, funnel workflows, and reporting before you switch. Find the tool that fits the questions your team needs to answer.
Dashboard-managed events and funnels or the wider Google marketing ecosystem?
→Web analytics workflowsOwlEye vs PlausibleCompare how you define events, measure goals, and inspect drop-offs.
→Product analytics platformOwlEye vs PostHogA deliberately smaller stack or an expansive product engineering suite?
→Events and journey reportsOwlEye vs UmamiCompare dashboard rules, custom events, and funnel reports.
→Collection boundaries
The visitor script and the signed-in console do different jobs. These are the defaults: what the script can collect, and what it leaves alone.
Inspect every SDK optionUseful signals
Default boundaries
The authenticated team console uses secure session cookies. Visitor tracking does not. Same product, very different job descriptions.
Frequently asked questions
How tracking works, what you need to set up, and what to expect.
Owleye Analytics is hosted web and product analytics for founders, developers, and small product teams. It tracks page views and product actions, then shows where visitors drop off in conversion funnels.
Install the optional rules collector once and choose a stable selector for your button. Then add a click rule from your dashboard without redeploying for each new event; new page loads pick up the changes. If the page needs a new selector, that initial change requires a deploy. Track confirmed signups and purchases where they actually succeed.
Choose an ordered sequence of page views or named events. The funnel shows the recorded audience reaching each step and where it drops off within the supported window. It helps you choose what to investigate; it does not establish why an individual left.
OwlEye covers page views, traffic sources, custom events, and funnels. If those are the reports you need, it may suit you. Check the features and integrations you rely on before switching.
OwlEye's visitor tracking does not write cookies or save data in local or session storage. The OwlEye dashboard uses separate sign-in cookies to keep your team logged in.
No. OwlEye hosts the dashboard, receives your tracking events, and stores your analytics. You add OwlEye to your website and manage it from the dashboard.
OwlEye estimates visitors using part of their IP address and browser information, without saving an ID in their browser. Full IP addresses are not stored with analytics events. Counts are estimates: people sharing a network can be grouped together, and someone changing networks or browsers can count again.
When AI is available on an eligible paid plan and enabled for your app, you can ask questions about recorded traffic and events with supporting facts to check. Your question and relevant summaries go to an AI provider; avoid personal information or secrets.
Check our status page for service availability and incident updates. View service status
Your next product question
Start with page views, add one confirmed outcome, and build the funnel between them. Move to a paid plan when you need more events, projects, or history.