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.

The steps ↓

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.

If the steps below are more than you want to own, ask me about it first.

Ask me about Climent Ads

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?

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.

Why does Google say no?

Still refused? Email me what Google shows you

How do I connect GA4?

  1. In the same Google Cloud project, enable the Google Analytics Admin API and the Google Analytics Data API.
  2. The Google user you signed in with needs read access to each property. Whoever administers the property gives it.
  3. Nothing else to set up. It uses the same credentials file.

How do I connect Meta Ads?

  1. 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.
  2. Use a Meta user with access to the ad accounts. System user tokens with an admin role do not work with this connector.
  3. Open a terminal inside the system’s folder: go to that folder in File Explorer, type cmd in 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.

Stuck on a step? Email me what you see, and I will tell you where to look

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

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.