Guide · paid-media-os
Connect paid-media-os by API, step by step
For anyone running paid-media-os without Climent Ads. These are the steps the system cannot do for you: only you can open these accounts.
Short answer: without Climent Ads, paid-media-os connects to Google Ads, GA4 and Meta through their official APIs. You create one Google Cloud project with Explorer access, sign in once with one command, set up to three Windows variables and add Meta’s connector with your own App ID. Then /welcome tests each source.
Why is Climent Ads the safer route?
By API, the file that opens your accounts sits on your own computer, and looking after it is your job. With Climent Ads you can disconnect each account at any time.
- A change reaches an account only after a person in your workspace approves that exact change, and each one can be undone.
- It shows you what it would change first, and waits.
- Every proposed action stops at an approval with an audit trail, and that step cannot be switched off.
- It reads Google Ads, Meta Ads, GA4 and Search Console every day, as one reading instead of four tabs, and shows which Tag Manager tag fires each conversion.
If the steps below are more than you want to own, ask me about it first.
Climent Ads is in private beta: accounts join one at a time. Email me and I will tell you if yours can join now.
What do I need before I start?
- Windows 10 or 11, with paid-media-os already installed.
- The Google Cloud CLI, called
gcloud. Install it first with Google’s Windows installer: the sign-in step needs it. - The
claudecommand, for the Meta step. The Claude app alone did not add it on the PC I checked. Typeclaude --versionin Command Prompt: if Windows does not recognize it, install it with Anthropic’s command for CMD. - One rule for the whole page: no key goes in the Claude chat, or in a file inside the system’s folder. That is the folder where paid-media-os is installed.
Nobody has walked this route from start to finish yet. The steps come from the package’s instructions and from Google’s and Meta’s documentation. If a step does not match what you see, email me.
How do I connect Google Ads?
- Create a Google Cloud project in the Cloud Console and enable the Google Ads API. It takes minutes. Write down the project ID.
- Ask for Explorer access. In that project, open Google Ads API Overview in the Cloud Console and request it. Google reviews it automatically and approves it in most cases. You do not need a manager account.
- Set up the consent screen in the same project (Cloud Console, Google Auth Platform, Audience). If the project belongs to a Google Workspace organisation, choose Internal. With a personal Google account only External is available: press Publish app, because while it says Testing, Google ends your sign-in after 7 days. When you sign in, Google warns you that the app is unverified. It is your own app: choose Advanced, then the link that starts with Go to.
- Create an OAuth client of type Desktop app in the same project, following Google’s instructions, and download its JSON file.
- Sign in once. Open Command Prompt (type
cmdin the Start menu), not PowerShell, which strips the commas. Paste the path of the file you downloaded below (hold Shift, right-click it, Copy as path) and the page writes the command. Run it on a single line, because Windows does not accept it split. Sign in with a Google user who has access to your Google Ads accounts.
gcloud auth application-default login --client-id-file=PATH_TO_CLIENT_JSON --scopes=https://www.googleapis.com/auth/adwords,https://www.googleapis.com/auth/analytics.readonly,https://www.googleapis.com/auth/cloud-platform
Google saves that sign-in at %APPDATA%\gcloud\application_default_credentials.json (Google, Application Default Credentials, read on 21 November 2026). These three permissions come from the setup pages of Google’s Ads server and its Analytics server, read on 7 November 2026. One file then serves Google Ads and GA4.
Last step: save them as Windows user variables. Fill in your IDs and run the command in the same Command Prompt. They stay in Windows, never in a file in the folder.
setx GOOGLE_APPLICATION_CREDENTIALS "%APPDATA%\gcloud\application_default_credentials.json" & setx GOOGLE_PROJECT_ID YOUR_PROJECT_ID
What you type in these boxes stays on this page, and nothing is sent. Then restart the Claude app.
Stuck on the consent screen or the command? Email me what you seeWhy does Google say no?
CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION: the project only has Test access. Go back to the Explorer step and request it.- You are not given Explorer or Basic: your project may be on the Google Cloud free trial, or have its billing suspended or disabled. Google lists it as a known issue, with the workaround, on its access page, read on 7 November 2026.
invalid_granta week later: the consent screen is still in Testing. Press Publish app and run the sign-in command again.- A tutorial asks you for a developer token: it is out of date. Google retired them on 9 September 2026. My guide to Google Ads API access has what changed.
How do I connect GA4?
- In the same Google Cloud project, enable the Google Analytics Admin API and the Google Analytics Data API.
- The Google user you signed in with needs read access to each property. Whoever administers the property gives it.
- Nothing else to set up. It uses the same credentials file.
How do I connect Meta Ads?
- Create your own Meta app in Meta for Developers and choose the use case for creating and managing ads. Write down its App ID, at the top of the app’s page. It takes minutes.
- Use a Meta user with access to the ad accounts. System user tokens with an admin role do not work with this connector.
- Open a terminal inside the system’s folder: go to that folder in File Explorer, type
cmdin the address bar and press Enter. Type your App ID in the box below, and the page writes it into the command. Run it there. The App ID goes only in that command, never in a file.
claude mcp add --transport http --client-id <META_APP_ID> meta-ads https://mcp.facebook.com/ads
The first time you use it, Facebook asks you to sign in and grant permissions. Meta asks for ads_mcp_management plus one of two ads permissions: grant ads_read if you only want to read, and ads_management if you want the system to apply the changes you approve. What each one allows is in my guide to connecting Claude to Meta Ads. Meta’s connector is in beta.
How do I know it worked?
Open the folder in the Code tab of the Claude app and type /welcome. It tests each source with one read and tells you which ones work. If one fails, it gives you the error in one line and moves on to the next.
Questions before you start
Do I need a manager account?
Not to start. Explorer access is requested from the Cloud project, without one. You only use one if you already reach your accounts through it, and then its ID goes in the optional variable.
Where do my credentials end up?
On your computer: the file the sign-in command creates, and the Windows variables that point to it. That is why nothing goes in the Claude chat or in a file inside the system’s folder.
What if a screen does not match these steps?
Menu names move. Email me what you see and I will tell you where to look.
Related reading
- Google Ads API access. The access levels, and what an MCP for your own accounts needs.
- Connect Claude to Meta Ads. The connector, its permissions and what each one lets Claude do.
- Google Ads MCP: the options. Google’s server, third-party ones and ours, and what each one can change.
- Meta Ads MCP: the options. Meta’s server, third-party ones and ours, and what each one can change.
Written by Manuel Climent · Last updated:
Who wrote this
I’m Manu. I’m a media buyer, and I built Climent Ads Assistant because no ads software I paid for was worth it. It reads Meta, Google Ads, GA4 and Search Console one client at a time, and changes a campaign only through a proposal that a person signs in the product.
Climent Ads is in private beta: accounts join one at a time. Email me and I will tell you if yours can join now.