Profile schema

How your user data is defined and structured across Krenalis and your data warehouse.

The profile schema is the single, authoritative definition of the properties that make up a user profile. It specifies which properties exist, how they are structured, and how their values (attributes) should be interpreted throughout Krenalis.

This definition applies uniformly to all user data — whether collected from events, SDKs, backend systems, databases, or files. Because every identity and profile follows the same schema, all downstream tools — analytics platforms, CRM systems, customer journeys, and internal dashboards — work with clean, consistent, and well-structured information.

• 

  View the profile schema

  Learn how to explore the profile schema and understand its structure and data types.

• 

  Alter the profile schema

  Learn how to update the profile schema while keeping your workspace fully consistent.

Each workspace is fully isolated: it has its own profile schema and its own set of tables. This separation allows environments — such as production, testing, or different teams — to adopt a data structure tailored to their specific needs. You can change the schema in one workspace without affecting any others or introducing unintended side effects.

When you update the schema in a workspace, Krenalis automatically applies the same changes to the corresponding tables in the connected warehouse, ensuring the structures stay perfectly aligned. Any addition, removal, or renaming of a property is reflected directly in that workspace's user tables.