Welcome to walkerOS
walkerOS is a unified, privacy-centric data collection platform that creates a single source of truth for data, marketing and product teams. It offers features like data capturing, consent management, data integration, and tag management enabling full data ownership. The project started as a web library called walker.js and has evolved into a complete first-party tracking system.
Why walkerOS?
- Sustainability: A robust infrastructure for continuous data collection, even amidst evolving data landscapes.
- Privacy focus: Emphasizing user privacy, with a strict privacy-by-design approach, in-build consent management and various data protection features.
- Complete data ownership: Gain full control with your first-party data, avoid vendor lock-in and control data processing.
- Simplified data model: The intuitive event model streamlines data collection, making analytics straightforward and efficient.
- Flexible architecture: Adapt walkerOS to your specific data needs with the modular design and grow step-by-step.
How walkerOS operates
walkerOS is a streamlined framework with one standardized Event model. Components are designed to always be extensible for a steadily growing data journey.
Basic infrastructure
- Sources: Event collection and state management with complete control.
- Destinations: Data activation by initializing, mapping and then sharing events to third-party tools.
- Utils: Supporting helper function to standardize and improve data collection.
Complete infrastructure
Example event journey
- a: The walker.js integrates with the website, initializes event listeners and interprets the tagging on the page.
- b: The walker.js ensures a user granted consent, eventually initializes and maps events appropriately before pushing them to destinations.
- c: Events are formatted correctly and get sent directly to the respective tools from the source.
- d: Events can be sent to a (public) endpoint from various sources, running a Source Node
- f: Similar to client-side operations, consent gets verified, a destination eventually initialized, and event preparation are processed server-side.
- g: Events are formatted correctly and sent to tools from the server.
info
If you need professional support with your walkerOS implementation, check out our services.