Getting Started
Practical answers to common questions about building queries, understanding results, and managing analysis cost.
1. What do I need before I can run my first query?
Configure an Event Source for each table or view you want to use, selecting its EventOwner and timestamp columns. Create User Defined Events for the actions you want to find, then add them to a query.
2. Where does zinzu process and store my data?
Zinzu processes your data inside your Snowflake account. Any intermediate objects and results it creates also remain within your account.
3. Can I analyze records from multiple tables or views?
Yes. Each Event is tied to one Event Source, and a query can combine Events from different sources. The configured owner values must identify the same entity across those sources.
4. What is the difference between an Event Source and an Event?
An Event Source defines where records come from and which columns identify their owner and timestamp. An Event defines which records from that source represent an action.
Example: A payments table is the source; records where status equals failed define Payment Failed.
5. What should I choose as my EventOwner?
Choose the identifier that keeps one subject’s activity together. Customer ID groups customer activity; Order ID separates orders; Request ID separates requests. The engine matches within an owner’s timeline, so choosing Customer ID can combine activity from several orders or visits.
6. Can different sources use different column names for the same EventOwner?
Yes. One source might use APPLICATION_ID and another REQUEST_ID. They can be combined when the values identify the same application. Matching column names alone is insufficient; their values must correspond.
7. Can I create an Event without filter conditions?
Yes. Every eligible record from that Event Source can match the Event. Be careful when combining it with narrower Events from the same source: a record may match both definitions. See question 18.