walkerOS Event Management FAQs

Question 1

What is the 'entity action' format in walkerOS?

Accepted Answer

It is a strict naming convention where every event consists of a noun (entity) and a verb (action) separated by a space, such as 'product add' or 'page view'. Underscores or merged words are considered invalid.

Question 2

Why are walkerOS events considered vendor-agnostic?

Accepted Answer

They capture data in a generic, self-describing format using standard nouns and verbs. This allows the data to be transformed for any destination (like GA4, Facebook, or Segment) during the mapping phase rather than at the point of capture.

Question 3

Can I use this skill to debug existing walkerOS implementations?

Accepted Answer

Yes, Claude can use this skill to scan your code for naming violations (like using underscores) or structural errors in event objects and suggest the compliant walkerOS format.

Question 4

How does this skill handle event properties like context and globals?

Accepted Answer

The skill provides the specific schema requirements for different property types: 'data' for entity-specific info, 'context' for hierarchical state, and 'globals' for session-wide properties, ensuring they are structured correctly for the walkerOS core.

walkerOS Event Management

Key Features

Use Cases

walkerOS Event Management

Key Features

Use Cases