Partner Connector requirements

Stay organized with collections Save and categorize content based on your preferences.

Review the Publishing overview to understand the benefits and required level of commitment for publishing a connector. To publish a Partner Connector, your connector must meet all of the requirements described below.

Apps Script

  1. Share view access of your Apps Script project with the following:
  2. Create a deployment named Production and update the Production deployment to the version of code you intend to publish.

Manifest

Include the following in your connector's manifest. View the manifest reference for more information.

dataStudio

  1. description should provide information and instructions for a basic understanding of the connector and how to use it. Connectors with vague and incomplete descriptions will be rejected.
  2. addOnUrl should be a dedicated hosted page about your connector, preferably hosted on your own domain. The page must include the following:
    • A Privacy Policy and Terms of Use or a link to this content, on the same domain as the addOnUrl.
    • Details the user will need to know to use your connector.
    • The sign up link, if an account is required to use your connector,.
    • Content hosted preferably on your domain. Hosting on https://sites.google.com/ is not allowed.
    • See example pages from existing partners: Funnel, Supermetrics, CallRail.
  3. supportUrl should be a hosted page to get support for your connector. This cannot be an email or mailto link.
  4. logoUrl should point to a static image hosted under your control. You cannot use images served by Google services on domains such as *.gstatic.com, *.ggpht.com, *.google.com, *.googleusercontent.com. Using Google Cloud Storage to serve images from the *.googleapis.com domain is acceptable and is a recommended hosting option.
    • Connectors with animated icons will be rejected. Use static images.
    • It's recommended to use at minimum, a 48x48-pixel image.
    • Avoid text-only images that are difficult to read when scaled down to 48x48-pixels.
  5. Populate the sources property with all sources your connector connects to. See Sources in Manifest reference for details.
    • You can view the existing list of sources at Data Registry Repository. If the source you are connecting to does not exist in the repository, send a pull request to the Data Registry Repository to add the source. Your connector will fail the review process if the sources in your manifest do not exist in the repository.
    • This is additional metadata for the connector that will be indexed for search feature in the gallery. Your connector will show up in the search results when users search for a specific source in the gallery.
  6. Provide values for shortDescription, authType, feeType, privacyPolicyUrl, and termsOfServiceUrl.
  7. name should directly represent the purpose of the connector. A clear name will help users determine whether your connector meets their needs. Avoid using the word connector in the name since users already know they are looking at a connector.
    • Do not include special or non-visible characters with the intention of drawing attention to or potentially altering the position of your connector.
  8. Do not use shorthand names for Data Studio anywhere in the manifest (e.g. GDS, DS, etc.).
  9. Emojis are not allowed in any manifest field (description, shortDescription, name, etc). In general, do not include special or non-visible characters with the intention of drawing attention to your connector.
  10. If your connector has a fixed schema, create a report template for your connector and add it to the manifest. Enable Sharing by link for the report.

urlFetchWhitelist

  1. Limit the number of endpoints called by UrlFetchApp to those absolutely required for connector functionality. Add the urlFetchWhitelist property to the root level of your manifest. View the urlFetchWhitelist reference for more info.
    • Include all endpoints used with the UrlFetchApp service.
    • If your connector does not fetch resources using the UrlFetchApp service, set urlFetchWhitelist to an empty list [].
    • If your connector does not connect to a set of fixed endpoints or the endpoint prefix varies, omit the urlFetchWhitelist property and provide details in the Exception for urlFetchWhitelist form field when submitting the review request.

oauthScopes

  1. Set explicit OAuth scopes in the manifest. Connectors without explicit OAuth scopes will be rejected.

Connector

  1. If the user needs an account to use the connector, make sure the connector description or the addOnUrl link provides instructions to help the user create one.
  2. Your connector cannot be in unfinished or beta status. You have to publish a complete and functional connector. You can always update your connector but the production deployment that is released to users should be tested and feature complete.
  3. Provide meaningful and actionable error messages to users when users encounter a Connector internal error. This includes cases when a user provides invalid/blank input at configuration.
  4. shortDescription, description, addOnUrl link, supportUrl link, and OAuth page (if applicable) should be free of spelling and grammatical errors.
  5. shortDescription cannot contain URLs.
  6. Use authentication methods provided by getAuthType(). Do not request credentials via getConfig().
  7. Complete the OAuth Client Verification process. The verification is mandatory for all connectors regardless of the authentication method in getAuthType(). The verification process is a different process from the connector review and is handled by a separate team, not Data Studio. Consult the OAuth API Verification FAQ for more info. Your connector will be rejected if the OAuth Client Verification process is not completed.
    • During the OAuth verification process, add your connector's required OAuth scopes as part of the OAuth consent screen configuration. If you fail to add all required scopes, you might pass the OAuth verification process but your connector will still show the Unverified app screen. This will cause the Partner Connector verification process to fail.
      Authorize and test your connector using a new account after passing the OAuth verification process to ensure that Unverified app screen is not displayed to your users.
  8. Ensure you adhere to the Data Studio Galleries Terms of Service (Submitter).

Once you have met all the requirements, click the following button to request a review for your connector:

Publish your Partner Connector