Event Schema Overview
Event Schema Overview
Intempt uses an event-centric data model, where every real-world action is represented as an event.
Events contain identifiers, timestamps, and contextual metadata, enabling Intempt to unify customer behavior, perform real-time analytics, and trigger engagement workflows.
Events are processed and stored using Intempt’s performance-first infrastructure:
- ClickHouse for high-volume ingestion, time-partitioned historical storage, and sub-second analytical queries.
- Flink pipelines for triggering real-time engagement (Journeys).
- CDN-based personalization for <500ms segmentation and experience delivery globally.
Event Object Structure
{
"eventId": "string",
"profileId": "string",
"sessionId": "string",
"accountId": "string",
"pageId": "string",
"eventName": "string",
"timestamp": "ISO-8601",
"properties": {}
}
Fields
| Field | Type | Required | Description |
|---|---|---|---|
| eventId | string | Yes | Unique identifier for the event. Enables deduplication and accurate traceability. |
| profileId | string | Yes | Identifier of the user (masterID) performing the action. Used for profile merging and unification. |
| sessionId | string | Yes | The session context of the event. Groups multiple actions into a single behavioral session. |
| accountId | string | No | Optional account/workspace identifier for B2B or CRM use cases. |
| pageId | string | No | Page or screen where the event occurred, mainly for client-side tracking. |
| eventName | string | Yes | Name describing the action being tracked. |
| timestamp | string | Yes | ISO-8601 timestamp indicating when the event happened. |
| properties | object | Optional | Additional JSON metadata describing the event context. |
How Events Power GrowthOS
Discover
Unify and analyze event data across sources using segmentation, behavioral tracking, and predictive models.
Engage
Trigger automated journeys, send personalized messages, and deliver privacy-compliant interactions.
Optimize
Run experiments, measure performance, and iterate using dashboards and detailed event-driven insights.
Why the Schema Works
- Event-driven → clean mapping to real-world actions
- Real-time ingestion → analytics available in seconds
- Unified model → shared across all GrowthOS tools
- Scalable → designed for trillions of events
This schema forms the foundation of Intempt’s unified customer data platform and real-time engagement engine.