walkeros-mapping-configuration

You can map custom events to GA4 and Meta Pixel using declarative mapping schemas that transform walkerOS events like view_item and purchase into platform-specific payloads, handling nested field extraction and static values.

Yes, consent-gated fields can be included or redacted based on user consent within the event mapping configuration, ensuring analytics pipelines process PII according to active consent states.

You can transform and route events to custom REST API destinations by defining mapping schemas that apply event transformation, nested field extraction, and static value assignments to generate structured payloads.

Yes, conditional mapping allows you to apply different mapping configurations based on specific event data, enabling dynamic event transformation patterns for GA4, Meta Pixel, and custom API destinations.

You can validate event mappings in a controlled debugging environment by defining mapping blocks to translate incoming events and testing the resulting walkerOS payloads before deploying to live analytics pipelines.

Source-side mapping maps incoming fields directly to the walkerOS event structure, allowing you to normalize incoming event data before it undergoes further transformation for GA4, Meta Pixel, or custom API destinations.