Stay organized with collections
Save and categorize content based on your preferences.
When associating entitlements with a reader's Google Account, publishers must
create a publisher-provided identifier (PPID). The PPID is associated client-side,
and used in subsequent server-side calls for referring to the reader.
The PPID can be an existing publisher identifier for the reader, or a newly
created one, but must be stable for the reader. It cannot be updated without
the reader deleting and re-linking their account.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-06 UTC."],[[["\u003cp\u003ePublishers must create a stable, publisher-provided identifier (PPID) to associate entitlements with a reader's Google Account, which cannot be updated without the reader deleting and re-linking their account.\u003c/p\u003e\n"],["\u003cp\u003eThe initial Google Account and PPID association is done client-side using the JavaScript API, while all other operations are handled server-side.\u003c/p\u003e\n"],["\u003cp\u003ePublishers are responsible for storing the association between the PPID and their internal reader records, ensuring PPIDs adhere to RFC3986 Section 2.3 for formatting.\u003c/p\u003e\n"]]],[],null,["# Creating Publisher-Provided IDs (PPIDs)\n\nWhen associating entitlements with a reader's Google Account, publishers must\ncreate a publisher-provided identifier (PPID). The PPID is associated client-side,\nand used in subsequent server-side calls for referring to the reader.\nThe PPID can be an existing publisher identifier for the reader, or a newly\ncreated one, but must be stable for the reader. It cannot be updated without\nthe reader deleting and re-linking their account.\n\nThe initial association between a Google Account and a PPID is done exclusively\nusing the [client-side JavaScript api](/news/subscribe/subscription-linking/implementation/client-side). All other features are done\nusing the [server-side integration](/news/subscribe/subscription-linking/implementation/server-side).\n| **Note:** When creating a PPID, the publisher must store the association between the PPID and their internal record for the reader.\n\nPPID requirements\n-----------------\n\n1. PPIDs must conform to [RFC 3986 Section 2.3](https://datatracker.ietf.org/doc/html/rfc3986#section-2.3)\n\n - RFC 3986 allows the following `unreserved` characters: `ALPHA\n / DIGIT / \"-\" / \".\" / \"_\" / \"~\"`\n - This means PPIDs can include uppercase and lowercase letters, numbers, hyphens, periods, underscores, and tildes.\n2. The maximum length allowed is 150.\n\n const publisherProvidedId = 'ASDF_jkl-1234.~'"]]