Next generation Player IDs

To further enhance the privacy of users, we are introducing PGS next generation Player IDs. With next generation Player IDs, users will be assigned a different Player ID for each game they play, however the Player ID will remain consistent for a given game (by PGS Project) across devices.

Next generation Player IDs will only apply to users who have never signed into your game with PGS. Existing users who have already logged into your game will continue to get the same Player ID.

Next generation Player IDs will be rolled out gradually and will eventually be a requirement for all PGS projects starting March 2024. For a detailed timeline of the rollout plan, please review this blog post.

Using next generation Player IDs

In order to start supporting next generation Player IDs, you will need to navigate to Play Game Services > Setup and management > Configuration within the navigation bar, then on the configuration page click Edit properties. Here, you will find the settings to enable next generation Player IDs, as seen below.

Play Game Services Next Generation ID Config

Prior to publishing the change to enable next generation Player IDs, we recommend using tester accounts to verify that next generation Player IDs won't cause issues with your identity system.

To do this, set the radio button to "On" but don't publish the change. Once the radio button is set to "On", the tester accounts will return next generation Player IDs for you to test with. This setting will apply to all the games linked to this PGS project.

Once you have completed testing, publish the change with your PGS project in the Play Console (under Play Games Services > Setup and management > Publishing) so the change goes into effect and all new users start receiving next generation IDs.

Testing next generation Player IDs

If your game doesn’t make the assumption that a Player ID will be consistent across different titles, then we expect that you will be able to enable next generation Player IDs without issues. However, we still recommend testing to confirm there won’t be any issues.

A few tests we would recommend running:

  • Ensuring tester accounts (receiving next generation Player IDs) are able to login and link their PGS profile with game progresses
  • (If applicable) Tester accounts are able to login to the same identity system with the same PGS profile across separate games, and have their progress tracked

Using the developer player key

If you need a way to identify a user across your titles to offer cross-game users experiences, you can use the developer player key. The developer player key is only accessible via the REST Web APIs. To retrieve the ID:

  1. [If not already completed] Set-up your client and backend server for access to the PGS REST APIs
  2. Make the following HTTP request GET

The response will have one field:

developer_player_key (string) - The user's ID which will be the same across a developer's applications in their Google Play Console.

Retrieving a list of Player IDs across your applications

You can also retrieve a list of your user's Player IDs across the list of applications that are owned by your developer account. Please note that a user will only have an ID for the games that they have been signed into with PGS.

  1. (If not already completed) Set-up your client and backend server for access to the PGS REST APIs
  2. Make the following HTTP request