Overview
The Node.js SDK is designed for server-side tracking where you have user identity. It supports:- Identified tracking - Use
emailoruserIdfor user-scoped resolution - Customer attribution - Add
customerIdfor account/workspace context, even before a user is known - Efficient batching - Events are queued and sent in batches
- Device tracking - Use
fingerprintfor desktop/mobile apps (learn more)
Use server-side tracking for events that happen in your backend: subscription changes, feature usage from APIs, background jobs, etc.
Installation
Quick Start
Configuration
Options
Your organization’s public key.
API endpoint for sending events.
How often to automatically flush events (milliseconds).
Maximum events per batch before auto-flush.
HTTP request timeout in milliseconds.
API Reference
outlit.track(options)
Track a custom event for a user, a customer, or both.
User’s email address. Resolves immediately to a customer profile.
Your system-owned user/contact ID.
Device identifier for anonymous tracking. See Device Tracking.
Your system-owned customer/account/workspace ID.
Name of the event. Use
snake_case.Additional data to attach to the event.
Unix timestamp in milliseconds. Defaults to current time.
At least one of
email, userId, fingerprint, or customerId is required for track(). customerId-only events are valid immediately and can later link to a resolved customer when identify() uses the same customerId with an email.outlit.identify(options)
Update user traits without tracking an event. Customer metadata can be included alongside the user identity.
User’s email address. Use this or
userId to establish user-scoped identity.Your system-owned user/contact ID.
Device identifier for linking anonymous events. See Device Tracking.
Properties to update on the user profile.
Your system-owned customer/account/workspace ID. Send this with
email or userId to link the account/workspace to the resolved contact profile.Properties to update on the customer profile.
At least one of
email or userId is required for identify(). Customer fields are optional additions.Lifecycle and billing
Send ordinary product facts withtrack(). For activation, choose the ordinary event that represents your product’s value milestone and track it after the action succeeds:
Outlit Core derives activation from the customer-selected ordinary event and derives engagement and inactivity from activity. Billing status comes from verified integrations such as Stripe. See Customer Journey.
outlit.flush()
Immediately send all queued events. Call this before your process exits.
outlit.shutdown()
Gracefully shutdown: flushes remaining events and stops the timer.
outlit.queueSize
Get the number of events waiting to be sent.
Framework Examples
Express.js
Next.js API Routes
Serverless Functions (AWS Lambda, Vercel)
Stripe Webhooks
Connect Stripe as a verified Outlit integration. Subscription state then updates account billing status automatically; do not translate Stripe webhooks into authoritative SDK billing commands.
Background Jobs (Bull, Agenda)
Common Events to Track
Here are recommended server-side events:Error Handling
The SDK silently handles errors to not disrupt your application. For debugging:TypeScript Support
Full TypeScript support is included:Next Steps
Identity Resolution
Learn how profiles are merged across sources
Customer Journey
Understand contact stages and account billing