clix-event-tracking

Event tracking design standardizes event naming, property schemas, and end-to-end validation to ensure reliable campaign triggers and analytics. It enforces snake_case naming, JSON primitive property values, and exact event-name matching.

Event tracking naming conventions require snake_case for event names and property keys to ensure campaigns trigger reliably. Property values must use JSON primitives to maintain data hygiene across platforms.

Audit trackEvent calls by validating event names, property schemas, and success criteria across platforms and MCP workflows. Use bundled templates, references, and practical checklists for end-to-end debugging and implementation support.

Event-triggered campaigns fail when event names do not match exactly or property schemas are inconsistent. Enforce exact event-name matching, snake_case naming, and JSON primitive property values to ensure reliable campaign triggers.

Yes, trackEvent supports safe property schemas with privacy guardrails to minimize PII exposure and promote data hygiene. Use JSON primitive property values and standardized naming to maintain privacy compliance across platforms.

MCP workflows are supported for end-to-end event tracking validation but not strictly required. The validation scope covers planning, implementation, and debugging tasks across platforms with bundled references and templates.