Events & Taxonomy

Event catalog, custom properties, and auto-discovery

Events & Taxonomy

Nuxie auto-discovers event names and property keys as your app sends them. Browse the event catalog, mark events as verified, and add descriptions to keep your data organized.

Auto-discovery

You do not need to register events or properties before sending them. When Nuxie receives an event it has not seen before, it automatically:

1. Creates an entry in the event catalog with the event name.
2. Records each property key observed in the event payload.
3. Infers the data type of each property value.
4. Maps properties to the event that carried them.

Auto-discovery applies to custom events (events without a $ prefix), $identify events, and $feature_used events. Other system events are excluded from the catalog by default to reduce noise.

Event catalog

The event catalog is a searchable list of every event name observed in your app. Access it from the dashboard under your app's settings or from the segment builder.

Each event entry includes:

• Name -- The event name string as sent by the SDK
• Last seen -- Timestamp of the most recent occurrence
• Verified -- A checkmark indicating the event has been reviewed by your team
• Description -- Optional text explaining what the event represents

Marking events as verified

Verified events appear with a checkmark badge in the segment builder and event picker. Mark an event as verified to signal to your team that it is intentional and reliable.

To verify an event, open the event catalog, find the event, and toggle the verified status.

Hiding events

Hide events that are noisy or irrelevant. Hidden events are excluded from typeahead suggestions in the segment builder but remain in the underlying data.

Property catalog

Every property key observed across your events is recorded in the property catalog. Properties are categorized by scope:

Each property entry includes the inferred type, last-seen timestamp, and optional description.

Type inference

Nuxie infers the data type of each property when it first appears. The inferred type is locked in on first observation and does not change if later values differ.

Tip: Use descriptive key names like created_at or subscription_start_date to help Nuxie correctly infer datetime types.

Property directives

When you send properties with $set, $set_once, or $unset keys, Nuxie treats the nested values as customer-scoped properties:

NuxieSDK.shared.trigger("signup_completed", properties: [
    "plan": "premium",
    "$set": ["email": "[email protected]", "plan_tier": "premium"],
    "$set_once": ["signup_date": "2026-01-15"]
])

In this example:

• plan is recorded as an event-scoped property.
• email and plan_tier are recorded as customer-scoped properties.
• signup_date is recorded as a customer-scoped property (set only if not already present).

How taxonomy powers segments

The event catalog and property catalog feed directly into the segment builder:

• Event name typeahead -- When you add an event condition to a segment, the builder suggests event names from the catalog.
• Property key typeahead -- When you filter by event properties, the builder suggests keys that have been observed on that event.
• Type-aware filters -- The inferred property type determines which comparison operators are available (equals, greater than, contains, etc.).

Verified events and properties appear first in typeahead suggestions, making it faster to build segments from trusted data.

Defensive limits

To protect against malformed payloads, Nuxie enforces the following limits:

• Event names longer than 400 characters are dropped.
• Property keys longer than 400 characters are skipped.

Events and properties within these limits are processed normally.

Next steps

• Segment Builder -- Build segments using discovered events and properties
• System Events -- Reference for $-prefixed system events
• Tracking Events -- Send custom events from the iOS SDK