Data catalog

Use the data catalog when you want to understand which customer data getuserfeedback.com has seen and how that data can be used for targeting, segmentation, personalization, and delivery rules.

The catalog is built from the data you send through the widget, SDKs, API events, and connected integrations. It can include events, event properties, user traits, feature flags, and capabilities.

Open it from your workspace at Data catalog.

What appears in the catalog

Each catalog entry represents one signal in one scope. For example, a plan property on a Checkout completed event is tracked separately from a plan trait on a user profile. This matters because the same property name can mean different things in different events.

Catalog entries can come from:

Observed traffic — data getuserfeedback.com has received from your app or an integration.
Definitions — metadata imported from a connected source, when available.

Your team can then add manual metadata to those entries: names, descriptions, status, and sensitivity labels. Observed facts and manual metadata are kept separate. Editing the catalog name or description does not rename the event or property that your app sends.

Status

Status controls how your team should treat a catalog entry.

Visible — the signal is available and expected to be used.
Deprecated — the signal is kept for history, but should not be used for new targeting or delivery rules.

Some entries may be hidden by the system after an integration is removed or a source is revoked. Hidden entries are not customer-editable.

Sensitivity

Sensitivity helps your team flag whether a signal may contain private or regulated data.

Unknown — nobody has reviewed the signal yet.
Normal — expected product or account data without sensitive content.
Sensitive — data that may be private, regulated, or customer-sensitive.

Sensitivity does not change ingestion by itself. Use it as an operational cue when deciding what data should be used in targeting, messages, and integrations.

Names and descriptions

Catalog names and descriptions are for humans. Use them to explain what a signal means, where it comes from, and when it should be used.

The observed key remains unchanged. If your app sends plan, the catalog can display Billing plan, but the underlying key is still plan.

What can break

The catalog is only as useful as the data you send. If events are renamed in your app without a migration plan, the catalog will show the new signal separately from the old one. If the same property name is used with different meanings on different events, document each scoped entry separately.

For identity and traits, see Personalization and Identity resolution.