Skip to main content

Users model

The users model represents people who belong to customer accounts. It lets FunnelStory attribute product activity, invites, and other events to individuals, roll up to the account level, and power user-centric views.

Prerequisites

Configure the Accounts model first. Every user row must reference a valid account_id that exists in your account model.

Model keys

Rows are uniquely identified by the combination of user_id and account_id (the same person could theoretically appear under different accounts with different IDs).

Field reference

Required key properties

PropertyTypeDescription
user_idstringStable identifier for the user within your product or source system.
account_idstringThe account this user belongs to; must match an account from the accounts model.
PropertyTypeDescription
namestringDisplay name.
emailstringEmail address; used for matching, enrichment, and assignment flows where applicable.
created_attimestampWhen the user record was created; used for lifecycle and timelines.

Optional properties

PropertyTypeDescription
rolestringProduct role or persona label; may be used for role tagging in FunnelStory.
traitsjsonArbitrary JSON object of additional attributes from the source (for example Segment-style traits).
fs_user_idstringInternal or cross-system user identifier when you use one.
user_typestringDistinguish user categories if your source provides them.

Custom properties

Any additional column you map becomes a custom user property, subject to naming rules (letters, numbers, spaces, hyphens, underscores). Custom properties can be used for filtering and display where the product exposes them.

For general type and timestamp rules, see Data type reference and Timestamp formatting.

Activities from this model

When a user model is saved, FunnelStory creates default activity rules such as Created user and Updated user so account timelines reflect user lifecycle changes.

Configure the model

  1. Add a data connection that contains your users (warehouse, Postgres, HubSpot, Salesforce, etc.).
  2. Open Configuration → Data models → Add model → User.
  3. Select the connection and provide a query (or table selection) that returns one row per user per account with the properties above.
  4. Map each source column to the correct property name. Ensure user_id and account_id are never null for rows you want to keep.
  5. Validate the query, run quick test if available, then save.
  6. Refresh the model and confirm user counts on the Accounts and Users views in the app.