elbwalker/walkerOS

What it solves

walkerOS provides a unified collection layer for event tracking, replacing the need for multiple separate setups for GA4, ad pixels, and custom tags. It solves the problem of inconsistent data across different platforms and the difficulty of tracking where events break in the fragmented tracking landscape.

How it works

It operates as a processing engine that manages the flow of events from sources to destinations.

• Sources: Captures events from the browser, dataLayer, Express, AWS Lambda, and GCP Functions.
• Collector: Handles consent management, schema validation, mapping, routing, and enrichment.
• Destinations: Routes events to platforms like GA4, Google Ads, Meta CAPI, and BigQuery.

Users can implement it via Integrated mode (importing directly into TypeScript apps) or Bundled mode (building a standalone script from a JSON configuration).

Who it’s for

Developers and data engineers who want version-controlled, declarative tagging and warehouse-native event collection that avoids vendor lock-in.

Highlights

• Config-as-code: Version control tracking definitions via PRs.
• Declarative tagging: Tag UI elements in HTML rather than using scattered JavaScript.
• Consent-native: Queues events until consent is given before flushing to destinations.
• Schema validation: Catches bad events at the time of collection.
• Warehouse-native: Delivers clean, structured data directly to data warehouses.
• AI-ready via MCP: Uses the Model Context Protocol to allow AI agents to read schemas, suggest tracking definitions, and generate integration code.