OwlEye, explained
Track the click. Find the drop-off.
Configure supported events from your dashboard after setup, connect them in ordered funnels, and investigate where your signup flow loses visitors.
Facts reviewed:
What can I do with Owleye Analytics?
Owleye Analytics helps founders, developers, and small product teams measure page visits and product actions, configure supported events from a dashboard, and inspect drop-off in ordered funnels. Add optional performance measurements to investigate slow pages. On eligible paid plans, ask supported analytics questions when AI is available and enabled. Start with recorded traffic and events; confirmed signups and purchases need explicit success events.
Add the event from your dashboard
Install page analytics and the optional rules entrypoint once. Owners and admins can then configure supported clicks, form submissions, and section-visibility events from the dashboard using stable selectors and bounded metadata. New page loads pick up rule changes.
If your button or form already has a stable selector, you can add a supported rule without another site deployment. If it does not, adding a selector still needs a site edit. Rules do not run arbitrary JavaScript or recover interactions that were never collected.
See which measured step loses visitors
Connect pageviews and named events in an ordered funnel. Choose the steps and conversion window, then inspect how the measured cohort moves from landing page to pricing, form, or signup completion. Use the drop-off at each step to decide what to investigate next.
Referrers and campaign context help you compare acquisition sources where data is available. A funnel describes the actions you recorded; it cannot prove what someone thought or why they left.
Ask a supported question. Check the evidence.
When available on an eligible paid plan and enabled for the app, the AI analyst answers supported questions about recorded traffic, funnels, campaigns, performance, and visible-page segments. Inspect the supporting data and the limits of each answer before making a decision.
The analyst uses scoped, read-only reports. It cannot run arbitrary SQL or change your app. Each completed analytics question or Growth review uses one shared AI credit, including optional public competitor research within a review. Clarifications, rejected requests, and failed requests consume no credits.
Add application context when you need it
Use analytics.track() for events that need application context, such as a completed export. Send up to ten primitive custom fields in total, including global fields. Use a site-scoped secret ingestion key with events:write permission for server-originated events and keep that secret out of browser code.
SDK reference · Developer access
Keep the collection focused
Page analytics, rules, and explicit performance timing have separate entrypoints. The runtime package has no third-party dependencies. Loading more features adds bytes; a core-only size is not a price tag for the whole toolkit.
Explore pageviews, visitor estimates, referrers, countries, and named events alongside the funnel. Add optional Web Vitals collection when you need performance measurements to investigate a slow page.
The visitor SDK writes no cookies or browser storage. It captures five bounded UTM campaign fields automatically; arbitrary URL query parameters and fragments are excluded by default. Visitor estimates use site-scoped pseudonyms, not an identity register. Your configuration and the data you choose to send still matter.
Start free with 10,000 billable events per month.