What is a service-specific account or user ID?¶

A provider return or technical record may include a long numeric or alphanumeric account ID.

Evidential caution: that the visible username is always the best way to identify the account.

What this means¶

A service-specific account or user ID is an internal identifier assigned by the platform. It is used to distinguish that account within the provider’s systems.

Unlike a display name, it is often not intended for ordinary users and may remain stable when the visible name or username changes.

That makes it valuable for linking messages, group membership, login records, provider returns and account history to the same underlying account.

But an account ID identifies the account, not the person controlling it. Shared use, compromise, delegation and linked devices still need to be considered.

Where available, preserve related identifiers such as conversation IDs, message IDs, channel IDs, device IDs and session IDs. These can help reconstruct how records fit together.

Be alert to provider terminology. “User ID”, “account ID”, “member ID”, “profile ID” and “conversation ID” may refer to different objects and should not be merged without explanation.

An account may also have more than one identifier because of migrations, linked products or organisational tenancy. Preserve the original field names and source records so later interpretation remains possible.

What to check or do next¶

• Preserve the identifier exactly. Do not shorten it, reformat it or treat similar-looking IDs as interchangeable.
• Record which service issued it and where it came from. A user ID from one platform has no meaning on another.
• If the meaning is unclear, seek documentation or specialist interpretation rather than guessing.