此外,開發人員會透過 Google 儲存喚回符記,該符記會對應至使用者的遊戲內帳戶。Google 會根據使用者的 PGS 設定檔自動儲存喚回符記。
使用者現在決定首次在 Google Play 遊戲電腦版上玩遊戲。系統會自動透過 PGS 帳戶登入使用者,而遊戲用戶端會檢查該 PGS 使用者是否存有遊戲進度。接著,遊戲伺服器向 Google 查詢該 PGS 帳戶是否存有任何符記。假設有的話,Google 就會傳回喚回符記,而遊戲伺服器會使用該符記尋找與使用者相關聯的「Racer94」帳戶,並還原其遊戲進度。由於 PGS 登入體驗順暢無阻,使用者不必輸入使用者名稱或密碼,應用程式就能還原使用者的進度。此外,開發人員可使用 PGS 登入功能搭配現有的身分識別系統,並藉由 Google 來儲存玩家進度與 PGS 帳戶之間的連結。
如前述範例所示,Recall API 執行了兩個主要動作:
使用者透過遊戲內帳戶登入時,儲存 Google 憑證。
擷取使用者的符記,以便還原其遊戲內帳戶。
除了喚回符記,Recall API 也會要求與遊戲內帳戶對應的穩定 ID (稱為「人物角色」),以強制執行基數限制。您可以將人物角色視為開發人員身分識別系統中代表使用者遊戲內帳戶的標籤,而喚回符記就是用來將使用者遊戲內帳戶還原到遊戲的金鑰。在不同的 PGS 專案中,人物角色和符記值皆不得重複使用。此外,雖然喚回符記可能會隨著時間變更,但人物角色應隨著使用者的遊戲內帳戶保持穩定不變。
[null,null,["上次更新時間:2025-07-26 (世界標準時間)。"],[],[],null,["# Recall API\n\nThe Recall API lets games manage links between Google Play Games Services (PGS) users and\ntheir in-game accounts by storing *recall tokens* with Google servers. Here's a\nsample scenario of how the Recall API might be used.\n\n1. A user is playing a game where the developer has an identity system to track\n user progress, and uses PGS in parallel with other authentication methods to\n log users into their game. In this example, a user is logged into their PGS\n account *Laura* , and creates an in-game account with the developer's\n identity system called *Racer94*. As the user plays the game, the\n developer's game server syncs their progress.\n\n2. Separately, the developer saves a recall token with Google, which\n corresponds with the user's in-game account. Google automatically stores\n that recall token against the user's PGS profile.\n\n3. The user now decides to play the game on [GPG on\n PC](/games/playgames/overview) for the first time. The user is automatically\n signed in with their PGS account, and the game client checks to see if there\n is any progress available for this PGS user. The game server then queries\n Google to see if there are any tokens for this PGS account. Since there are,\n Google sends back the recall token, and the game server uses that token to\n find the user's associated account Racer94, and restore their progress.\n Since signing in with PGS is a frictionless experience, the user's progress\n is restored by the app without the user needing to enter a username or\n password. Furthermore, the developer can use PGS sign-in with their existing\n identity system, and rely on Google to store the link between player\n progress and their PGS account.\n\nAs seen in the example earlier, there are two main actions which are performed\nby the Recall API:\n\n- **Storing** the token with Google when a user logs in with one of the in-game\n accounts.\n\n- **Retrieving** the token for a user in order to restore their in-game\n accounts.\n\nIn addition to recall tokens, the Recall API also requires a stable identifier\ncorresponding to the in-game account, known as *persona* , to enforce\n[cardinality constraints](#enforcing-cardinality). You might think of a persona\nas the label which represents the user's in-game account within the developer's\nidentity system, and the recall token as a key which is used to restore the\nuser's in-game account to the game. Persona and token values must not be reused\nacross different\n[PGS projects](/games/pgs/console/setup#add_your_game_to_the).\nAlso, while recall tokens may be changed over time, a persona should be stable\naccording to the user's in-game account.\n| **Note:** Strings used for recall tokens and personas must be opaque and not contain any sensitive or personally-identifiable information (including but not limited to name, email address, and demographics). Games must use robust encryption algorithms for generating recall tokens.\n\nCardinality rules\n-----------------\n\nThe Recall API enforces a 1:1 relationship between PGS profiles and in-game\naccounts (referred to as *cardinality rules*), where one persona can only be\nlinked to one PGS profile, and one PGS profile can only be linked to one\npersona. The persona is used as a stable identifier for an in-game account,\nsince recall tokens may change over time.\n\nThe persona linked to a PGS profile may also be changed over time (as different\nin-game accounts are linked to the PGS profile).\n\nTechnical flows for storing and retrieving the recall tokens\n------------------------------------------------------------\n\nThis section covers the technical flow between the game client and servers with\nGoogle servers when storing and retrieving recall tokens.\n\n### Step 1: Sign in the PGS User and retrieve the session ID\n\nThe game initializes the PGS SDK and attempts to sign the user in with PGS.\n\nAssuming the user is signed in, request a session ID from the Games SDK on the\ngame client, and request an OAuth 2.0 token from Google's OAuth backend. The\nsession ID and OAuth 2.0 tokens are used to communicate with the Google Games\nbackend.\n\n### Step 2: Retrieve any available recall token\n\nRequest for any associated recall token with the PGS user's account. If a token\nis present, [proceed to Step 3a and restore progress](#restore-progress).\nOtherwise, if this is a new user and they have no token present, [proceed to\nStep 3b and store a new token](#store-tokens).\n\n### Step 3a: If token is present, restore progress\n\nIf a token is present, retrieve and decrypt the token, and restore user data.\n\n### Step 3b: If no token is present, store a token\n\nSince no token is present, no progress is restored. The user proceeds to sign in\nwith the developer's identity system, or creates a new account if one does not\nexist. Note - this isn't signing in with PGS (which has been done already), but\nwith a developer's identity system outside of PGS.\n\nCreate an encrypted recall token which encodes the user's in-game account, and\nsend it to Google along with the session ID and OAuth 2.0 token. At this point,\nGoogle creates an association between the recall token which was sent, and the\nplayer's PGS account.\n\nFlows for users without a PGS profile\n-------------------------------------\n\nYou can store recall tokens for a user who hasn't created a PGS profile yet by\nusing profileless mode. However, there are two important caveats:\n\n- You can't retrieve tokens for a user who doesn't have a PGS profile. Profile creation is automatically prompted when the user tries to log into your game with Play Games Services on a second device.\n- You must follow [additional guidelines](/games/pgs/recall/recall-setup#terms) to ensure you have an appropriate notice describing the following items and obtaining the appropriate end-user consent:\n - Your sharing of the data with Google to enable the Play Games account linking feature.\n - The availability of settings to manage this sharing, such as Play Games settings.\n - The processing of such data under the [Google Privacy\n Policy](https://policies.google.com/privacy).\n\n### Store a token and persona pair\n\n1. A user without a PGS profile opens a game that has profileless recall enabled.\n2. The Games SDK triggers an automatic sign-in, which fails because the user has no PGS profile.\n3. The Games SDK shows a snackbar that informs the user that the game has integration with Google. This snackbar is actionable---the user can disable recall until a profile is created.\n4. The game requests recall access. Note that PGS rejects recall access requests when there are PGS profiles on the device or when there are no Google Accounts on the device. In that case, the game should proceed without using PGS.\n5. After the user logs in with an in-game account, the game creates a token and persona pair for the user that corresponds to their in-game account. The game stores this pair with Google. The game might store more tokens later if the user logs into other in-game accounts.\n\n### Launch a game on a new device\n\n1. A user without a PGS profile opens a game that has profileless recall enabled on a device.\n2. The game records a profileless recall token as described in [Store a token\n and persona pair](#profileless-store).\n3. The user opens the same game on a different device that has the same account setup.\n4. The Games SDK triggers profile creation. The user can review and reject previously stored recall tokens. The user creates a PGS profile at this time.\n5. The automatic sign-in into PGS completes, and the game receives the authenticated status.\n6. The game retrieves recall tokens for the user as usual.\n\nNext steps\n----------\n\nIn order to integrate the Recall API with your client and game server, [follow\nthis guidance](/games/pgs/recall/recall-setup)."]]