Identity Events

The Events tab shows a chronological history of actions associated with a particular identity. You can see when a play session began and ended and all the events in between (for example: joined a group, unlocked a character, received a reward).

The actions displayed are specific, predefined events in your game. Use them to capture the details you need to understand and improve player experience, engagement, and outcomes.

Core events #

Satori’s event taxonomy includes a set of core events (also known as default events) that are already defined in the system. These events are preconfigured and ready to be received by the server.

A series of computed properties are automatically generated and tracked per identity for each of these default events, as long as the event is fired.

Synthetic events #

Synthetic events, also known as server-side events, are automatically generated and tracked by Satori in response to certain actions. For example, whenever a user’s properties are updated—whether via the client SDK or during authentication—Satori fires the _propertiesUpdate event.

Tracking players before sign-in #

When a player starts your game without signing in, Satori can still track their activity under a temporary identity (typically device-based). If that player later authenticates, Satori merges their guest history into their permanent identity.

Here’s what happens:

1. Player starts as guest: Your client calls Authenticate with a temporary ID. Satori fires _identityCreate and _sessionStart for this identity.
2. Player generates activity: All events, properties, and experiment assignments are tracked under the temporary identity.
3. Player signs in: Your client calls Identify with the player’s permanent ID. Satori fires _identify, migrates all data from the temporary identity to the permanent one, and deletes the temporary identity.

See Identifying a session with a new ID for more details.

Commonly confused terms #

Some Satori terms sound similar but have distinct meanings. The following clarifies what each one means.

Item Spent vs Item Consumed #

Use the item events to distinguish cost from use:

Metadata vs Value #

Satori events include two fields for custom data:

Example (tutorialCompleted):

1
2
3
4
5
6
7
8

{
  "name": "tutorialCompleted",
  "value": 3,
  "metadata": {
    "tutorialType": "movement",
    "isSkipped": false
  }
}

Schema validation #

Both metadata and value are validated against schemas defined in Taxonomy. Satori provides these built‑ins, and you can add your own:

• ANY - Accepts any value; no validation.
• Number - Expects a numeric value.
• String - Expects a string.
• Object - Expects a JSON object (arbitrary keys/values allowed).
• Event‑Revenue‑Metadata - Specialized object for revenue events; include at least amount and currency (and optional test) to enable correct conversion and revenue calculations.

Additional Information #

How-to Guides

• How to Send Server-Side Analytic Events
• How to use Satori for Effective Session Management

Linked Concepts

• Events Taxonomy

Reference Docs

• Properties: computed properties
• Publishers