Skip to main content
The Orwel SDK (orwel on npm, current version 1.7.1) tracks visits, sessions, events and conversions, resolves a stable visitor id, and carries first and last touch attribution. Drop it into any site or app: it captures behavior automatically and powers personalities, journeys, feature adoption and leads, all in one workspace.
Looking for copy and paste steps for your stack? See Install by framework or orwel.io/install.

​
Installation

​
Initialization

Initialize the SDK once, at the root of your application (e.g. App.tsx, main.js), before any tracking call.
The SDK key is the production API key: it can only send data, so it is safe in the browser bundle. Read it from an environment variable anyway, so production uses the production API key and development uses the development key. Reading data needs a separate API key.

​
What you can do

Event Tracking

Automatic capture, custom events, and the semantic catalog.

Feature Tracking

Map events to features and measure adoption.

Conversions

Capture leads and goals, attributed across sessions.

Attribution

UTMs and ad click ids, first and last touch.

CDN & Infrastructure

How the SDK is distributed and how events reach the server.

SDK Reference

Every method and init option.

​
Core methods

​
Identify

Associate a visitor with traits. Call when a user logs in or updates their profile.

​
Track

Record a named event. The code must exist in your workspace catalog (see Event Tracking).

​
Conversion

Record a high-value outcome, enriched into a lead. conversion() is async: it waits for the visitor id to resolve, sends the conversion with its attribution, and resolves with the result the server acknowledged.

​
Session

Update session properties.