Creating an Event Source
An Event Source connects a Snowflake table or view to the columns zinzu uses to analyze behavior. It defines which column identifies the EventOwner and which column determines when each event occurred.
Each table or view can have only one Event Source, but the same Event Source can be reused to create multiple Events with different filters.
Step 1: Select a Table or View
Navigate to Event Source → Add Event Source.
Browse the available Snowflake databases, expand a schema, and select the table or view you want to analyze.
Databases accessible to zinzu appear automatically once the Snowflake administrator grants the required permissions.
Tables or views marked CONFIGURED already have an Event Source defined.
Step 2: Configure the Event Source
After selecting a table or view, specify the following columns:
| Field | Description |
|---|---|
| EventOwner (Required) | Identifies the entity whose behavior you want to analyze, such as a customer, request, order, or device. |
| Event Time (Required) | Determines when each record occurred and its chronological position. |
| Description (Optional) | A short description to help identify the Event Source. |
Use Sample Rows to preview the data or Schema to inspect available columns before configuring the Event Source.
Example — Payments Table
| Configuration | Value |
|---|---|
| Table | PAYMENTS |
| EventOwner | REQUEST_ID |
| Event Time | PAYMENT_TIME |
zinzu uses REQUEST_ID to group related payment records and PAYMENT_TIME to arrange them chronologically.
Step 3: Reuse the Event Source to Create Events
Once an Event Source is configured, it can be reused to define multiple Events by applying different filters.
For example, a single Payments Event Source can define:
| Event Name | Filter |
|---|---|
| Payment Failed | status = 'failed' |
| Payment Succeeded | status = 'succeeded' |
| Payment Refunded | status = 'refunded' |
All three Events share the same EventOwner and Event Time columns. Only their filter conditions differ.
You will configure these filters in the next section, Creating Events.
Important: One Event Source per Table or View
Each table or view supports only one Event Source, with a single EventOwner and Event Time configuration.
If you need to analyze the same underlying data using a different EventOwner, create separate Snowflake views and configure each as an independent Event Source.
For example:
| View | EventOwner |
|---|---|
| PAYMENTS_BY_REQUEST | REQUEST_ID |
| PAYMENTS_BY_CUSTOMER | CUSTOMER_ID |
Both views can reference the same Payments table without duplicating the underlying data.
Remember: An Event Source defines how records are grouped and ordered. Events define which records are selected for analysis.