Select Actions to adjust the guide

Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.

Action

Scope(s)

Loading actions...

Dynamic Guide URL

Scopes Selected


          
            Separator

Create or select a Google Cloud project

To use the Google Merchant API with OAuth 2.0, you need a Google Cloud project.

Select an existing project from the dropdown at the top of the page, or create a new one by clicking New Project and filling in the Project name, Organization, and Parent resource fields, then clicking Create.

Enable the Merchant API

Enable the Merchant API for your project. This step is required whether you created a new project or selected an existing one.

In the Google Cloud Console, navigate to APIs & Services > Library.

Search for "Merchant API", click on it.

New project: Click Enable to activate the API.
Existing project: If the API is already enabled, the button will show Manage. If it shows Enable, click it to enable the API.

Configure Google Auth Platform

Before creating OAuth credentials, ensure Google Auth Platform is configured.

In the Google Cloud Console, go to APIs & Services > OAuth consent screen. This will open the Google Auth Platform dashboard.

If you have already configured Auth Platform (the OAuth Overview page with usage metrics is shown), skip this step and navigate to the Branding page from the sidebar. Otherwise, you will see a Get started button — click it to begin the configuration process.

Fill in the required fields for your application.

App name: Enter a name for your application (e.g., StackOne Integration).
User support email: Select an email for user inquiries.
Click Next to continue.

Choose the appropriate user type for your application.

Internal: Only users within your Google Workspace organization can authorize (no app verification required).
External: Any Google account can authorize (requires app verification for production use).
Click Next to continue.

Provide email addresses for Google to notify you about any changes to your project. Click Next to continue.

Review your settings, agree to the Google API Services User Data Policy, and click Create to complete the setup.

Configure scopes

In Google Auth Platform, go to Data Access and click Add or Remove Scopes to configure the OAuth scopes your application needs. All three scopes below are required — `userinfo.email` is what lets the connector read the OAuth user's email at connect time to bootstrap the one-time GCP developer registration (without it, the consent screen will not return the email, and Google will not auto-grant the `API_DEVELOPER` role).

Enables actions: Batch Create Regions, Batch Delete Regions, Batch Update Regions, Claim Homepage, Create Conversion Source, Create Data Source, Create Notification Subscription, Create Online Return Policy, Create Region, Create User, Delete Conversion Source, Delete Data Source, Delete Local Inventory, Delete Notification Subscription, Delete Online Return Policy, Delete Product Input, Delete Region, Delete Regional Inventory, Delete User, Disable Program, Enable Program, Get Account, Get Autofeed Settings, Get Automatic Improvements, Get Business Identity, Get Business Info, Get Conversion Source, Get Data Source, Get Email Preferences, Get Homepage, Get Limit, Get Notification Subscription, Get Online Return Policy, Get Product, Get Program, Get Region, Get Service, Get Shipping Settings, Get Terms Of Service, Get Terms Of Service Agreement State, Get User, Insert Local Inventory, Insert Product Input, Insert Regional Inventory, Insert Shipping Settings, List Account Issues, List Accounts, List Aggregate Product Statuses, List Conversion Sources, List Data Sources, List Limits, List Local Inventories, List Notification Subscriptions, List Online Return Policies, List Products, List Programs, List Quotas, List Regional Inventories, List Regions, List Services, List Users, Render Account Issues, Render Product Issues, Retrieve Application Terms Of Service Agreement State, Retrieve Latest Terms Of Service, Search Reports, Undelete Conversion Source, Update Account, Update Autofeed Settings, Update Automatic Improvements, Update Business Identity, Update Business Info, Update Conversion Source, Update Data Source, Update Email Preferences, Update Homepage, Update Notification Subscription, Update Product Input, Update Region, Update User

Add all three Google scopes listed below. Omitting `userinfo.email` will cause the first-connect test to skip the auto-grant and require the API Developer role to be assigned manually.

In the Update selected scopes side panel that opens, check the required scopes from the list. `openid` and `https://www.googleapis.com/auth/userinfo.email` typically appear under Sensitive scopes (or Your sensitive scopes); `https://www.googleapis.com/auth/content` is the Merchant API scope.

If a required scope is not shown in the list (most commonly `https://www.googleapis.com/auth/content`), use the Manually add scopes section.

Enter the full scope URL in the input field.
Click Add to table.

Confirm and persist your scope configuration.

Click Update to apply the selected scopes. The side panel will close.
On the Data Access page, click Save to persist the scope configuration.
If you are updating an existing OAuth client (not creating a new one), end users on existing connections must re-authenticate to grant the new `userinfo.email` scope — otherwise the test action will still receive an empty email.

Create OAuth 2.0 client credentials

Set up OAuth client credentials to authenticate with the Google Merchant API. If you already have an existing OAuth 2.0 client, you can reuse it by adding the StackOne redirect URI and generating a new secret.

In the Google Cloud Console, go to APIs & Services > Credentials.

Skip this step if you are using an existing client.

Click + Create Credentials and select OAuth client ID.
Select Web application as the application type.
Enter a Name for your OAuth client (e.g., StackOne Merchant Integration).
Under Authorized redirect URIs, click Add URI and enter `https://api.stackone.com/connect/oauth2/googleshopping/callback`.
Click Create. A dialog will display your Client ID and Client Secret — copy and store them securely.

Skip this step if you created a new client above.

Click on your existing OAuth 2.0 client ID from the list.
Under Authorized redirect URIs, click Add URI, enter `https://api.stackone.com/connect/oauth2/googleshopping/callback`, and click Save.
Under Client secrets, click + Add secret to generate a new secret. Copy it and store it securely — it will not be shown again.
Your Client ID is shown on the same page under Additional information.

Add the authenticating user to Merchant Center

The Google account that completes the OAuth consent must already exist in the target Merchant Center account with Admin access. Without it, the connector's on-connect developer registration fails with `401 PERMISSION_DENIED_ACCOUNTS`.

In the Merchant Center UI, open Settings > Access and services > People and access and confirm the Google account that will complete the OAuth consent appears in the People table with role Admin and status Verified. If it is missing, click Add person to invite it as an Admin and have the invitee accept before continuing.

## Creating the StackOne Connector Profile To create the Connector Profile in StackOne for Google Shopping: Login to StackOne and navigate to [Connector Profiles](https://app.stackone.com/connector_profiles)

Click + Connector Profile
Search for and select Google Shopping
Select Type as OAuth 2.0
Fill out the fields using details retrieved from your provider:
- Client ID
- Client Secret
(Optional) Select Actions to be enabled for this Connector Profile
Click Create profile

Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Google Shopping.