# What is a user property?

> A user property is a fact about a player, not about one event, such as a supporter plan or a Discord role. Manalens calls user properties traits.

By Yos Riady. Updated 2026-11-18. Published 2026-11-18. Canonical URL: https://manalens.dev/glossary/user-property

A user property is a fact about a player rather than about one event, such as their plan, their Discord role or the store they bought on. In Manalens, user properties are called traits. You set them with an identify call, and a later call changes only the keys that it sends.

## Key points

- Manalens calls user properties traits and sets them only with identify events.
- A later identify updates only the keys it sends, and a null value clears a key.
- Use a stable ID from your game or backend as the user ID, not an email address.

## How do traits work in Manalens?

Traits are allowed only on identify events. Keys have at most 100 characters. Values are strings of at most 1024 characters, numbers, booleans or null. A later identify updates only the keys that it sends, and a null value clears a key.

You can also edit traits on the player's profile page. The change is saved as a new identify event with the channel dashboard. A backend can set traits with the secret key, and an API key with the profiles:write scope can set them through the REST API.

Sources: Manalens identify event, MCP and server events documentation.

## What does an example look like?

Example: your game calls identify("player_42", {"plan": "supporter"}) when a player buys the supporter pack. Later it calls identify("player_42", {"discord_role": "tester"}). The profile now has both traits, because the second call changed only discord_role. A call with {"plan": null} would clear the plan.

Sources: worked example; Manalens identify event documentation.

## Why do user properties matter for indie PC and web games?

They let you compare groups of players, such as supporters and other players, or testers and buyers. Mixpanel describes profile properties the same way: they describe who the user is and show the latest known state, while event properties describe one event.

Use a stable ID from your own game or backend as the user ID. Email is an optional trait, not the identity key.

- [Player segmentation for small studios](https://manalens.dev/blog/player-segmentation-small-studios)
- [User profiles](https://manalens.dev/features/user-profiles)
- [Retention calculator](https://manalens.dev/tools/retention-calculator)

Sources: Mixpanel documentation: User profiles; Manalens core concepts documentation.

## Frequently asked questions

### How do I remove a user property?

Send identify with the key set to null. A null value clears that key. Other traits stay as they are, because a later identify updates only the keys that it sends. You can also edit traits on the player's profile page.

### Should I use an email as the user ID?

No. Use a stable ID from your own game or backend as the user ID. In Manalens, email is an optional trait, not the identity key, and the user ID has 1 to 255 characters. A stable ID keeps the same player history when the player changes the email address on their account.

### Who can set traits?

Your game sets traits with an identify call. A backend can set them with the secret key, and an API key with the profiles:write scope can set them through the REST API. You can also edit traits on the player's profile page, and the change is saved as a new identify event with the channel dashboard.

## Sources

- [Mixpanel documentation: User profiles (read 19 November 2026)](https://docs.mixpanel.com/docs/data-structure/user-profiles)

## Related guides

- [Player segmentation for small studios](https://manalens.dev/blog/player-segmentation-small-studios)
- [User profiles](https://manalens.dev/features/user-profiles)
- [Retention calculator](https://manalens.dev/tools/retention-calculator)
- [Event property](https://manalens.dev/glossary/event-property)
- [Identity stitching](https://manalens.dev/glossary/identity-stitching)
