AI media-buying agents: L1, L2, L3 autonomy explained (2026)
The full framework - what belongs at each level, how action types graduate, and why full autonomy fails compliance review.
ReadThe account can absorb more spend but the team cannot ship enough variants to feed it. Fatigue sets in on the winners, and the next batch is three days out because someone has to write, brief, and assemble it by hand.
A campaign starts bleeding at 2am. Nobody looks until the morning stand-up. By then you have paid for a full day of a spend pattern anyone would have killed if they had been watching.
Pulling numbers out of each platform, reconciling them against the affiliate postbacks, and rebuilding the same sheet every morning is hours a week of a senior person doing assembly work.
Tools that promise to run the account for you make decisions you cannot reconstruct afterwards. When spend goes somewhere strange, there is no trace of why - and in a regulated vertical that is not a risk you can carry.
Variant generation from your winning angles, passed through a checklist gate before it can reach a human queue - banned claims, required disclaimers, regional restrictions. Output is a draft for review, never a direct publish.
Statistical monitoring on cost per action, conversion rate, and spend velocity per campaign, against that campaign's own baseline rather than a global threshold. It fires an alert with the numbers attached, not a vague warning.
A daily proposal that says which campaigns should move budget and why, with the evidence. In L2 configuration a human approves it in one click; in L3 it executes inside pre-agreed bounds and logs every move.
One pipeline pulling from each ad platform and your affiliate postbacks, reconciled into a single table. The morning sheet builds itself before anyone logs in.
Generated variants tied back to the performance data, so the next round of creative is briefed from what actually converted rather than from what the team remembers converting.
Every proposal, every approval, every automated execution written to a log with inputs and reasoning. This is what makes the system defensible in a compliance review and debuggable when a decision looks wrong.
We look at how spend is currently managed, where the manual hours actually go, and whether the performance data is clean enough to drive automated decisions. Two to three weeks. If the tracking is broken, fixing that comes first and we will say so.
First deployment is advisory only - the agent proposes, humans decide, nothing executes. Once the proposals have been right often enough for the team to trust them, we move approved action types to one-click approval.
Only specific, low-blast-radius action types graduate to autonomous execution, inside hard bounds you set, with an audit log and a kill switch. Most accounts should keep budget decisions above a threshold at L2 permanently, and we will tell you which.
Thirty minutes on the account. We map where the manual hours go and whether your tracking is clean enough to automate against. If it is not, that is the first project and we will say so.
Book a 30-min call