Event Sources and Data

Connect source records into the correct owner timelines.

3 min readProduct documentationzinzu Usage FAQ

51. Can I use the same table with different EventOwner columns?

An Event Source fixes its owner and timestamp columns. To analyze the same underlying data using a different owner, create a separate view and configure it as another Event Source.

For example, one view can group activity by Customer ID and another by Order ID. The choice changes which records can belong to the same sequence.

Related records across selected sources are connected for the same owner.

52. What if two sources use the same owner value for different entities?

The engine groups by the configured owner value. It does not infer that “123” means a customer in one source but an unrelated device in another.

Only combine sources whose owner identifiers share the same meaning. Use views to create compatible identifiers when necessary.

53. Can event conditions check attributes inside map or JSON columns?

Yes. Event conditions can target attributes within structured record data.

For example, an Event can check payload.email_verified. Nested member names must match the stored keys, including their case. Missing or inaccessible members resolve to null.

54. Are event filter comparisons case-sensitive?

Text filters treat text equality, inequality, containment, and membership comparisons case-insensitively.

For example, “FAILED” and “failed” match under Equals. Nested JSON member names remain case-sensitive. Like/Contains checks a substring; do not assume SQL percent-wildcard semantics.

55. How are missing attributes and null values handled?

Missing columns or attributes resolve to null. Is Null therefore matches both a missing value and a null value.

Equality to a non-null value and numeric comparisons do not match null. Negative comparisons have different behavior: Not Contains, for example, returns true for null. Use Is Not Null when absence must not satisfy a negative condition.

56. Does changing an Event affect previously submitted queries?

Existing completed results are not recalculated when an Event changes.

A new submission can use updated Event definitions. Review the definitions before submitting if you need to compare runs.

57. How can I make comparisons between query runs reproducible?

Review the Event definitions and settings before submitting another run.

For a meaningful comparison, keep the date range, EventOwner mapping, filters, and sampling settings consistent. Keep a record of the settings used for each run.

Continue readingSequence Order and Wildcards
Search documentation · Esc to close
Open original image ↗