Skip to main content

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.

Source
Collector
Destination
GA4
Destination
API
External
Google Analytics
External
Custom Endpoint
12
1Receive: Mapped events from collector ready for delivery2Deliver: Tool-specific API calls, SDK initialization, and event dispatch

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

Analytics tools

DestinationWebServer
AmplitudeYesYes
ClarityYes-
GA4Yes-
GTMYes-
MixpanelYesYes
Piwik PROYes-
PlausibleYes-
PostHogYesYes
SegmentYesYes
SnowplowYes-

Marketing tools

WebServer
GoogleGoogle AdsGoogle Data Manager API
LinkedInLinkedIn Insight TagLinkedIn Conversions API
MetaMeta PixelMeta Conversions API
PinterestPinterest TagPinterest Conversions API
TikTokTikTok PixelTikTok Events API

Data warehouses

DestinationWebServer
APIYesYes
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.

PropertyTypeDescriptionMore
consentWalkerOS.ConsentRequired consent states to send events to this destination
settingsDestination.SettingsImplementation-specific configuration
dataany | anyGlobal data transformation applied to all events for this destination
includeArray<string>Event sections to flatten into context.data
envDestination.EnvEnvironment dependencies (platform-specific)
idstringDestination instance identifier (defaults to destination key)
initbooleanWhether to initialize immediately
loadScriptbooleanWhether to load external script (for web destinations)
mappingMapping.RulesEntity-action specific mapping rules for this destination
policyMapping.PolicyPre-processing policy rules applied before event mapping
queuebooleanWhether to queue events when consent is not granted
requireArray<string>Defer destination initialization until these collector events fire (e.g., ["consent"])
loggerLogger.Config
setupboolean | objectOne-time setup options applied during destination registration (boolean enables defaults, object configures specifics)
beforeRouteWithoutManyPost-collector transformer chain applied before this destination receives the event. `many` is not valid here — use multiple destinations for post-collector fan-out.
nextRouteWithoutManyPost-push transformer chain. Runs after destination push completes; push response is available at ingest._response. `many` is not valid here — use multiple destinations for post-collector fan-out.
cacheEventCache.ConfigCache configuration for deduplication; skip push on cache HIT
stateState.Config | State.Config[]Declarative store get/set operations applied around this destination
disabledbooleanCompletely skip this destination (no init, no push, no queue)
mockDestination.Mock
queueMaxnumberMaximum consent-denied events retained in queuePush for this destination. FIFO drop on overflow. Default 1000.
dlqMaxnumberMaximum failed-push entries retained in dlq for this destination. FIFO drop on overflow. Default 100.
batchnumber | objectBatch scheduling: bare number is the debounce wait window (legacy); object form supports wait (debounce ms), size (count cap, default 1000), age (max ms since first entry, default 30000).
💡 Need implementation support?
elbwalker offers hands-on support: setup review, measurement planning, destination mapping, and live troubleshooting. Book a 2-hour session (€399)