Meta ads · Daily review
RelayPerformance marketingRunning Meta ads from the same workspace as your creative
Performance teams spend their mornings pulling the same numbers out of Ads Manager. These field notes cover connecting Meta ads to Agent Serve, asking questions in Chat, and letting a Relay send a daily review that a person acts on.
Valnora & Elric team6 min read
Most performance marketers start the day the same way: open Ads Manager, sort by spend, work out what changed overnight, then decide what to pause and what to push. These notes cover moving that routine into Agent Serve, so questions, drafts and the daily review happen next to your creative and your store data, and a person still approves every change that spends money.
How does Agent Serve connect to Meta ads?
There is no built-in Meta Ads block. Meta publishes an official ads server for AI tools, built on MCP, an open standard that lets an AI assistant call another service's actions. You add it once under Settings → Tool connections with its address, https://mcp.facebook.com/ads, and sign in with a Meta account that already has access to your ad accounts.
Its tools then work in Chat: listing accounts, reading campaign insights, and creating or drafting campaigns and ad sets. Meta decides which tools the server offers, so check the list after connecting. Relays can use the same connection once it is on their allowlist, through the workspace’s connected account. Reads run; anything that changes a campaign waits for approval.
What can you ask in Chat?
Start with questions you already answer by hand.
- "Summarize the top-spending campaigns over the last 30 days, with ROAS and CPA."
- "Which ad sets spent more than ₹20,000 last week with a CPA above ₹700?"
- "Compare the UGC-style ads against studio images in the Diwali campaign."
Chat answers from the account data, and you can ask follow-ups in the same thread. It can also draft: a new ad set for a product launch, using the audience and budget you describe, or a campaign in draft that a person reviews in Ads Manager before it runs. Creative made in the same workspace, such as UGC-style images or product video ads, is already in the Library with its provenance.
How does the daily Relay review work?
Meta ads in Chat, a daily Relay review and a dashboard
Data · Connection
- 01Meta ads serverAdded in Settings → Tool connections for Chat and allowed Relays; lists accounts, reads insights, drafts campaigns.
- 02Daily ad metricsA scheduled workflow calls the insights API with an API block and stores spend, purchases and revenue per campaign per day.
Relay · Daily review
- 03Every morningSchedule trigger at 9:00 in your time zone.
- 04Review performanceReads yesterday and the last 7 days from the metrics table, compares with targets in its instructions.
- 05Recommend, then approveBudget increases, pauses and new campaigns wait in the review queue until a person approves.
- 06Recommendations emailDrafted to the growth lead; sent only after approval.
Dashboard · Performance
- 07Spend, ROAS, CPAPanels over the daily metrics table, by campaign and by week.
- 08CPA monitorAlerts by email, in-app or Slack when CPA crosses your limit.
A Relay is an AI coworker with a role, instructions and its own access. Give it a schedule trigger, such as 9:00 every morning in your time zone, and instructions that spell out your targets: the CPA limit per campaign type, the ROAS floor, how many days a new ad gets before it is judged.
Bind it to the daily metrics table described further down, which a scheduled workflow fills before the Relay runs. Each morning it reads yesterday and the last seven days from that table, checks live insights through the Meta connection when a number looks off, compares them with your targets and writes a short review. It drafts the email to the growth lead and reports in its own chat with a notification.
What the solution produces
Daily review email (illustrative, waiting for approval)
MessageSubject: Meta ads review · Tuesday
Yesterday: ₹61,200 spent, 104 purchases, CPA ₹588, ROAS 2.8.
"Prospecting · new kurtas" has run 9 days at a CPA of ₹940, 57% above the ₹600 target. Two of its four ads take 80% of spend; both use the same studio image.
Recommendation: pause the two studio-image ads and give the UGC-style variants a fair test. Approve the pause in my review queue, or make the change in Ads Manager.
"Retargeting · 7-day viewers" is at ₹380 CPA and spending its full budget by 6 pm. Consider a budget increase.
No action taken. All figures from the daily metrics table, built from Meta’s reported data, which can change for a few days as conversions are attributed.
Emails always need approval under Assist or Operate autonomy, so the review is sent only after someone approves it. Keep the recipient policy on internal only, the default.
What stops it from spending money?
Three settings matter.
- Chat asks before a connected tool runs. With tool permissions on, each call to a connected tool shows Allow, Always allow or Skip. Choose Always allow only for read tools such as insights, never for tools that create campaigns, resume ads or change budgets.
- The Relay classes every call. Each Meta call is a read, write, destructive or spend. Reads run. On Assist, a pause waits for approval; budget changes and new spend always wait, unless they fall within delegated limits you set. The approved call runs exactly once and is audited.
- A kill switch. One switch pauses the Relay, or the whole team of Relays, if anything looks wrong.
By default a Relay runs up to 25 tasks a day, two at a time, which is plenty for one review.
Controls and governance
Approvals before action
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
Audit trail
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
Roles and permission groups
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
Run logs
Every workflow run records each block’s inputs, outputs and errors, so a reviewer can trace how a result was reached.
SSO and SCIM
Sign in through your identity provider with SAML 2.0 or OIDC, and provision people with SCIM.
Bring your own keys
Use your organisation’s own model provider keys at organisation or workspace level.
More on how Agent Serve handles access, data and audit on the security page.
Where do the dashboard numbers come from?
Dashboard panels and the Relay both read workspace Tables. A scheduled workflow can call Meta's Marketing API insights endpoint with the generic API block, using an access token stored as a workspace secret, and write one row per campaign per day. If your ad data already lands in a warehouse such as BigQuery or Snowflake, connect it as a data source instead, refreshed every 15 minutes or queried live.
Meta ads · last 30 days (illustrative)
Top campaigns by spend
| Campaign | Spend | ROAS | CPA | Status |
|---|---|---|---|---|
| Prospecting · Diwali edit | ₹6.1L | 2.4 | ₹690 | Watch |
| Retargeting · 7-day viewers | ₹3.8L | 4.1 | ₹380 | On target |
| Advantage+ · bestsellers | ₹3.2L | 2.9 | ₹560 | On target |
| Prospecting · new kurtas | ₹2.6L | 1.6 | ₹940 | Over CPA |
Add a monitor on CPA. It re-checks as often as every five minutes and alerts by email, in-app or Slack. Remember that Meta's reported conversions change for a few days as they are attributed, so judge yesterday with care.
Where should you start?
Connect the server, spend a week asking Chat the questions you already ask, then add the metrics workflow and the Relay. For pacing across Google Ads and Meta together, see budget pacing and anomaly alerts.
Questions teams ask
Is there a built-in Meta Ads block?
No. You connect Meta’s official ads server under Settings → Tool connections, and its tools become available in Chat and to any Relay whose allowlist includes the connection. Which tools the server offers is up to Meta and can change.
Can the Relay change budgets on its own?
No. Budget changes move money, so they wait in the Relay’s review queue for a person, even under Operate. The approved call runs once and is audited. If you set delegated limits per action, day or week, calls within them can run, and paper mode lets you simulate them first.
Can it post the daily review to Slack or WhatsApp?
Relays send email and report in their own chat with notifications. They do not post to Slack or WhatsApp themselves; a workflow the Relay runs can. Monitors on the dashboard can alert Slack directly.
What you need
- Access to your Meta ad accounts with the permissions your team already uses
- Meta’s ads server added under Settings → Tool connections and on the Relay’s allowlist
- Written targets: CPA, ROAS and daily budget limits per campaign type
- A Relay with a morning schedule, Assist autonomy and an internal-only recipient policy
- A scheduled workflow that fills a daily metrics table, and a dashboard for spend, ROAS and CPA
- One person who owns approvals for anything that spends money