User Insights

Last updated on July 1, 2026

Overview

User Insights is an analytics feature in the ADT Admin Portal that gives game developers a persistent, cross-session view of individual users in their game. Instead of seeing crashes and sessions as isolated events, developers can trace a complete history for a single user — who they are, what hardware they run, how many sessions they've had, and how many crashes they've experienced.

User Insights is part of the Health pillar and sits inside the Debugging section of the Admin Portal, scoped per game.

Why User Insights Exists

Session IDs change every time a user launches the game. Without a stable identity, two crashes from the same user look identical to ten crashes from ten different users. This makes it difficult to:

• Identify users who are repeatedly crashing (a "troubled user")
• Distinguish a widespread issue from a single user's hardware problem
• Track whether a fix actually resolved an issue for affected users
• Prioritize bug investigations based on how many unique users are impacted

User Insights introduces a stable User ID that persists across sessions, making it possible to connect events over time and surface patterns that session-level data cannot reveal.

How User Insights Works

The User ID

Every user in a game is assigned a persistent User ID derived from two identity signals sent automatically by the SDK during session creation:

• ADT account / computer username — the ComputerUsername field from the session request
• Machine name — the device hostname

The resulting User ID takes one of two formats:

Format	Meaning
platform-{uuid}	The user has a linked AGS (AccelByte Game Services) account
device-{uuid}	The user is identified by device only — no AGS account linked

The platform-* prefix signals a higher-confidence identity (account-backed), while device-* identifies anonymous or device-only users. Both types appear in User Insights and can be tracked across sessions.

Device Metadata

In addition to the User ID, ADT stores hardware and environment metadata per user at the time of first session creation. This metadata includes:

• CPU and GPU model
• Operating system and OS version
• Renderer, system architecture, and memory
• IP address, country code, and locale

note

IP address is personal data under applicable privacy regulations (e.g., GDPR). Ensure your studio's privacy policy and data processing agreements cover collection of this field before enabling User Insights for users in regulated regions.

This data powers the filtering and segmentation capabilities in the dashboard.

Data Flow

1. The game client sends a session request containing the computer username and device metadata. This is handled automatically by the SDK — no extra integration is required.
2. The profiling service computes a stable User ID, stores it, and associates all subsequent sessions and crashes from that user to the same ID.
3. The Admin Portal queries the profiling service and displays aggregated data per user on the User Insights dashboard.

info

User IDs are assigned from the point the feature flag is enabled. Crashes and sessions recorded before enablement are not retroactively attributed to a User ID.

Key Benefits

• Identify troubled users — surface users who are experiencing repeated crashes, distinct from users with a single isolated crash
• Full user history — view every session and crash for a specific user in one place, without searching across individual crash reports
• Hardware-aware debugging — filter users by CPU, GPU, OS, and region to determine whether a crash is hardware- or environment-specific
• Platform segmentation — understand the split between AGS-linked users (platform-*) and anonymous device users (device-*)
• Zero SDK changes required — User Insights works from data the SDK already sends; no additional instrumentation is needed

Limitations and Considerations

• Feature flag required — User Insights is disabled by default. A namespace admin must enable the User Insights toggle under ADT Web > Namespace Settings > Labs before the dashboard is visible.
• Device-only identity is not account-level — device-* users are identified by machine, not by a logged-in account. If a user reinstalls the OS or changes machines, they may appear as a new user.
• Permission required — accessing User Insights requires NAMESPACE:{namespace}:SESSION [READ] permission. Users without this permission cannot view the dashboard.

Supported Platforms

User Insights is a backend and Admin Portal feature. It receives data from any platform that uses the ADT SDK for session reporting.

Engine	Platform	Supported
Unreal Engine	Windows	Yes
Unreal Engine	PS5, Xbox	Yes
Unreal Engine	macOS	Yes
Unreal Engine	iOS, Android	Yes
Unity	Windows	Yes
Unity	macOS	Yes
Unity	iOS, Android	Yes

No platform-specific SDK configuration is required. Support is contingent on the SDK sending session data to ADT.