[null,null,["最后更新时间 (UTC):2025-07-26。"],[],[],null,["# Next generation Player IDs\n\nTo further enhance the privacy of users, we are introducing PGS next generation\nPlayer IDs. With next generation Player IDs, users will be assigned a different\n[Player ID](https://developers.google.com/android/reference/com/google/android/gms/games/PlayersClient#public-abstract-taskstring-getcurrentplayerid)\nfor each game they play. However, the\nPlayer ID remains consistent for a given game\n([PGS Project](/games/pgs/console/setup)) across devices.\n\nNext generation Player IDs will only apply to users who have never signed into\nyour game with PGS. **Existing users who have already logged into your game\nwill continue to get the same Player ID.**\n\nNext generation Player IDs will be rolled out gradually and will eventually be a\nrequirement for all PGS projects starting August 2025. For a detailed timeline\nof the rollout plan, review this [blog post](https://android-developers.googleblog.com/2023/02/enable-next-generation-ids-for-better-play-games-services-support-for-all-google-accounts.html).\n| **Note:** Next generation Player IDs enable better Play Games Services support for all accounts, including those [under supervision](https://support.google.com/families/answer/9499456).\n\nUse next generation Player IDs\n------------------------------\n\nTo support next generation Player IDs, do the following:\n\n1. In the [Google Play Console](https://play.google.com/apps/publish/), select a game.\n2. Navigate to **Grow \\\u003e Play Games Services \\\u003e Setup and management \\\u003e Configuration**.\n3. On the configuration page, select **Edit properties**. This page includes the settings to enable next generation Player IDs, as shown in the following image:\n\nPrior to publishing the change to enable next generation Player IDs, we\nrecommend using [tester accounts](/games/pgs/console/setup#test) to verify that\nnext generation Player IDs won't cause issues with your identity system.\n\nTo do this, set the radio button to \"On\" but don't publish the change. Once the\nradio button is set to \"On\", the tester accounts will return next generation\nPlayer IDs for you to test with. **This setting will apply to all the games\nlinked to this PGS project.**\n| **Note:** Existing tester accounts will need to recreate their PGS profile in order to receive next generation Player IDs.\n\nOnce you have completed testing, [publish the change with your PGS project in\nthe Play Console](/games/pgs/console/publish)\n(under **Play Games Services \\\u003e Setup and\nmanagement \\\u003e Publishing**) so the change goes into effect and all new users\nstart receiving next generation IDs.\n| **Note:** If issues arise in production, you can choose to temporarily disable next generation IDs by selecting \"Off\" and [publishing the new change](/games/pgs/console/publish).\n\nTest next generation Player IDs\n-------------------------------\n\nIf your game doesn't make the assumption that a Player ID will be consistent\nacross different titles, then we expect that you will be able to enable next\ngeneration Player IDs without issues. However, we still recommend testing to\nconfirm there won't be any issues.\n\nA few tests we would recommend running:\n\n- Ensuring tester accounts (receiving next generation Player IDs) are able to login and link their PGS profile with game progresses.\n- (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.\n\n| **Note:** Next generation Player IDs are supported on devices running GMS Core versions 22.30.12 or higher. More info on how to check the GMS Core version can be found [here](/games/playgames/faq#q_why_does_v2_auto_sign-in_fail_on_a_mobile_device). For all devices running versions older than this, next generation IDs won't be supported.\n\nUse the developer player key\n----------------------------\n\nIf you need a way to identify a user across your titles to offer cross-game\nusers experiences, you can use the *developer player key* . The *developer\nplayer key* is only accessible through the REST Web APIs. To retrieve the ID:\n\n1. [Create a server-side web app](/games/pgs/android/server-access#create_a_server-side_web_app).\n2. Make the following HTTP request:\n\n `GET https://www.googleapis.com/games/v1/players/me/scopedIds`\n\nThe response will have one field:\n\n`developer_player_key (string)` - The user's ID which will be the same\nacross a developer's applications in their Google Play Console.\n| **Warning:** If a game transfers developer accounts, then the *developer player key* will change. **Therefore, you should not consider this as a stable\n| identifier, nor as a primary key to access progress.** This also should not be considered a Player ID when interacting with the PGS API. The developer player key should only be user to enable cross-game capabilities, as needed.\n\nRetrieve a list of Player IDs across your applications\n------------------------------------------------------\n\nYou can also retrieve a list of your user's Player IDs across the list of\napplications that are owned by your developer account. Please note that a user\nwill only have an ID for the games that they have been signed into with PGS.\n\n1. [Create a server-side web app](/games/pgs/android/server-access#create_a_server-side_web_app).\n2. Make [the following HTTP request](/games/services/web/api/rest/v1/players/getMultipleApplicationPlayerIds):\n\n `GET https://www.googleapis.com/games/v1/players/me/multipleApplicationPlayerIds`"]]