Meta Ads Automated Workflow

The challenge

Running paid media for OASIS212 solo meant campaign setup, creative assembly, and performance monitoring all competed for the same hours, with no dedicated ad ops support.

The approach

I built a system that governs its own risk. Campaigns deploy through code, not manual dashboard clicks, but every campaign launches into a paused state by design, so live spend requires a deliberate human decision, not a pipeline default. A separate audit layer continuously evaluates live performance against weighted platform benchmarks and proposes optimizations, but nothing writes back to the account without approval.

The execution

Built and orchestrated via Claude Code, integrated directly with the Meta Marketing API (v21.0).

1. 01Brand and creative layer: dedicated agents handle pre-launch production. A creative-strategist agent defines campaign concepts and messaging pillars, a copy-writer agent produces platform-compliant headlines, CTAs, and descriptions, a visual-designer agent builds image-generation prompts and organizes the resulting assets, and a format-adapter agent validates every asset against platform-specific dimension and spec requirements before it moves downstream
2. 02Deployment layer: takes the resulting creative, agent-generated or pulled from OASIS212’s existing photo and video library, then builds the campaign, ad set, ad creative, and ad in sequence through the Meta API, landing every object in a paused state by default
3. 03Safety by design: activation to live spend is a separate, manual, reviewed step, never automatic
4. 04Audit layer: six specialized agents, covering Meta pixel and creative health, Google conversion tracking and bidding, cross-platform budget allocation, creative fatigue, compliance, and tracking integrity, evaluate live campaigns against weighted, platform-specific checklists and produce a scored account health report
5. 05Write-back layer: approved optimizations, pausing underperformers, correcting optimization-goal mismatches, are applied to the live account through the same API integration, gated by manual sign-off at every step