Open source · Apache-2.0
Climent Ads Assistant
The console that reads Meta Ads, Google Ads, Google Analytics and Search Console every morning, works out what actually moved, and hands you the answer — or hands it to your Claude. It proposes; nothing moves until you say yes.
Climent Ads Assistant is an open-source console for people who run ads for other people. It reads the four accounts that never agree with each other, on a daily schedule, and turns them into one reading instead of four tabs. It is built around approval: it works out what it would change and shows you first. And it answers questions — you can point Claude or ChatGPT at it and ask about a client account in your own words, with every answer carrying a line that says what it did not touch. Apache-2.0, self-hostable, with a runnable demo on synthetic data.
What it reads
Meta Ads
Campaigns, ad sets and creatives, plus what changed since last week.
Google Ads
Search terms, budgets and the change history nobody opens in time.
Google Analytics
Traffic and conversions, checked against what the ad platforms claim.
Search Console
The organic side of the same question, so paid is not judged alone.
Google Tag Manager
Which tag fires each conversion, and on which site.
How the loop runs
You grant access
Per account, and you take it back whenever you want. It only ever sees the accounts you point it at.
It reads on a schedule
Once a day, on closed days. No live polling, no surprise API usage, no dashboard to babysit.
You ask it, in your words
Point Claude or ChatGPT at it and ask what happened in a client account. It answers from the data it already read — it does not go and change anything to find out.
You approve the change
Climent Ads Assistant works out what it would do and shows you first. Nothing moves on its own, and that is the whole point.
What it uses from each account, and why
You connect each account yourself and can disconnect it at any time. Reading happens once a day. A change happens only after a person in your workspace approves that exact change, and each one can be undone. How the data is stored, shared and deleted is in the privacy policy.
Google Ads
Reads, and changes you approve
Campaign, keyword and search-term reporting and the change history, to show what moved and why. Campaign settings (status, dates, budget, bid targets) and conversion actions change only after you approve each change.
Google Analytics 4
Reads, and changes you approve
Traffic, key events and landing pages, to check what the ad platforms claim. Annotations, key-event settings and events built from a page view change only after you approve each change.
Search Console
Reads only
Clicks, impressions, click-through rate and position by page and query, so paid is not judged without the organic side.
Google Tag Manager
Reads, and changes you approve
Containers, tags and triggers, to check which tag fires each conversion. An approved tag change is published as a new version, and the undo is another version.
Meta Ads
Reads, and changes you approve
Campaigns, ad sets, ads, creatives and their daily results. Status, budgets, schedule and names change only after you approve each change, and the images you upload go to the ad account library.
The part you can check yourself
You can point Claude or ChatGPT at it and ask about a client account in your own words. What comes back is a reading, and every reading carries a line saying what it did not touch — not a claim on a marketing page, a field in the response.
What every answer carries
Climent Ads Assistant reads four ad and analytics accounts and answers questions about them. It changes a campaign only through a proposal that a person signs in the product. So the worst it can do on its own is be wrong out loud, where you can see it, instead of quietly.
Read what each platform gives it: Meta Ads, Google Ads, Google Analytics and Search Console. And the Google Tag Manager container behind them, to check which tag fires each conversion.
The rest of it
Where to go from here
Four different people land on this page. Pick the one that is you.
You want to see it work before you believe any of it
Fair, and it is the fastest route
There is a runnable demo on synthetic data. No credentials, no account connected, nothing of yours touched. Walk it first and decide afterwards.
You want to know whether it reads your platform
Meta, Google Ads, GA4, Search Console
Each platform has its own page saying what is read, at what level, and what is not covered yet. If the answer is not there, it is not read, and you should assume that rather than hope.
You would rather run it yourself than trust us with access
Self-hosted, MIT
Self-hosting is the version we would pick too. The code is public, it runs on your machine, and the rollups stay there. You are not buying access to a dashboard you cannot see inside.
You want the number before the conversation
Pricing
The price is on the page rather than behind a call. If it does not fit, that is a two-minute answer instead of a forty-minute one.
You want it to run the account for you
Then this is not it
Climent Ads Assistant reads, reports and proposes. It changes a campaign, a budget or a tag only after a person approves that exact change, and it never approves one itself. That is a design decision rather than a missing feature. If what you want is autonomy, you want a different product and you will be happier saying so now.
The Paid Media Capacity Check
Being built now. You will connect one ad account and see what your team should look at first, and why. The free audit it replaces is closed.