What is a service-specific account or user ID?¶
It is an internal identifier assigned by a platform to distinguish an account or user object. It often remains stable when visible names change, making it a strong key for joining provider and device records.
IDs identify defined technical objects¶
Account, user, member, profile, message, conversation, channel, device and session IDs can refer to different objects. Preserve the original field name, value, service and source rather than merging similar-looking identifiers.
An account can also receive several IDs through product links, tenancy or migration. Provider definitions or specialist interpretation may be needed to map them.
Preserve exact values and scope¶
Do not shorten, reformat or allow spreadsheets to round a long numeric ID. Store it as text and record where it appeared. An ID from one service has no meaning on another unless documented linkage exists.
The value connects records to an account, not a person. Sharing, compromise, delegation and linked devices still govern personal attribution.
The point to remember
Use exact service-specific IDs to join the same technical object across records, while keeping account identity separate from human control.