Skip to content

Build with OwlEye

Facts reviewed:

Owleye Analytics shows where visitors drop off in a measured funnel, so you can choose what to investigate next. Install page analytics and the optional rules module once, add supported click, form-submit and section-visible events from your dashboard, then build a funnel to find the step that needs attention.

Begin with the quickstart. Rules need stable selectors; new tracker starts and page loads pick up saved changes. A submit event records an attempt, so send an explicit application event to confirm a completed signup.

Start with a Tracking ID from your app in the OwlEye console. The browser SDK connects to the hosted service automatically. You do not need an API key or a server URL for browser tracking.

Your site Guide
JavaScript or TypeScript app Quickstart: npm, pnpm, or Bun
Plain HTML, a CMS, or a site builder CDN script tag
WordPress WordPress installation
React or Next.js Client component setup
Vue or Nuxt Client lifecycle setup
Module Import Collects
Page analytics @owleye/analytics Initial page view, SPA navigation, page sessions, and explicit custom events
Tracking rules @owleye/analytics/rules Console-configured clicks, submissions, and element visibility
Performance @owleye/analytics/performance Opt-in Web Vitals estimates and named performance measurements

The SDK writes no cookies, local storage, or session storage. Arbitrary query parameters and URL fragments are excluded by default; SDK 1.0.3 automatically captures bounded campaign tags. Review the privacy and lifecycle controls before installing it.

Custom events accept 10 properties total, including global fields, with only string, finite-number, or boolean values. The CDN guide covers window.OwlEyeAnalytics.track(), custom data, campaigns, optional rules, and performance globals.

Create apps and manage your team, inspect traffic and events, build custom dashboards and funnels, or ask your data questions on an eligible paid plan when AI is enabled and available. Empty charts stay empty until real events arrive.

The API reference tab covers server-side event ingestion, scoped developer read keys, and eligible AI integrations. Secret keys belong on your server. For the data flow behind these features, see Architecture.