External User ID
GameAnalytics supports tracking a secondary identifier that you can use to aggregate and link data sets.
Common use cases:
- Linking in-game behavior with backend user profiles
- Synchronizing analytics across multiple platforms (mobile + web)
- Enabling data enrichment with third-parties
External user IDS are not displayed in the AnalyticsIQ web-tool. Instead, you can access and analyze them exclusively through PipelineIQ’s Data Warehouse and Data Export features.
| Platform / Feature | Appearance |
|---|---|
| Data Export | Appears as a field in the exported raw files E.g: user_ID_ext:steamID |
| Data Warehouse | Appears as a field in the player checkpoint table E.g: user_ID_ext |
| Metrics API | Not available / not used for metrics calculations |
| AnalyticsIQ UI | Not available / not used for metrics calculations |
How to send External User IDs
External User IDs are sent as any string value of your choice by setting a custom user ID before initializing the GameAnalytics SDK.
Refer to the SDK Documentation for code examples specific to your platform (Unity, Unreal, Roblox, iOS, Android, etc.).
Considerations
-
External User IDs are optional, and not used in the AnalyticsIQ UI for calculating metrics.
-
When instrumented, External User IDs are sent with every event type
-
When an External User ID is set for the user, it will be persisted across sessions and app exit until:
- Another external user ID value is specified.
- The external user ID value is reset by calling with null.
- The app is re-installed.
-
Persistent identity is your responsibility: Ensure that your game reliably provides the same ID per player (e.g. from a login system).
-
GDPR compliance: If you use External User IDs that could identify users personally, ensure that you handle privacy and consent appropriately.