An AI agent for AppLovin Axon: web and app campaigns, read and run with approvals
AppLovin's Axon ads now promote websites as well as apps, which puts AppLovin next to Meta, Google and TikTok in many media plans. An AI agent connected with AppLovin's keys reads the Axon reports for both, MAX mediation revenue for publishers, and — with the Campaign Management key — creates and edits campaigns, creative sets and assets. This post covers what it reads, what it changes, what always waits for a person, and goals to start with.
Why AppLovin needs its own playbook
AppLovin is not a sign-in platform like Google Ads or Meta. It works with keys from the Keys page of the AppLovin dashboard: a Report Key for reporting, an Event Key for the Axon Pixel, and a Campaign Management key for changes. Its reports are three different APIs — Axon ads promoting websites, Axon ads promoting apps, and MAX mediation revenue — each with its own columns.
Its campaign API also behaves differently from the platforms most teams know. It has no delete or archive, it ignores the status you send when you create something, and it blocks an account's API for 24 hours after 100 error answers in 5 minutes. An agent that treats AppLovin like any other ad platform will either report the wrong numbers or, worse, lock the account for a day.
What the agent reads
| Report | Who it is for | Typical columns |
|---|---|---|
| Axon ads for websites | E-commerce and lead-generation advertisers | Spend, impressions, clicks, CTR, CPC, sales, checkout revenue and ROAS over 0–28 day windows, new-customer columns |
| Axon ads for apps | App marketers (AppDiscovery) | Spend, installs, conversions, CPA, retention and ROAS windows by campaign, country and platform |
| MAX revenue | App publishers using MAX mediation | Estimated revenue, eCPM, impressions, requests and fill rate by app, ad format, network and ad unit |
What it changes, with the Campaign Management key
- Campaigns: web or app campaigns created from a brief, then paused right after creation and read back; names, end dates, targeting, daily budgets and goal values edited; campaigns paused or started.
- Creative sets: built from uploaded assets, edited, cloned into another campaign, added to or taken out of campaigns.
- Assets: images, videos and HTML playables uploaded for AppLovin's review and added to creative sets. Spied third-party ads are refused as uploads.
- No deletes. AppLovin has none; the agent pauses instead.
What always waits for a person
Ordinary changes — a rename, new targeting, a paused creative set, a pause — follow the task's approval setting: they wait for your approval unless auto-approve is on. Anything that can start or change spend waits for a person on every lane: in the app, on a schedule, under auto-approve and from an MCP client.
- A new campaign (it sets a daily budget and a goal).
- A budget or goal-value change.
- Setting a campaign or creative set LIVE.
- Adding creative sets to campaigns, creating a creative set into a campaign, or cloning one that is not paused.
Respecting AppLovin's error limit
The 24-hour block after 100 error answers in 5 minutes is the rule that shapes everything else. The agent checks every request against AppLovin's documented rules before sending it — dates, required fields, the columns each report takes, which fields can change after creation — so a mistake is refused locally instead of counted by AppLovin. A refused request is never retried, and sending stops after 30 errors in 5 minutes, well before AppLovin's limit.
Goals to start with
| Goal | What the agent does |
|---|---|
| "Which AppLovin web campaigns had the best 7-day ROAS last week, and which spent without sales?" | Reads the web report by campaign for the 7 UTC days ending yesterday and ranks by roas_7d and spend with no sales. |
| "Compare AppLovin, Meta and TikTok cost per purchase last month." | Reads each platform in its own report; AppLovin's numbers are UTC days in US dollars, so the comparison names each platform's window and currency. |
| "Which countries are too expensive on my app campaigns?" | Reads installs and CPA by country and platform, and proposes a targeting or budget change for your approval. |
| "Which MAX networks lost eCPM this week?" | Reads MAX revenue by network and ad unit for two weeks and compares them. |
| "Set the Axon Pixel up on my site." | Gives the Google Tag Manager steps with your saved Event Key, and AppLovin's warnings. |
Setting it up
- 1In the AppLovin dashboard open your account menu → Keys and copy the Report Key (and the Event Key).
- 2On Integrations, press Connect with keys on the AppLovin card, name the account and press Check and save.
- 3For changes, add the Campaign Management key and the numeric account id with Add campaign management.
- 4Pick the account in the context picker and write a goal — or call the same tools from Claude, Codex or Cursor over MCP.
Frequently asked questions
- Can an AI agent manage AppLovin Axon campaigns?
- Yes, with the Campaign Management key: it creates and edits campaigns, creative sets and assets. New objects are paused right after creation, and a new campaign, a budget or goal change and going live wait for a person.
- Does the agent read AppLovin web campaigns as well as app campaigns?
- Yes. Axon ads for websites and Axon ads for apps are separate reports, and the agent reads either or both.
- Can the agent delete AppLovin campaigns?
- No. AppLovin's Campaign Management API has no delete or archive; the agent pauses instead.