Creating an Event

An Event defines which records from a table or view you want to analyze. Each Event is associated with one configured Event Source and can optionally include filters to select specific records.

2 min readProduct documentationzinzu user guide

Multiple Events can reuse the same Event Source with different filter conditions.

Step 1: Name the Event and Select an Event Source

Navigate to Events → Add Event.

  1. Enter a descriptive Event Name, such as Payment Failed.
  2. Select an existing configured Event Source from the dropdown.
  3. Use Sample Rows or Schema to inspect the available data.

Each Event is tied to one Event Source (table or view). If the records you want to analyze are spread across multiple tables or views, create a separate Event for each relevant source.

Step 2: Define Filter Conditions (Optional)

Filters determine which records from the selected Event Source qualify for the Event.

To add a filter:

  1. Select a column.
  2. Choose a comparison operator, such as = (equals).
  3. Enter the target value.
  4. Add more conditions if needed.

Example: Payment Failed

SettingValue
Event NamePayment Failed
Event SourcePAYMENT_LEDGER
Filter ColumnPAYMENT_STATE
OperatorEquals (=)
Target ValueFAILED

This Event includes only records where PAYMENT_STATE = 'FAILED'.

Combining Multiple Filters

When using multiple conditions, select how they should be combined:

  • AND: All conditions must match the same row.
  • OR: At least one condition must match the row.

zinzu supports either AND or OR across an Event's filters, but not a combination of both.

Creating an Event Without Filters

Filters are optional. If no filter conditions are specified, all rows from the selected Event Source qualify for the Event.

For example, an Event named Payment Attempt without filters includes every record from the PAYMENT_LEDGER table.

Important: Events Across Multiple Sources

An individual Event cannot combine records from multiple tables or views.

If your business activity is recorded across different sources, create separate Events for each source.

Example:

EventEvent Source
Payment FailedPAYMENT_LEDGER
Retry AttemptedSERVICE_LOGS
Payment SucceededPAYMENT_LEDGER

These Events can then be used together in a zinzu query to find patterns such as:

Payment Failed → Retry Attempted → Payment Succeeded

Query example: Payment recovery using events from two sources.

zinzu connects matching EventOwner records across the sources when executing the query.

Continue readingAny-Order Behavior
Search documentation · Esc to close
Open original image ↗