I just spent the weekend testing the new Claude connector on my own ad accounts. Here’s what it’s actually good at, the 5 prompts I’m running, and the safety setup that keeps you in control of every dollar.
If You Haven’t Connected It Yet
If you’re reading this and haven’t actually plugged Claude into your Meta account yet, do that first — the full setup walkthrough is here: Claude Can Now Run Your Meta Ads (Full Setup Walkthrough). Once it’s connected, this is what to actually do with it.
I used to work in Meta’s ads division before I quit to run my own businesses, so I’ve seen the inside of the ads ecosystem from both sides. Here’s the honest read after a weekend of testing this connector on real spend.
01
Live reporting from chat
Ask in plain English: “Build me a dashboard of my last 30 days, broken out by campaign, with spend, ROAS, CPA, and conversions.” Claude pulls live from your account and gives you the answer in seconds. No more ten-tab Ads Manager workflow.
02
Anomaly detection (this is the killer feature)
Meta built Claude a dedicated anomaly-detection tool. Ask “what looks off in my account this week” and it surfaces the things you’d miss — CPM spikes that came out of nowhere, frequency creep on a winning ad, conversion drops that a human review wouldn’t catch fast enough. This alone is worth setting up the connector.
03
Paused-by-default campaign creation
It can build campaigns, ad sets, and ads. Every single one ships in paused state. You flip them on yourself in Ads Manager when you’re ready — nothing goes live without your hand on the switch.
Run these in Claude with the Meta connector enabled. Replace the bracketed placeholders with your numbers and you’re live.
Prompt 1 — The Morning Brief
Prompt 2 — The Anomaly Scan
Prompt 3 — Creative Fatigue Audit
Prompt 4 — New Test Campaign (Paused)
Prompt 5 — Budget Reallocation Read
Two things to do before you give Claude write access to a real ad account:
01
Run read-only for the first few days
When you connect the integration in Claude, choose the read-only permission level. You’ll still get the reporting and anomaly detection — you just won’t be able to create or modify anything. Run it that way for at least 3–5 days so you trust the outputs before you give it write access.
02
Set an account-level budget cap
In Meta Business Suite, set a hard daily or monthly spend cap on the account before flipping write access on. Even if every campaign Claude creates ships paused, the cap is your floor of last defense. Set it conservatively — you can always raise it.
The Honest Take
The connector is genuinely useful. It’s not magic, and it can’t replace the judgment a real operator brings to scaling an account — but for the daily diagnostic work that used to eat 30 minutes of your morning, it’s a real win. Reporting + anomaly detection alone are worth setting it up.
For Your Job
If you’re ready to set up Claude for your specific job — with custom skills, connectors, and automations built around the work you do every day — I built a bootcamp just for you.
Start the Weekend Bootcamp →Go Even Further
If you’re looking to go even further, join mine and my husband’s community group where we give you all the AI agents and systems running our businesses.
Join the Community →© 2026 Mariah Brunner. All rights reserved.