PostHog

Server Source code Package

Server-side event delivery to PostHog for product analytics, identity resolution, group analytics, and feature flags via the official posthog-node SDK.

Where This Fits

PostHog is a server destination in the walkerOS flow:

Sends events server-side to PostHog's ingestion API, translating walkerOS events into capture, identify, and groupIdentify calls with full control over identity and group resolution.

Installation

Setup

Integrated
Bundled

Add to your flow.json destinations:

See Bundled Mode setup → | CLI reference →

Configuration reference

Property	Type	Description
`apiKey*`	`string`	PostHog project API key (starts with "phc_"). Find it in PostHog project settings.
`host`	`string`	PostHog API host. Defaults to https://us.i.posthog.com. Use https://eu.i.posthog.com for EU or your self-hosted URL.
`flushAt`	`number`	Number of events queued before auto-flush. Default: 20.
`flushInterval`	`number`	Milliseconds between periodic flushes. Default: 10000.
`personalApiKey`	`string`	Personal API key (phx_...) for local feature flag evaluation.
`featureFlagsPollingInterval`	`number`	Milliseconds between feature flag definition polls. Default: 30000.
`disableGeoip`	`boolean`	Disable GeoIP lookups globally. Useful for GDPR compliance.
`debug`	`boolean`	Enable PostHog SDK debug logging. Default: false.
`identify`	`any`	walkerOS mapping value resolving to an identity object. Keys: distinctId, $set, $set_once. Resolved on every push (server is stateless).
`group`	`any`	walkerOS mapping value resolving to a group object. Keys: type, key, properties. Resolved on every push.
`include`	`Array<string>`	Event sections to flatten into capture() properties (e.g. ["data", "globals"]).

* Required fields

Docker Deployment

Step 1: Create Flow Configuration

Use the $env.NAME syntax in your flow configuration to reference environment variables at runtime:

Step 2: Bundle the Flow

Bundle your flow configuration before running in Docker:

Step 3: Run with Docker

Docker Compose Example

Security Best Practice

Never commit API keys to version control. Use environment variables or a secrets manager to inject credentials at runtime.

💡 Need implementation support?

elbwalker offers hands-on support: setup review, measurement planning, destination mapping, and live troubleshooting. Book a 2-hour session (€399)

Installation​

Setup​

Configuration reference​

Docker Deployment​

Step 1: Create Flow Configuration​

Step 2: Bundle the Flow​

Step 3: Run with Docker​

Docker Compose Example​