Skip to main content
User properties are a powerful feature in Tranthor that allow you to define how user events are aggregated to be rendered in your templates. User properties are also used to identify users when contacting channel providers. For example, the email property is used to identify users when sending emails.

User Property Types

  • Trait: Trait user properties selects the last observed trait value of an identify event.
  • Performed: Performed user properties select the last observed property value of a track event.
  • Id: Tranthor uses the id property to identify logged in users.
  • Any Of: Any Of user properties can be used to select the most recent value provided by a collection of sub-properties.
  • File: File user properties can be used to reference files in your templates e.g. for sending email attachments.
  • AnonymousId: Tranthor uses the anonymousId user property to identify logged out users.
  • Keyed Performed: Keyed Performed user properties select the last observed property value of a track event - specialized to event entry journeys.

Default User properties

Tranthor comes pre-populated with a set of default user properties.
  • email: The user’s email address. Used to identify users when sending emails.
  • phone: The user’s phone number. Used to identify users when sending SMS messages.
  • deviceToken: The user’s device token. Used to identify users when sending push notifications.
  • firstName: The user’s first name.
  • lastName: The user’s last name.
  • language: The user’s language.
  • accountManager: The user’s account manager.
  • id: The user’s unique identifier, provided by your system. This user property cannot be deleted or changed.
  • anonymousId: The user’s anonymous identifier, provided for logged out users. This user property cannot be deleted or changed.

User Property Examples

For example, when rendering an email, you can use the firstName user property to personalize the email.

What a user profile shows

The User Properties card shows workspace-defined, computed properties used in messages, segments, and journeys. Computed properties usually appear within a few minutes. A user with events can have a profile before these properties and their entry in the Users list exist. The Traits card shows raw identify traits without requiring a matching property definition. It merges the newest 200 identifies by client event time, breaking ties with processing time. The newest value wins per top-level key; nested objects are displayed without merging. Duplicate keys within a JSON object use the last value in this card; computed Trait properties use the first value returned by ClickHouse JSON_VALUE. JSON numbers use JavaScript number precision, so large integers may lose precision. At most 100 live keys appear, with +N more keys when the cap drops keys. Values whose serialized UTF-8 JSON exceeds 2 KB are replaced with a clipped string ending in … [truncated]. An explicit null clears a key in this card. A computed Trait property instead stores the string 'null'; Trait properties inside an Any-of group skip nulls. Computed Trait properties do not display raw nested objects in the same way. Both raw and computed Trait values are ordered by client event timestamps: a future-dated timestamp can pin a value until an event with a later timestamp arrives. Create a Trait user property to use a raw trait in segments and journeys. Traits use the newest 200 identifies across all history, regardless of age. Older keys remain visible when a recent identify updates only some traits, as long as the older identify is among those 200 events. This card is a bounded preview rather than a complete history of traits. The Device & app card shows device & app info from the last 90 days, using the newest non-empty event context processed within that period, and its client event time. Mobile SDK device, OS, app, library, locale, and timezone information comes from event context; web context can also show user agent and page URL/title. Page URLs are reduced to origin and pathname, removing query strings, fragments, and credentials. Finite numeric and boolean SDK metadata are shown as strings. Only those documented fields are returned, excluding device tokens, advertising IDs, IP addresses, and other context fields. Each field has the same 2 KB value bound as traits. Last seen covers the past 90 days and uses ingestion time, excluding Tranthor’s internal events, so client clock skew and internal message delivery do not make a user appear active. Times are labeled UTC. If the raw profile service is temporarily unavailable, computed properties remain visible with a “Raw profile unavailable” message. A profile renders when a computed user exists, retained traits are non-empty, or there is activity within the last 90 days. A user with only older track events and no computed user or retained traits returns a not-found page; profile lookups do not scan older activity to establish existence. Older identify users with retained traits can still render, with empty recent device context and last seen.