Types of Events

zinzu provides two types of events to build queries: System Defined Events and User Defined Events.

2 min readProduct documentationzinzu user guide

System Defined Events

System Defined Events are controls provided by zinzu. They define how a query matches a pattern—for example, where it starts and ends, whether other activity is allowed between steps, how often an action can repeat, or which timing conditions must be satisfied.

Example: Place Any event between Product viewed and Order placed to allow other activity between those two actions.

Query example: Allow activity between a product view and an order.

User Defined Events

User Defined Events describe the actions you want to find in your data. You create them by selecting a configured Event Source and optionally adding filter conditions. Each event uses the EventOwner and timestamp columns already configured on that source.

Example: Create Payment failed using the Payments table, request_id as the EventOwner, payment_time as the timestamp, and status = failed as the filter.

Using Them Together

Combine User Defined Events with System Defined Events to express your pattern.

Example:

Start → Payment failed → Any event → Payment succeeded → End

Query example: Combine named payment events with a wildcard.

Here, Payment failed and Payment succeeded identify the required actions. Start, Any event, and End control how zinzu matches them.

Query builder event library showing System Defined Events and User Defined Events.

Continue reading1. Simple query