Pause Meta ad sets over your cost per lead
Ask and the agent pauses Meta ad sets that spent enough to judge but cost more per lead than your target.
Letaido's Facebook Ads integration puts an AI agent on your Meta ad accounts: daily logs, alerts and cost checks, scheduled or on request.
Checked step by step. Open one to watch it run.
Ask and the agent pauses Meta ad sets that spent enough to judge but cost more per lead than your target.
Every morning, the agent checks for Meta ads that were disapproved or have issues and posts them to Slack.
Every morning, the agent adds yesterday's spend, clicks, CTR, CPC and purchases per Meta campaign to your sheet.
Every Monday, the agent posts last week's Shopify revenue per dollar of Meta spend next to Meta's own reported ROAS.
Every Monday, the agent adds a Notion page with last week's Meta results by campaign and what changed from the week before.
Every Friday, the agent drafts a short Meta Ads update for your client in Gmail.
Five ways to hook up Meta Ads, and what each is good at.
| Option | Set up by asking | Works across your apps | Runs on its own | No code | Syncs lead form leads |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Conversions API and partner integrations | No | Partly | Yes | Partly | No |
| Zapier, Make and similar | No | Yes | Yes | Yes | Yes |
| Meta Marketing API | No | Partly | Yes | No | Yes |
| Meta Ads MCP server | Partly | No | No | Yes | No |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | Type the job. The agent reads ad accounts and insights, pauses ad sets or builds paused campaigns and ad sets, and mixes Meta with 64 other apps. | Daily logs, disapproval alerts, cost checks and client updates. | 65 apps, not thousands. It can't read Lead Ads form leads. |
| Conversions API and partner integrations | Your website platform, CRM or server sends purchases and other events to Meta. A Pixel site can set it up from Events Manager. | Better measurement and ad delivery from your own conversion data. | Sends data to Meta. It doesn't report back or change ads. |
| Zapier, Make and similar | Workflows built mostly from Facebook Lead Ads triggers, sending new leads to a CRM, email tool or sheet. | Getting lead form leads to sales quickly. | One Zap per lead path, built by hand. |
| Meta Marketing API | Developers create, update, pause or delete ads and read insights across Facebook, Instagram, Messenger and WhatsApp. | Custom builds by an in-house team. | Needs developers and a Meta app. |
| Meta Ads MCP server | Meta's remote MCP server lets AI clients such as Claude and ChatGPT report on, create and edit campaigns, ad sets and ads. | Managing ads by chatting. | Meta is rolling access out gradually, and it works when you chat. |
Connect Meta Ads once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
Save it to run on a schedule.
Every Meta Ads job starts at a set time or when you ask.
In Meta Business Settings, open Users, then System users, and add one. Assign it each ad account the agent should use.
Generate a token for the system user with ads_read and ads_management, set to never expire, and paste it into Letaido.
Only if your Meta app has Require App Secret turned on, also paste the app id and app secret.
Allow all read operations once per app; approve each kind of write once. After that it repeats on its own.
28 actions across 9 groups, from reporting to campaigns, ad sets and ads.
In Meta Business Settings, create a system user, assign it your ad accounts and generate a token with ads_read and ads_management that never expires. Paste the token into Letaido.
Yes. Instagram ads run from the same Meta ad accounts, so the jobs read and change them the same way as Facebook ads.
No. The connector reads campaigns, ads and insights. Lead form leads need a lead tool or a workflow tool such as Zapier.
Yes. Meta runs a remote Ads MCP server for AI clients such as Claude and ChatGPT, and is rolling access out gradually. Letaido is not an MCP server. It has its own Meta Ads connector, mixes it with apps like Shopify and Slack, and runs jobs on a schedule.
Only when a job asks for it, like pausing ad sets over your cost per lead. Allow all read operations once per app; approve each kind of write once.
No. Meta Ads jobs run on a schedule, like the morning disapproval check, or when you ask in a chat.
Connect Meta Ads, then ask for a job like "Pause Meta ad sets above our target cost per lead". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoView Meta ad account details including name, currency, timezone, status, and spend information.
Pull impressions, clicks, spend, reach, CTR/CPC/CPM, and conversions at the account, campaign, ad set, or ad level over any date range.
Submit heavy insights queries as background jobs and retrieve the results once complete.
Create, edit, pause, activate, or delete Meta campaigns including budgets, bid strategy, and objectives.
Create, edit, pause, activate, or delete Meta ad sets including targeting, budgets, scheduling, and optimization goals.
Create, preview, pause, activate, or delete Meta ads and upload images for use in creatives.
Search Meta's targeting taxonomy and estimate audience size before building an ad set.
List existing custom audiences in a Meta ad account with size and delivery status.
Make raw Meta Graph Marketing API calls for any endpoint not covered by other capabilities.