Event Architecture.
Well-designed events carry the right context for behavioral analysis. Learn to structure events that maximize ABIS intelligence while minimizing payload overhead.
Events are the atomic unit of behavioral data. A well-designed event schema captures the who, what, when, where, and how of user actions. Too little context and ABIS can't make accurate assessments; too much and you're wasting bandwidth and processing power.
Core event fields include: event type (click, scroll, navigation), timestamp (ISO 8601 with milliseconds), session ID (links events within a session), user ID (if authenticated), and action-specific metadata (coordinates, target elements, values).
Schema versioning is critical for long-term maintenance. Include a schema version field in every event. When you add fields, increment the minor version; when you change field types or remove fields, increment the major version. ABIS maintains compatibility with recent schema versions.
CORE FIELDS
Required in every event: type, timestamp, sessionId, eventId (UUID), schemaVersion. These enable event correlation and temporal analysis.
REQUIREDIDENTITY FIELDS
User identification: userId, deviceId, ipHash. Include when available to enable cross-session behavioral profiles.
RECOMMENDEDCONTEXT FIELDS
Environment data: userAgent, viewport, timezone, locale. Helps ABIS detect device anomalies and impossible travel.
RECOMMENDEDACTION FIELDS
Event-specific data: coordinates, targetElement, inputValue (hashed), scrollDepth. Varies by event type.
TYPE-SPECIFIC