Destinations

Destinations are the endpoints where walkerOS sends your processed events. They transform standardized walkerOS events into the specific formats required by analytics platforms, marketing tools, data warehouses, and custom APIs.

Each destination operates independently, so one failed destination won't affect others.

Analytics tools

Destination	Web	Server
Amplitude	Yes	Yes
Clarity	Yes	-
GA4	Yes	-
GTM	Yes	-
Mixpanel	Yes	Yes
Piwik PRO	Yes	-
Plausible	Yes	-
PostHog	Yes	Yes
Segment	Yes	Yes
Snowplow	Yes	-

Marketing tools

	Web	Server
Google	Google Ads	Google Data Manager
LinkedIn	LinkedIn Insight Tag	LinkedIn Conversions API
Meta	Meta Pixel	Meta Conversions API
Pinterest	Pinterest Tag	Pinterest Conversions API
TikTok	TikTok Pixel	TikTok Events API

Data warehouses

Destination	Web	Server
API	Yes	Yes
AWS Firehose	-	Yes
GCP BigQuery	-	Yes

Create your own

Build a custom destination for any endpoint. See Create your own destination for a step-by-step guide.

Configuration

These fields are available on every destination, regardless of package. They wrap the package-specific settings field, which is documented on each destination's page.

Property	Type	Description	More
consent	WalkerOS.Consent	Required consent states to send events to this destination
data	Mapping.Value | Mapping.Value[]	Global data transformation applied to all events for this destination
include	Array<string>	Event sections to flatten into context.data
env	any	Environment dependencies (platform-specific)
id	string	Destination instance identifier (defaults to destination key)
loadScript	boolean	Whether to load external script (for web destinations)
mapping	Record<string, object>	Entity-action specific mapping rules for this destination
policy	Record<string, Mapping.Value>	Pre-processing policy rules applied before event mapping
queue	boolean	Whether to queue events when consent is not granted
require	Array<string>	Defer destination initialization until these collector events fire (e.g., ["consent"])
logger	object	Logger configuration (level, handler) to override the collector defaults
before	__schema0	Post-collector transformer chain applied before this destination receives the event
next	__schema0	Post-push transformer chain. Runs after destination push completes; push response is available at ingest._response
cache	object	Cache configuration for deduplication; skip push on cache HIT
disabled	boolean	Completely skip this destination (no init, no push, no queue)