Chapter 47 · Instrument Integration
Subchapter 47.49
references/node.mdMarkdown27 KBView on GitHub
If you’re working with Node.js (versions 20+), the official posthog-node library is the simplest way to integrate your software with PostHog. This library uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your web app or other server-side application that needs performance. And in addition to event capture, are supported as well.
Run either npm or yarn in terminal to add it to your project:
PostHog AI
npm install posthog-node --saveyarn add posthog-nodepnpm add posthog-nodebun add posthog-nodeIn your app, set your project token before making any calls.
Node.js
PostHog AI
import { PostHog } from 'posthog-node'
const client = new PostHog(
'<ph_project_token>',
{ host: 'https://us.i.posthog.com' }
)
await client.shutdown()You can find your project token and instance address in the project settings (opens in a new tab) page in PostHog.
Note: As a rule of thumb, we do not recommend hardcoding API keys or tokens. Setting it as an environment variable is preferred.
Identifying users is required. Backend events need a
distinct_idthat matches the ID your frontend uses when callingposthog.identify(). Without this, backend events are orphaned — they can’t be linked to frontend event captures, session replays (opens in a new tab), LLM traces (opens in a new tab), or error tracking (opens in a new tab).See our guide on identifying users (opens in a new tab) for how to set this up.
| Variable | Description | Default value |
|---|---|---|
| host | Your PostHog host | https://us.i.posthog.com/ (opens in a new tab) |
| flushAt | After how many capture calls we should flush the queue (in one batch) | 20 |
| flushInterval | After how many ms we should flush the queue | 10000 |
| personalApiKey | An optional personal API key (opens in a new tab) for evaluating feature flags locally. Note: Providing this will trigger periodic calls to the feature flags service, even if you’re not using feature flags. | null |
| featureFlagsPollingInterval | Interval in milliseconds specifying how often feature flags should be fetched from the PostHog API | 300000 |
| requestTimeout | Timeout in milliseconds for any calls | 10000 |
| maxCacheSize | Maximum size of cache that deduplicates $feature_flag_called calls per user. | 50000 |
| disableGeoip | When true, disables automatic GeoIP resolution for events and feature flags. | true |
| evaluation_contexts | Evaluation context tags that constrain which feature flags are evaluated. When set, only flags with matching evaluation context tags (or no evaluation context tags) will be returned. This helps reduce unnecessary flag evaluations and improves performance. See evaluation contexts documentation (opens in a new tab) for more details. Available in version 5.10.0+. The legacy parameter evaluation_environments (version 5.9.6+) is also supported for backward compatibility. | undefined |
Note: When using PostHog in an AWS Lambda function or a similar serverless function environment, make sure you set
flushAtto1andflushIntervalto0. Also, remember to always callawait posthog.shutdown()at the end to flush and send all pending events.
You can send custom events using capture:
Node.js
PostHog AI
client.capture({
distinctId: 'distinct_id_of_the_user',
event: 'user signed up',
})Tip: We recommend using a
[object] [verb]format for your event names, where[object]is the entity that the behavior relates to, and[verb]is the behavior itself. For example,project created,user signed up, orinvite sent.
Optionally, you can include additional information with the event by including a properties (opens in a new tab) object:
Node.js
PostHog AI
client.capture({
distinctId: 'distinct_id_of_the_user',
event: 'user signed up',
properties: {
login_type: 'email',
is_free_trial: true,
},
})If you’re aiming for a backend-only implementation of PostHog and won’t be capturing events from your frontend, you can send $pageview events from your backend like so:
Node.js
PostHog AI
client.capture({
distinctId: 'distinct_id_of_the_user',
event: '$pageview',
properties: {
$current_url: 'https://example.com',
},
})The Node SDK captures identified events by default. These create person profiles (opens in a new tab). To set person properties (opens in a new tab) in these profiles, include them when capturing an event using $set and $set_once:
Node.js
PostHog AI
client.capture({
distinctId: 'distinct_id_of_the_user',
event: 'movie_played',
properties: {
$set: { name: 'Max Hedgehog' },
$set_once: { initial_url: '/blog' },
},
})For more details on the difference between $set and $set_once, see our person properties docs (opens in a new tab).
To capture anonymous events (opens in a new tab) without person profiles, set the event’s $process_person_profile property to false:
Node.js
PostHog AI
client.capture({
distinctId: 'distinct_id_of_the_user',
event: 'movie_played',
properties: {
$process_person_profile: false,
},
})Sometimes, you want to assign multiple distinct IDs to a single user. This is helpful when your primary distinct ID is inaccessible. For example, if a distinct ID used on the frontend is not available in your backend.
In this case, you can use alias to assign another distinct ID to the same user.
Node.js
PostHog AI
client.alias({
distinctId: 'distinct_id',
alias: 'alias_id',
})We strongly recommend reading our docs on alias (opens in a new tab) to best understand how to correctly use this method.
Requires
posthog-nodeversion >= 5.25.0.
Super properties are properties that are automatically included with every event captured by the client. Use register to set them:
Node.js
PostHog AI
client.register({
app_version: '1.2.0',
environment: 'production',
})
// Both events include app_version and environment
client.capture({
distinctId: 'distinct_id',
event: 'page_viewed',
})
client.capture({
distinctId: 'distinct_id',
event: 'button_clicked',
})If an event sets a property with the same key as a super property, the event’s property takes precedence:
Node.js
PostHog AI
client.register({ environment: 'production' })
// This event is captured with environment='staging'
client.capture({
distinctId: 'distinct_id',
event: 'page_viewed',
properties: { environment: 'staging' },
})To remove a super property, use unregister:
Node.js
PostHog AI
client.unregister('environment')Super properties are global — they apply to every event for the lifetime of the client instance. For properties that should only apply to a specific scope (e.g. a single request or transaction), use contexts instead.
Requires
posthog-nodeversion >= 5.17.0.
The Node SDK uses nested contexts for managing state that’s shared across events. Contexts are useful for adding properties to multiple events (including exceptions) during a single user’s interaction with your product.
You can enter a context using withContext:
Node.js
PostHog AI
posthog.withContext(
{
distinctId: 'user-123',
properties: { transactionId: 'abc123' }
},
() => {
// This event is captured with the distinct ID and properties set above
posthog.capture({ event: 'order_processed' })
}
)Contexts are persisted across function calls. If you enter one and then call a function and capture an event in the called function, it uses the context properties set in the parent context:
Node.js
PostHog AI
function someFunction() {
// When called from `outerFunction`, this event is captured
// with transactionId='abc123'
posthog.capture({ event: 'order_processed' })
}
function outerFunction() {
posthog.withContext(
{ properties: { transactionId: 'abc123' } },
() => {
someFunction()
}
)
}By default, each context inherits from parent contexts. To disable nesting (where child contexts is fresh and has no properties), pass { fresh: true }:
Node.js
PostHog AI
posthog.withContext(
{
properties: {
someKey: 'value-1',
someOtherKey: 'another-value'
}
},
() => {
posthog.withContext(
{ properties: { someKey: 'value-2' } },
() => {
// Captured with someKey='value-2', someOtherKey='another-value'
posthog.capture({ event: 'order_processed' })
},
)
// Captured with someKey='value-1', someOtherKey='another-value'
posthog.capture({ event: 'order_completed' })
}
)Note: Properties passed directly to
capturecalls override context state in the final event.
Contexts can be associated with a distinct ID:
Node.js
PostHog AI
posthog.withContext(
{ distinctId: 'user-123' },
() => {
// Associated with "user-123"
posthog.capture({ event: 'order_processed' })
// Overrides to "another-user"
posthog.capture({
distinctId: 'another-user',
event: 'order_processed'
})
}
)Node.js
PostHog AI
posthog.withContext(
{ sessionId: 'some-session' },
() => {
// Associated with session "some-session"
posthog.capture({ event: 'image_uploaded' })
// Overrides to "next-session"
posthog.capture({
event: 'image_uploaded',
properties: { $sessionId: 'next-session' }
})
}
)Node.js
PostHog AI
posthog.withContext(
{ flightNumber: 'TAC313' },
() => {
// Associated with flightNumber TAC313
posthog.capture({ event: 'flight_cancelled' })
// Overrides to PL7714
posthog.capture({
event: 'flight_cancelled',
properties: { flightNumber: 'PL7714' }
})
}
)PostHog’s feature flags (opens in a new tab) enable you to safely deploy and roll back new features as well as target specific users and groups with them.
There are two steps to implement feature flags in Node:
Call client.evaluateFlags() once for the user, then read values from the returned snapshot.
Node.js
PostHog AI
const flags = await client.evaluateFlags('distinct_id_of_your_user')
if (flags.isEnabled('flag-key')) {
// Do something differently for this user
// Optional: fetch the payload
const matchedFlagPayload = flags.getFlagPayload('flag-key')
}Node.js
PostHog AI
const flags = await client.evaluateFlags('distinct_id_of_your_user')
const enabledVariant = flags.getFlag('flag-key')
if (enabledVariant === 'variant-key') { // replace 'variant-key' with the key of your variant
// Do something differently for this user
// Optional: fetch the payload
const matchedFlagPayload = flags.getFlagPayload('flag-key')
}flags.getFlag() returns the variant string for multivariate flags, true for enabled boolean flags, false for disabled flags, and undefined when the flag wasn’t returned by the evaluation.
Note:
client.isFeatureEnabled(),client.getFeatureFlag(),client.getFeatureFlagPayload(), andcapture({ sendFeatureFlags: true })still work during the migration period, but they’re deprecated. PreferevaluateFlags()for new code.
If you want use your feature flag to breakdown or filter events in your insights (opens in a new tab), you’ll need to include feature flag information in those events. This ensures that the feature flag value is attributed correctly to the event.
Note: This step is only required for events captured using our server-side SDKs or API (opens in a new tab).
There are two methods you can use to include feature flag information in your events:
Pass the same flags object that you used for branching. This attaches the exact flag values from that evaluation and doesn’t make another /flags request.
Node.js
PostHog AI
const flags = await client.evaluateFlags('distinct_id_of_your_user')
if (flags.isEnabled('flag-key')) {
// Do something differently for this user
}
client.capture({
distinctId: 'distinct_id_of_your_user',
event: 'event_name',
flags,
})By default, this attaches every flag in the snapshot using $feature/<flag-key> properties and $active_feature_flags.
To reduce event property bloat, pass a filtered snapshot:
Node.js
PostHog AI
// Attach only flags accessed with isEnabled() or getFlag() before this call
client.capture({
distinctId: 'distinct_id_of_your_user',
event: 'event_name',
flags: flags.onlyAccessed(),
})
// Attach only specific flags
client.capture({
distinctId: 'distinct_id_of_your_user',
event: 'event_name',
flags: flags.only(['checkout-flow', 'new-dashboard']),
})onlyAccessed() is order-dependent. If you call it before accessing any flags with isEnabled() or getFlag(), no feature flag properties are attached.
In the event properties, include $feature/feature_flag_name: variant_key:
Node.js
PostHog AI
client.capture({
distinctId: 'distinct_id_of_your_user',
event: 'event_name',
properties: {
// Replace feature-flag-key with your flag key and 'variant-key' with the key of your variant
'$feature/feature-flag-key': 'variant-key',
},
})By default, evaluateFlags() evaluates every flag for the user. If you only need a few flags, pass flagKeys to request only those flags:
Node.js
PostHog AI
const flags = await client.evaluateFlags('distinct_id_of_your_user', {
flagKeys: ['checkout-flow', 'new-dashboard'],
})Capturing $feature_flag_called events enables PostHog to know when a flag was accessed by a user and provide analytics and insights (opens in a new tab) on the flag. With evaluateFlags(), the SDK sends this event when you call flags.isEnabled() or flags.getFlag() for a flag.
The SDK deduplicates these events per (distinct_id, flag, value) in a local cache. If you reinitialize the PostHog client, the cache resets and $feature_flag_called events may be sent again. PostHog handles duplicates, so duplicate $feature_flag_called events don’t affect your analytics.
flags.getFlagPayload() doesn’t send $feature_flag_called events and doesn’t count as an access for onlyAccessed().
Sometimes, you may want to evaluate feature flags using person properties (opens in a new tab), groups (opens in a new tab), or group properties that haven’t been ingested yet, or were set incorrectly earlier.
You can provide properties to evaluate the flag with by using the person properties, groups, and group properties arguments. PostHog will then use these values to evaluate the flag, instead of any properties currently stored on your PostHog server.
For example:
Node.js
PostHog AI
const flags = await client.evaluateFlags('distinct_id_of_the_user', {
personProperties: {
property_name: 'value',
},
groups: {
your_group_type: 'your_group_id',
another_group_type: 'your_group_id',
},
groupProperties: {
your_group_type: {
group_property_name: 'value',
},
another_group_type: {
group_property_name: 'value',
},
},
})
if (flags.isEnabled('flag-key')) {
// Do something differently for this user
}By default, a user’s GeoIP properties are set using the IP address they use to capture events on the frontend. You may want to override the these properties when evaluating feature flags. A common reason to do this is when you’re not using PostHog on your frontend, so the user has no GeoIP properties.
You can override GeoIP properties by including them in the person_properties parameter when evaluating feature flags. This is useful when you’re evaluating flags on your backend and want to use the client’s location instead of your server’s location.
The following GeoIP properties can be overridden:
$geoip_country_code$geoip_country_name$geoip_city_name$geoip_city_confidence$geoip_continent_code$geoip_continent_name$geoip_latitude$geoip_longitude$geoip_postal_code$geoip_subdivision_1_code$geoip_subdivision_1_name$geoip_subdivision_2_code$geoip_subdivision_2_name$geoip_subdivision_3_code$geoip_subdivision_3_name$geoip_time_zoneSimply include any of these properties in the person_properties parameter alongside your other person properties when calling feature flags.
You can configure the feature_flag_request_timeout_ms parameter when initializing your PostHog client to set a flag request timeout. This helps prevent your code from being blocked if PostHog’s servers are too slow to respond. By default, this is set to 3 seconds.
JavaScript
PostHog AI
const client = new PostHog('<ph_project_token>', {
api_host: 'https://us.i.posthog.com',
feature_flag_request_timeout_ms: 3000, // Time in milliseconds. Defaults to 3000 (3 seconds).
})Note: For remote config flags, see the remote config documentation (opens in a new tab). Remote config requires the Feature Flags secure API key (opens in a new tab) passed as the
personalApiKeyoption.
Evaluating feature flags requires making a request to PostHog for each flag. However, you can improve performance by evaluating flags locally. Instead of making a request for each flag, PostHog will periodically request and store feature flag definitions locally, enabling you to evaluate flags without making additional requests.
It is best practice to use local evaluation flags when possible, since this enables you to resolve flags faster and with fewer API calls.
For details on how to implement local evaluation, see our local evaluation guide (opens in a new tab).
Node.js
PostHog AI
const flags = await client.evaluateFlags('user distinct id', {
groups: { organization: 'google' },
groupProperties: { organization: { is_authorized: true } },
})
const flagValue = flags.getFlag('flag-key')When initializing PostHog, you can configure the interval at which feature flags are polled (fetched from the server). However, if you need to force a reload, you can use reloadFeatureFlags:
Node.js
PostHog AI
await client.reloadFeatureFlags()
// Do something with feature flags hereIn multi-worker or edge environments, you can implement custom caching for flag definitions using Redis, Cloudflare KV, or other storage backends. This enables sharing definitions across workers and coordinating fetches. See our guide for local evaluation in distributed environments (opens in a new tab) for details.
Since experiments (opens in a new tab) use feature flags, the code for running an experiment is very similar to the feature flags code:
Node.js
PostHog AI
const flags = await client.evaluateFlags('user_distinct_id')
const variant = flags.getFlag('experiment-feature-flag-key')
if (variant === 'variant-name') {
// Do something
}It’s also possible to run experiments without using feature flags (opens in a new tab).
Group analytics enable you to associate an event with a group (e.g. teams, organizations, etc.). Read the group analytics guide (opens in a new tab) for more information.
To create a group or update its properties, use groupIdentify:
Node.js
PostHog AI
client.groupIdentify({
groupType: 'company',
groupKey: 'company_id_in_your_db',
properties: {
name: 'Awesome Inc',
employees: 11,
},
// optional distinct ID to associate event with an existing person
distinctId: 'xyz'
})name is a special property which is used in the PostHog UI for the name of the group. If you don’t specify a name property, the group ID is used instead.
If the optional distinctId parameter is not provided in the group identify call, it defaults to ${groupType}_${groupKey} (e.g., $company_company_id_in_your_db in the example above). This default behavior results in each group appearing as a separate person in PostHog. To avoid this, it’s often more practical to use a consistent distinctId, such as group_identifier.
Once a group is created, you can use the capture method and pass in the groups parameter to capture an event with group analytics.
Node.js
PostHog AI
client.capture({
event: 'some_event',
distinctId: 'user_distinct_id',
groups: { company: 'company_id_in_your_db' },
})Before posthog-node v3.0, we added GeoIP properties to all incoming events by default. We also used these properties for feature flag evaluation, based on the IP address of the request. This isn’t ideal since they are created based on your server IP address, rather than the user’s, leading to incorrect location resolution.
As of posthog-node v3.0, the default now is to disregard the server IP, not add the GeoIP properties, and not use the values for feature flag evaluations.
You can go back to previous behavior by setting disableGeoip to false in your initialization:
Node.js
PostHog AI
const posthog = new PostHog('<ph_project_token>', {
host: 'https://us.i.posthog.com',
disableGeoip: false
})The list of properties that this overrides:
$geoip_city_name$geoip_country_name$geoip_country_code$geoip_continent_name$geoip_continent_code$geoip_postal_code$geoip_time_zoneYou can also explicitly chose to enable or disable GeoIP for a single capture request like so:
Node.js
PostHog AI
client.capture({
distinctId: distinctId,
event: 'your_event',
disableGeoip: `true`,
})You should call shutdown on your program’s exit to exit cleanly:
Node.js
PostHog AI
// Stop pending pollers and flush any remaining events
await client.shutdown()If you’re not seeing the expected events being captured, the feature flags being evaluated, or the surveys being shown, you can enable debug mode to see what’s happening.
You can enable debug mode by calling the debug() method in your code. This will enable verbose logs about the inner workings of the SDK.
Node.js
PostHog AI
client.debug()If you are experiencing issues with the SDK it could be a number of things from an incorrectly configured API key, to some other network related issues.
The SDK does not throw errors for things happening in the background to ensure it doesn’t affect your process. You can however hook into the errors to get more information:
Node.js
PostHog AI
client.on("error", (err) => {
// Whatever handling you want
console.error("PostHog had an error!", err)
})The Node SDK is designed to queue and batch requests in the background to optimize API calls and network time. As serverless environments like AWS Lambda or Vercel Functions (opens in a new tab) are short-lived, we provide a few options to ensure all events are captured.
First, we recommend using the captureImmediate method instead of capture to ensure the event is captured before the function shuts down. It guarantees the HTTP request finishes before your function continues (or shuts down).
Second, we recommend setting flushAt to 1 and flushInterval to 0 to ensure the events are sent immediately. These set the queue to flush immediately, both in terms of events and time.
Third, we provide a method shutdown() which can be awaited to ensure all queued events are sent to the API. For example:
Node.js
PostHog AI
export const handler() {
client.capture({
distinctId: 'distinct_id_of_the_user',
event: 'thing_happened'
})
client.capture({
distinctId: 'distinct_id_of_the_user',
event: 'other_thing_happened'
})
// So far 2 events are queued but not sent
// Calling shutdown, flushed the queue but batched into 1 API call for maximum efficiency
await client.shutdown()
}This is also useful for shutting down a standard Node.js app.
You can capture LLM usage and performance data by combining the posthog-node and @posthog/ai libraries. These work with LLM providers like OpenAI and Vercel’s AI SDKs. Learn more in our AI Observability docs (opens in a new tab).
You can capture errors using the posthog-node library. This enables you to see stack traces, source code, and watch associated session recordings to improve your application stability. Learn more in our error tracking docs (opens in a new tab).
V2.x.x of the Node.js library is completely rewritten in Typescript and is based on a new JS core shared with other JavaScript based libraries with the goal of ensuring new features and fixes reach the different libraries at the same pace.
With the release of V2, the API was kept mostly the same but with some small changes and deprecations:
callback parameter passed as an optional last argument to most of the methods is no longer supportedisFeatureEnabled and getFeatureFlag is slightly modified. See the above documentation for each method for more details.Ask a question
HelpfulCould be better