Core concepts
5 min read
Events and properties
How Tessera models user actions, and the naming rules that keep data clean.
Events describe what happened. Properties describe the details. Together they answer questions like which plan did people pick before they upgraded.
Reserved properties
A few properties have special meaning across every destination. Use them when they fit instead of inventing your own.
userId: a stable identifier from your database
timestamp: when the action happened, in ISO 8601
context: device, locale and library details added by the SDK
Property types
Tessera infers types from the first value it sees for each property. Sending a number as a string later will be flagged in the schema view, so pick a type and stick with it.
Was this page helpful?
