Amplitude

Server Source code Package

Server-side event delivery to Amplitude for product analytics, using the official @amplitude/analytics-node SDK. Supports track, identify, revenue, setGroup, groupIdentify, and flush calls with per-event identity via EventOptions.

Where This Fits

Amplitude is a server destination in the walkerOS flow:

Sends events server-side to Amplitude's HTTP API, providing reliable delivery with identity resolution, revenue tracking, and group analytics without browser-side SDK overhead.

Installation

Setup

Integrated
Bundled

Add to your flow.json destinations:

See Bundled Mode setup → | CLI reference →

Configuration reference

Property	Type	Description
`apiKey*`	`string`	Your Amplitude project API key. Find it in your Amplitude project settings under "General" -> "API Keys".
`serverZone`	`'US' \| 'EU'`	Amplitude data residency zone. Use EU for European data residency. Default: US.
`flushIntervalMillis`	`integer`	How often (in ms) to flush the event queue. Default: 10000.
`flushQueueSize`	`integer`	Max queued events before a flush. Default: 200.
`flushMaxRetries`	`integer`	Max retries on failed flush. Default: 12.
`useBatch`	`boolean`	Use the Amplitude batch endpoint for higher rate limits. Recommended for high-volume server flows. Default: false.
`minIdLength`	`integer`	Minimum length for user_id and device_id fields.
`serverUrl`	`string`	Custom server URL for proxies or self-hosted endpoints.
`optOut`	`boolean`	Initial opt-out state. When true, no events are sent. Default: false.
`enableRequestBodyCompression`	`boolean`	Enable gzip compression for request payloads. Default: false.
`identify`	`any`	walkerOS mapping value resolving to per-event identity. Keys: user_id, device_id, session_id, set, setOnce, add, append, prepend, preInsert, postInsert, remove, unset, clearAll.
`eventOptions`	`any`	walkerOS mapping value resolving to per-event EventOptions. Keys: time, insert_id, ip, city, country, region, language, platform, os_name, os_version, device_brand, device_model, app_version, user_agent.
`include`	`Array<string>`	walkerOS event sections to include as event_properties (like ['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​