Overview
WalkerOS is built vendor-agnostically. While sources create events, destinations are built to manage how events are processed and sent to various analytics, marketing or data storage tools.
Destinations ensure that data captured from your website or application is best-organized to easily get integrated with different tools if proper consent was granted. This helps maintaining data quality and simplifying the setup of new tools.
How it works
Destinations are added to a source
(see walker.js
or node). Before
receiving events from the source, the proper consent states are checked each
time automatically. Destinations receive events through the
push interface. Each destination can
have its own configuration, which is set up in the
config object. This configuration
includes general settings for the destination and individual event settings. The
optional init function in a
destination gets called before actually pushing events. This function must
return true upon successful initialization for the events to be processed.
Categories
There are two types of destinations within walkerSO that destinations are categorized in: web and node.
Web
Like walker.js, web destinations run in the browser directly. Their purpose is to initialize, map event data to the vendors' requirements, and send them.
Node
Node destinations offer a flexible and efficient way to handle your server-side event data. Whether you're sending data to a cloud-based data warehouse or to a custom API, they make it easy to configure, initialize, and push your events securely.
If you can't find a destination, you can request it.
If you need professional support with your walkerOS implementation, check out our services.