Account Links
Account Links service allows to store references to external systems, such as Social Logins (Google, Facebook, Apple) or client-specified external IDs (mappings with Ticketmaster, Seatgeek and other systems).
Cortex Platform provides UI to view and manage account links, you can find it in Fan Manager.

Primary/Secondary Account Links
Service supports nested records through the secondary flag. Please see the sample structure below:
[
{
"authId": 41069644,
"sourceSystemId": "CLIENT_VM",
"sourceSystemUserId": "5803090",
"sourceSystemCreatedAt": "2025-02-24T15:12:49.17253Z",
"alias": "CLIENT_VM",
"metadata": {
"email": "[email protected]"
},
"createdAt": "2025-02-24T15:12:10.516874Z",
"lastModified": "2025-02-24T15:12:49.193932Z",
"primary": true,
"secondaryLinks": null
},
{
"authId": 41069644,
"sourceSystemId": "EXTERNAL_GUID",
"sourceSystemUserId": "903eccde-bbd7-b5e6-31a0-1a09d3c89d03",
"sourceSystemCreatedAt": "2025-02-24T15:13:00Z",
"alias": null,
"metadata": null,
"createdAt": "2025-02-24T18:40:44.850941Z",
"lastModified": "2025-02-24T18:40:44.850941Z",
"primary": true,
"secondaryLinks": null
},
{
"authId": 41069644,
"sourceSystemId": "CLIENT_SOCIAL_GOOGLE",
"sourceSystemUserId": "111150331345793206539",
"sourceSystemCreatedAt": "2025-02-24T15:00:57.341329Z",
"alias": "Social Login - Google",
"metadata": null,
"createdAt": "2025-02-24T15:00:57.35553Z",
"lastModified": "2025-02-24T15:00:57.35553Z",
"primary": true,
"secondaryLinks": [
{
"authId": 41069644,
"sourceSystemId": "CLIENT_SOCIAL_GOOGLE",
"sourceSystemUserId": "1234567890",
"sourceSystemCreatedAt": "2025-02-24T15:00:57.341329Z",
"alias": "Social Login - Google (secondary)",
"metadata": null,
"createdAt": "2025-10-08T13:05:33.173982Z",
"lastModified": "2025-10-08T13:05:33.173982Z",
"primary": false,
"secondaryLinks": null
}
]
}
]
Account links have the following constraints:
Primary:
- Only one primary for SOURCE_SYSTEM
- SOURCE_SYSTEM_USER_ID should be unique across all primary account links
Secondary:
- SOURCE_SYSTEM_USER_ID should be unique across secondary account links for the given SOURCE_SYSTEM
To create secondary account link, request should have an explicit "secondary": true
set in the payload. When fetching account links, secondary records will be nested under the primary one with the same SOURCE_SYSTEM.
Secondary account link is considered orphaned if there is no primary link with the same SOURCE_SYSTEM. In that case, it will be returned in the root of the payload array, alongside primary records.
Updated about 13 hours ago