There is a scenario where a player could potentially unlink their Epic Product User ID from the external account ID, which they can keep doing to change the associated product user ID assigned to their external account ID. I was wondering if there is a way on the server side I can track the last cached external account ID prior to being unlinked from the EPIC product user ID? This way I can always correlate all activity of the player on the game server side. I suppose one way to do it would be to track it constantly on the game server end, but it would be tricky to synchronize all the data across multiple servers and was wondering if there’s a way to do it through an EOS SDK call if it exists, or if this feature could possibly be implemented?
Hello, could you please share any information on what you’re trying to achieve with this association information?
If I understand your request correctly, you would like an API that accepts an external account ID and checks if it has previously been linked to an EOS Product User.
We only have APIs to track active account associations, and instead, you would need to track historical associations between external accounts and EOS Product Users in your own backend.
If it is regarding Anti-Cheat and Sanctions, our systems do take into account the unlinking and relinking scenario.
Yes, that’s exactly correct, I’m referring to an API that can accept an external account ID and check if it has ever been linked to a given EOS Product User ID, even if that association is no longer active.
This request isn’t related to Anti-Cheat or Sanctions. It’s primarily for maintaining consistent server-side player records and analytics across unlink/relink scenarios. Since players can freely unlink and relink accounts, it becomes challenging to correlate historical gameplay data, server interactions, or progression that were tied to previous associations.
While we could theoretically track these associations on our backend, it’s not always reliable or synchronized in multi-server or dynamic matchmaking environments. Having an EOS-provided API or event callback for “link/unlink history” (even with a limited retention window) would help developers maintain consistent player identity tracking without introducing custom infrastructure.
I think it could be valuable for developers who need to maintain long-term continuity of user data, statistics, and entitlements across account link changes.