Run Meta Ads from Codex

Claude Code is interactive — you sit at the terminal, brief it, watch it run. Codex is autonomous — you write a default_prompt once, the agent runs on a schedule. Use Claude Code when you want to drive a one-off Meta launch hands-on; use Codex when you want a daily fatigue check, weekly wasted-spend audit, or anomaly monitor running unattended. Many teams use both — Claude Code for ad-hoc work, Codex for the recurring beat.

Typical autonomous Meta agents use 2-5 tool calls per run. A daily 6am performance check (1 call), a weekly Monday wasted-spend audit (3-4 calls), and a 6-hour anomaly monitor (4 runs/day × 1 call) costs roughly 200-300 calls / month — Plus tier ($49/mo, 150 calls) handles a single brand, Pro ($99/mo, 600 calls) covers multiple brands or higher cadence.

Yes. Create separate config files in ~/.codex/agents/ — one per client or brand — and each agent uses switch_primary_account to scope itself to a specific Meta ad account. A common agency pattern: one agent per client running weekly audits, output written to clients/{client}/meta-audit-{date}.md, all running on the same cron without colliding.

Image, video, and carousel campaigns are fully supported. Lifetime budgets, end dates, placement controls, and Dynamic Creative Optimization (DCO) are all available. Stories, Reels, and Audience Network placements are controlled at the ad-set level.

Meta requires $5/day per ad set. Adspirer recommends $20+/day for meaningful test data and $30/day split across 2-3 ad sets to find winners faster.

No — and that's the point. Even when a Codex agent runs unattended, Adspirer enforces hard-coded safety rules: every create_meta_image_campaign / create_meta_video_campaign / create_meta_carousel_campaign call ships paused, budget changes via update_meta_campaign require user confirmation, and there is no delete tool. The agent analyzes, recommends, and prepares — you approve final spending decisions manually.

No. Adspirer does not generate creative assets. You provide a public URL to your image or video (Google Drive, Dropbox, S3, or any public link) and Adspirer validates that it meets Meta's requirements before launching the ad.

Meta requires a 6-step sequence: verify the connection → search targeting → choose campaign type (image/video/carousel) → discover existing assets → validate creatives → create campaign. Adspirer enforces this order — skipping a step would cause Meta's API to reject the campaign.

Use list_meta_lead_forms to see configured forms, then get_meta_lead_form_submissions to pull recent submissions. Adspirer doesn't push leads into your CRM directly — it returns the submission data so you can route it through Zapier, Make, or a custom integration.

Adspirer can pause campaigns when you explicitly ask it to, but it cannot delete existing campaigns or ad sets. New campaigns are always created paused so you can review before they go live.