Your readers can sign in to third-party websites and apps quickly and securely with Google Identity Services (GIS), also known as Sign in with Google. They can enjoy a fast, low-friction sign-in and registration experience through Google One Tap which is the key feature of GIS. This integration with Reader Revenue Manager (RRM) provides 3 key benefits:
- Multi-prompt coordination: RRM prompts, like paywalls and One Tap pop-ups, coordinate to prevent conflict so readers get only one sign-in request at a time.
- Unified sign-in: Google One Tap powers the RRM registration wall and replaces the multi-step sign-in process with a single-click experience. This reduces friction and prevents high onboarding drop-off rates.
- Automatic entitlements: RRM automatically recognizes readers who sign in through Google One Tap. This provides them instant access to their subscriptions and metered content. Publishers can use GIS to sign-in without RRM prompts.
Set up Sign in with Google
If you’re new to Sign in with Google and Google One Tap, use these resources to learn the implementation basics:
- Sign in with Google: Learn about overview of Google Identity Services.
- Implement Sign in with Google via button: Learn how to display the Sign In With Google button.
- Implement Google One Tap: Learn how to display Google One Tap.
Here are the overall steps to get started with Google One Tap.
- To configure your OAuth Consent Screen, follow the steps described in Setup.
- Obtain a client ID and load the client library.
- To place a code snippet on pages where you want to use Google One Tap, select HTML or
- To configure a callback to handle a credential response, use either HTML or JavaScript.
Set up registration wall in Publisher Center
The Publisher Center's new guided experience simplifies your Sign in with Google integration. This streamlines how to get credentials and install scripts.
- To Setup, click Reader Revenue Manager
Content Access.
- Click Reader funnels
- Tip: For Enterprise publishers, the “Reader funnels” menu is labeled “Overview.”
- Turn on Sign in with Google.
Content Access.
- Follow the steps in ”Set up Sign in with Google.”
- Paste a website URL that has Google One Tap on.
- Click Verify.
- Confirm that the message has changed to “Reader registration is set up to use Sign in with Google for account creation.”
Integrate client-side code
To integrate the Google One Tap API with the RRM Reader Registration feature:
- Initialize
swg.js:- For the Standard version of RRM, learn how to add code snippets to your site.
- For an Enterprise publisher, learn how to include and initialize swg.js.
- Add the
rrm_interopandcallbackparameters to your GIS snippet:- To enable prompt deconfliction, add the
data-rrm_interop='true'parameter to your Google One Tap HTML snippet or includerrmInterop: truefor the JavaScript API. - Configure GIS to use a callback function (e.g.,
handleCredentialResponse) to receive the credential token. Detailed implementation instructions forhandleCredentialResponseare provided in the following step.
- To enable prompt deconfliction, add the
HTML API example:
JavaScript
<div id="g_id_onload"
data-client_id="YOUR_GOOGLE_CLIENT_ID"
data-login_uri="https://your.domain/your_login_endpoint"
data-your_own_param_1_to_login="any_value"
data-your_own_param_2_to_login="any_value"
data-callback="handleCredentialResponse"
data-rrm_interop='true'>
</div>
JavaScript API example:
JavaScript
google.accounts.id.initialize({
client_id: 'YOUR_GOOGLE_CLIENT_ID',
callback: handleCredentialResponse,
rrm_interop: true,
});
- Processing the credential in the callback
- To complete the integration, process the GIS credential using
processGisCredential. Depending on your setup, you will add this to either theSWG_BASICqueue (for Reader Revenue Manager Standard) or theSWGqueue (for Reader Revenue Manager Enterprise).
- To complete the integration, process the GIS credential using
For Reader Revenue Manager Standard (RRM:S) using SWG_BASIC:
JavaScript
function handleCredentialResponse(response) {
if (response.credential) {
(self.SWG_BASIC = self.SWG_BASIC || []).push((basicSubscriptions) => {
basicSubscriptions
.processGisCredential(response, {
gisClientId: 'YOUR_GIS_CLIENT_ID',
});
});
}
}
For Reader Revenue Manager Enterprise (RRM:E) using SWG:
JavaScript
function handleCredentialResponse(response) {
if (response.credential) {
(self.SWG = self.SWG || []).push((subscriptions) => {
subscriptions
.processGisCredential(response, {
gisClientId: 'YOUR_GIS_CLIENT_ID',
});
});
}
}
This ensures that the credential returned by GIS is properly passed to and processed by Reader Revenue Manager, completing the synchronization of sign-in state and entitlements for both versions.