Guides / API tokens
How to create a Google (Analytics and Search Console) API token with the narrowest permissions
Shipyard uses a Google (Analytics and Search Console) token for analytics and search. The token is stored in your computer's keychain and is not sent to shipyardmcp.com. These are the exact steps, and the smallest set of permissions that works.
Create the token
Start here: https://console.cloud.google.com/iam-admin/serviceaccounts
- In Google Cloud create a project (any name), then a service account in it. No roles are needed.
- Enable three APIs in that project: Google Analytics Admin API, Site Verification API, Google Search Console API.
- Service account, Keys, Add key, JSON. A file downloads.
- In Google Analytics: Admin, Account access management, add the service account email as Editor.
- Give Shipyard the path to the file, your Analytics account ID and your own Google email.
Permissions, and why each one is needed
- analytics.edit: Create the GA4 property and its web stream.
- siteverification: Prove you own the domain with a DNS record.
- webmasters: Add the property to Search Console and submit the sitemap.
Set up once in Google (Analytics and Search Console) before your first launch
- Create a Google Analytics account and accept its terms. Shipyard adds a property to it; it cannot create the account. (https://analytics.google.com)
What stays manual
These are things only a person can do at this provider. Shipyard cannot and will not do them for you.
- Creating the Google Analytics account and accepting its terms.
- Google's review of the OAuth consent screen, if your app offers Google sign-in.
What you paste into Shipyard
- Path to the service account key file (.json)
- Google Analytics account ID (numbers only): Google Analytics, Admin, Account details.
- Your Google account email (becomes an owner in Search Console)
Have this set up for you
Shipyard connects your accounts once and then does all of this for every new product, in about an hour.
See how it works