Legacy Google+ APIs have been shut down as of March 7, 2019. Changes to the shutdown plan have been made recently which may mitigate its effect on some developers. Learn more.

Google+ integrations for web and mobile apps have also stopped functioning as of March 7, 2019. Learn more.

Google+ API Best Practices

The following best practices are tips to help you build high quality applications with the Google+ API. More tips will be added over time.

Developer Policies

Ensure that you are following the developer policies and branding guidelines. Avoid the following common mistakes:

  1. Provide a way for your users to disconnect their Google+ account from your application. When a user disconnects your app, you must delete any association with their Google+ account, revoke any currently active OAuth tokens for that user, and delete any information about the user that you have retrieved from the Google+ API.
  2. You must not interrupt or customize the sign-in flow that is invoked by the Google+ Sign-In button. The Google+ Sign-In button can only be used to invoke the Google+ Sign-In flow and must request the https://www.googleapis.com/auth/plus.login scope.
  3. Use Sign in with Google (without the +) to label the Google+ Sign-In button, do not use Google+ (with the +).
  4. Use only the official logos, available from our branding guidelines page, to indicate Google+ features available on your website or in your mobile apps.
  5. The Google+ Sign-In button must be displayed at least as prominently as other third party sign-in options available on your website or in your mobile apps. For example, buttons should be approximately the same size and have similar visual weight.


Explain what your application does. Make sure this explanation is located where users will definitely see it. Your application's landing page is a good place to put this.

Use your brand name (and not an internal code name) as the Product Name in the API Console. This Product Name will appear in the stream and in the user's account settings page. Note that the Product Name is different from the Project Name that the API Console initially requests.


Use Google+ Sign-In to ease the implementation of your OAuth flow See the quickstart samples for examples.

Ask for only the permissions you need. Asking for more permissions will reduce the number of users who finish the process for giving you access to their accounts. It will also increase the amount of effort you will have to spend explaining to users what you are doing with their data.


Gracefully deal with account failure. Assume that your application will lose access to the accounts of some users — either because they revoke their access token, delete their accounts or don't complete the sign-up process. Make sure that your application can detect when it no longer has access to a user's account and will stop trying to act on behalf of that user. If the user still wants access, sometimes you may be able to fix the problem by asking the user to go through the authorization process again.

Sharing and interactive posts

Craft your snippets for impact: Use schema.org markup to create compelling previews when your site is shared on Google+. See the snippet documentation for more information.

Pick accurate and compelling call-to-action labels for your interactive posts. In addition to the snippet, the call-to-action buttons feature prominently to help engage the user with your app.

Measure your social analytics You can use the Google+ Platform Insights to measure the engagement of your interactive posts, including clicks, views, and app installs.

Send feedback about...

Google+ Platform
Google+ Platform