Each of these agents handles one complete process in your media buying workflow. They can work independently or be chained together into automated workflows (covered in Part 7).
The Creative Agent
Generates ad copy, headline variations, and creative concepts in seconds — not hours.
The Creative Agent handles the most time-consuming part of media buying: coming up with ad variations. Instead of spending hours writing copy and brainstorming angles, you describe the product and get dozens of variations back.
Capabilities
- Generates primary text (ad body) in multiple creative angles
- Creates headline and description variations for A/B testing
- Adapts tone: cold prospecting vs warm retargeting vs win-back
- Suggests angles: pain points, benefits, social proof, urgency, FOMO, authority
- Describes permitted public creative patterns without inferring spend, performance, intent, or copying protected expression
- Formats for different placements: Feed, Stories, Reels
Use a versioned brand brief, approved claims library, product source data, and reviewed examples. Keep each client's data tenant-isolated; do not silently train on, memorize, or reuse client inputs. Every factual, comparative, scarcity, testimonial, and performance claim needs source evidence and human approval.
The Campaign Launcher
Creates complete campaigns on Meta — without touching Ads Manager.
The Campaign Launcher handles the full campaign creation process via the Meta Marketing API: choosing objectives, setting budgets, configuring targeting, creating ad sets, and linking creatives.
The 5 Campaign Commands
| Command | What It Does |
|---|---|
/create-campaign | Creates campaign with objective + budget (CBO or ABO) |
/setup-adset | Configures targeting, placement, optimization goal |
/create-ad | Creates ad creative and links to ad set |
/check-performance | Pulls metrics and flags anomalies |
/scale-campaign | Drafts a capped canary request; cannot authorize spend |
A prompt cannot guarantee safety. A tenant-scoped executor rejects ACTIVE creation, unapproved accounts, spend above the cap, stale or mismatched approvals, and duplicate requests. It hard-codes PAUSED, requires an idempotency key and exact signed change-set, logs the write, and stores rollback. Activation is a separate privileged approval.
The Budget Optimizer
Use evidence to draft account-specific budget proposals; data and model output do not authorize a spend change.
The Budget Optimizer can summarize reported ROAS alongside contribution margin, attribution and conversion lag, incrementality, sample size, objective, cash flow, and account history. It proposes a reversible canary; a human approves the exact diff and a service enforces the cap, stop condition, idempotency, and rollback.
Illustrative Display — Not Universal Policy
| ROAS | Category | Action |
|---|---|---|
| Above example target | Investigate capacity | Consider a capped canary |
| Near example target | Review | Check lag, margin, and sample size |
| Below example target | Investigate | Check causes and measurement |
| Below stop criterion | Propose hold | Human-approved, reversible action only |
Reported ROAS alone cannot establish profit or incremental lift. Calibrate criteria per account, inspect uncertainty and lag, and prefer small canaries over universal scale/pause rules.
The Performance Monitor
Catches problems BEFORE they drain your budget — not after.
The Performance Monitor can evaluate scheduled, account-calibrated checks and flag observations for investigation. Detection speed depends on data freshness, sample size, and conversion lag.
What It Watches
The Report Generator
Generate a tenant-isolated draft with sources, definitions, freshness, and uncertainty for human review.
The Report Generator may read only sources authorized for that tenant and report purpose. It must not join, compare, or reuse data across clients. Treat the output as a draft: a named reviewer checks access scope, metric definitions, attribution, claims, and recipients before export or send.
Report Types
The Scaling Engine
Ranks candidates and drafts controlled canary proposals; it does not scale or retire campaigns automatically.
The Scaling Engine evaluates candidates using account-specific readiness criteria and uncertainty. It can propose a PAUSED test or capped budget canary, but a tenant-scoped service requires an exact approval, enforces spend and idempotency limits, monitors stop conditions, and can roll back.
Scaling Strategies
| Strategy | How It Works | When to Use |
|---|---|---|
| Vertical | Propose an account-capped budget canary | Incrementality, margin, lag, and capacity pass |
| Horizontal | Draft a PAUSED audience test | Evidence supports a distinct hypothesis |
| Creative | Draft substantiated creative variants | Rights, claims, and eval criteria pass |
| Rotation | Propose a reversible rotation test | Account-specific fatigue evidence is corroborated |
The Winner Identification Loop
This is the most powerful pattern — a continuous cycle of finding, analyzing, replicating, and scaling winners:
A recurring evaluation can keep a queue of candidates, but each test and spend change needs evidence, an account-specific readiness gate, human approval, deterministic controls, observation, and rollback. Continuous automation does not guarantee momentum or performance.
Built by @itsmazinzaki — AVAMARTECH