--- title: "AppLovin Creative Testing When the Engine Allocates Budget" description: "AppLovin decides which creative spends your money, then reports twelve delivery columns and no outcomes. What a creative comparison can and cannot prove." canonical: "https://lemon-ai.com/resources/applovin-axon-creative-testing" markdown_url: "https://lemon-ai.com/resources/applovin-axon-creative-testing.md" language: "en" image: "https://lemon-ai.com/og/resource-applovin-axon-creative-testing.png" image_alt: "Assets ranked by spend beside the same assets ranked by return. The engine picks the spend; that is not a quality ranking." date_published: "2026-08-15" date_modified: "2026-09-15" authors: ["Gregory Potemkin"] schema_types: ["Article","BreadcrumbList","Organization","Person","WebApplication","WebPage","WebSite"] --- # AppLovin Creative Testing When the Engine Allocates Budget [LEMON AI](https://lemon-ai.com/)/RESOURCES AppLovin creative testing AppLovin decides which creative spends your money, then reports twelve delivery columns and no outcomes. What a creative comparison can and cannot prove. AppLovin creative testing AppLovin decides which creative spends your money, then reports twelve delivery columns and no outcomes. What a creative comparison can and cannot prove. **On AppLovin the engine decides how much each creative spends, so a spend ranking is an output of that decision and not a measurement of creative quality.** The asset report gives you twelve delivery columns and no outcome columns, which means AppLovin’s own data cannot tell you whether the asset it funded was the asset that earned. This page sets out what a creative comparison on AppLovin can legitimately prove, what it cannot, and the guards that keep a decision honest when you did not control the allocation. ## AXON is now AppLovin Ads If you are searching for AXON, you are searching for a name AppLovin has stopped using. The advertising platform was rebranded to AppLovin Ads on June 30, 2026, and the self-serve product opened to all advertisers rather than a referral programme. Verified on August 15, 2026: [AppLovin’s own advertiser page](https://www.applovin.com/en/consumer-brands) refers to AppLovin Ads throughout and describes the optimiser only as “AppLovin’s AI engine”. The documentation host `support.axon.ai` returns HTTP 301 to `support.applovin.com` on every path we tested. Nothing underneath changed. The engine still buys, still allocates, and still declines to explain itself. Practitioners will keep saying AXON for years, which is fine. Just do not expect current documentation to be filed under that word. ## What the engine reports about its own decisions Nothing. That is the whole finding, and it is worth being precise about it. As documented on August 15, 2026, AppLovin’s [Asset Reporting API](https://support.applovin.com/en/growth/promoting-your-apps/api/asset-reporting-api) exposes exactly these columns: `asset_id`, `asset_name`, `asset_url`, `campaign`, `campaign_id`, `campaign_package_name`, `clicks`, `cost`, `creative_set`, `creative_set_id`, `ctr`, `impressions` Two endpoints serve them, and they do not behave the same way: | Endpoint | Date handling | Ceiling | | --------------------- | ---------------------------------------------- | --------------------- | | /assetReport | Presets only: yesterday, last\_7d, last\_month | No custom range | | /assetAnalyticsReport | Custom range, YYYY-MM-DD | 45 day maximum window | Read the column list again for what is missing. No installs. No revenue. No ROAS, CPI, or CPA. No conversion of any kind at asset grain. And nothing about the engine. No exploration or exploitation state is documented, nor a learning-phase marker, a per-asset budget allocation, a reason code, or a confidence value. The system that moved your money publishes no field describing why it moved. That opacity is not accidental, and AppLovin’s leadership has been direct about it. Speaking to [AdExchanger in February 2024](https://www.adexchanger.com/ai/a-tiny-peek-inside-the-black-box-algorithm-driving-applovins-business/), chief executive Adam Foroughi said of the model, “We can’t see into a black-box algorithm.” The [campaign scaling guidance](https://support.applovin.com/en/growth/promoting-your-apps/track-and-optimize/scale-your-campaign) tells advertisers to upload and test new assets frequently and to diversify formats. It documents no learning period and no ramp timeline. So the instruction is to keep feeding creatives, and the reporting surface will not tell you which ones worked. ## Why this is not a test A creative test assumes you controlled the exposure. On AppLovin you did not. The engine chooses how much each asset spends, and it chooses continuously. That produces three confounds you cannot remove with the asset report alone. **Allocation is the treatment.** Assets the engine favours receive more spend, more impressions, and therefore more mature outcome data. When you compare them to assets it starved, you are comparing two different levels of statistical power alongside two different creatives. **Selection runs both ways.** The engine allocates on its own predicted outcome. An asset that looks strong early attracts budget, which produces the volume that makes it look strong in your report. Rank and cause are entangled from the first day. **The report stops at delivery.** Impressions, clicks, cost, and CTR describe what the engine did. Whether it was right is a question about installs and revenue, and those are not in the response. None of this means the engine is allocating badly. It means the asset report cannot answer the question you are asking it. ## What you can and cannot conclude | Question | Evidence it needs | In the asset report? | Do this instead | | ------------------------------------------------ | ---------------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Which asset did the engine back? | Cost by asset | Yes | Read it directly. This is the one thing the report answers cleanly. | | Which asset earned the most? | Revenue by asset | No | Reconstruct from your MMP or warehouse at asset grain | | Which asset earned most per dollar? | Revenue and spend, aligned | Partly | Recompute the ratio from aligned components; never average ROAS | | Is asset A better than asset B? | Comparable exposure | No | Treat as a ranking hypothesis, then confirm on matured cohorts | | Did this creative fatigue? | Rate series with volume floors | Delivery only | Run the [fatigue measurement protocol](https://lemon-ai.com/resources/creative-fatigue-measurement), then check whether the decline is [fatigue or the engine shifting delivery](https://lemon-ai.com/resources/creative-fatigue-analysis) | | Which creative choice inside the winners worked? | Tagged attributes, with a sample size counted in creatives | No | Run an attribute comparison with the sample counted in creatives and the number of comparisons corrected for | | Why did the engine choose it? | Allocation state | No | Not answerable. Stop trying to infer it | The last row is the one teams waste the most time on. There is no field, so every explanation of the engine’s behaviour is a story fitted after the fact. ## Guards that survive an allocated test Four rules keep a conclusion defensible when you did not control delivery. **Set a volume floor before reading, not after.** A ranking over assets that never got enough delivery is noise. Set a minimum spend and impression count per asset, and a minimum number of qualifying assets per app, before you read the table; tune both to the variance in your own account. The floor also depends on the column: [re-rank the same assets on the odd and even days of one fortnight and count how much of each top quarter reproduces](https://lemon-ai.com/resources/creative-ranking-split-half-test) before you trust it. A revenue ranking rests on far fewer events than an install ranking and needs correspondingly more volume before it holds. **Match observation windows.** Compare assets over the same calendar range. The 45 day ceiling on `/assetAnalyticsReport` means longer comparisons must be stitched from multiple pulls, and a stitched window is easy to misalign. **Gate on outcome maturity.** D7 ROAS is only readable once every cohort in the window has had seven days. Comparing a mature asset against one still accumulating manufactures a gap that closes on its own. Which horizon is even available depends on the network, and the [attribution window comparison](https://lemon-ai.com/resources/ad-network-attribution-windows) sets out what AppLovin anchors its outcomes to and when the figure stops moving. **Split the read by platform before you rank.** The Asset Reporting API has no platform dimension, and on iOS the outcome half of the comparison cannot resolve to a creative at all. [What Apple’s postbacks return, and what is left to decide on](https://lemon-ai.com/resources/ios-creative-level-measurement) covers which half of an iOS creative comparison still carries evidence. **Keep provenance visible.** Any outcome you attach to an AppLovin asset was reconstructed. Label it. The [asset-level creative ROAS audit](https://lemon-ai.com/resources/asset-level-creative-roas) covers the provenance, scope, maturity, and aggregation checks a number should pass before it changes a budget. ## Where this leaves the work Feed the engine variety, because it can only choose among what you give it. Then build the evidence layer it does not provide: join asset-grain delivery to attributed outcomes, keep an unallocated bucket for what will not match, and rank on reconstructed return rather than on spend. That work is the same whether you do it in a warehouse or in a product. Lemon AI’s [creative analytics](https://lemon-ai.com/creative-analytics) puts AppLovin’s reported delivery next to reconstructed installs, purchases, revenue, and ROAS for the same asset, with recovered values visually distinct from network-reported ones so the provenance stays legible. The [reconciliation rules and limitations](https://lemon-ai.com/methodology) are published in full. For how the AppLovin reporting surfaces fit together once you have decided what to measure, see [AppLovin creative reporting](https://lemon-ai.com/resources/applovin-creative-reporting). ## Primary sources - [AppLovin Asset Reporting API](https://support.applovin.com/en/growth/promoting-your-apps/api/asset-reporting-api) - [AppLovin: scale your campaign](https://support.applovin.com/en/growth/promoting-your-apps/track-and-optimize/scale-your-campaign) - [AppLovin Ads for consumer brands](https://www.applovin.com/en/consumer-brands) - [AdExchanger: a tiny peek inside the black-box algorithm driving AppLovin business](https://www.adexchanger.com/ai/a-tiny-peek-inside-the-black-box-algorithm-driving-applovins-business/) On this page - [AXON is now AppLovin Ads](https://lemon-ai.com/resources/applovin-axon-creative-testing#axon-is-now-applovin-ads) - [What the engine reports about its own decisions](https://lemon-ai.com/resources/applovin-axon-creative-testing#what-the-engine-reports-about-its-own-decisions) - [Why this is not a test](https://lemon-ai.com/resources/applovin-axon-creative-testing#why-this-is-not-a-test) - [What you can and cannot conclude](https://lemon-ai.com/resources/applovin-axon-creative-testing#what-you-can-and-cannot-conclude) - [Guards that survive an allocated test](https://lemon-ai.com/resources/applovin-axon-creative-testing#guards-that-survive-an-allocated-test) - [Where this leaves the work](https://lemon-ai.com/resources/applovin-axon-creative-testing#where-this-leaves-the-work) --- Related product - [Creative Analytics](https://lemon-ai.com/creative-analytics) - [Attribute Analysis](https://lemon-ai.com/attribute-analysis) [Written by**Gregory Potemkin**Founder & CEO](https://lemon-ai.com/authors/gregory-potemkin)Published August 15, 2026 NEXT STEP ## Bring us the question your dashboards can't answer. See your creatives and cohorts in one place, with the answers your ad networks leave out. [Book a demo ](https://calendly.com/robert-lemon-ai) ## Structured data ```json {"@context":"https://schema.org","@graph":[{"@id":"https://lemon-ai.com/#organization","@type":"Organization","name":"Lemon AI","url":"https://lemon-ai.com/","logo":{"@type":"ImageObject","@id":"https://lemon-ai.com/#logo","url":"https://lemon-ai.com/brand/lemon-ai-mark-512.png","contentUrl":"https://lemon-ai.com/brand/lemon-ai-mark-512.png","width":512,"height":512,"caption":"Lemon AI"},"email":"hi@lemon-ai.com","sameAs":["https://cy.linkedin.com/company/lemon-ai","https://x.com/lemon_ai_adtech","https://www.g2.com/products/lemon-ai/reviews"]},{"@id":"https://lemon-ai.com/#website","@type":"WebSite","name":"Lemon AI","url":"https://lemon-ai.com/","publisher":{"@id":"https://lemon-ai.com/#organization"},"inLanguage":"en"},{"@id":"https://lemon-ai.com/resources/applovin-axon-creative-testing#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Lemon AI","item":"https://lemon-ai.com/"},{"@type":"ListItem","position":2,"name":"Resources","item":"https://lemon-ai.com/resources"},{"@type":"ListItem","position":3,"name":"AppLovin Creative Testing When the Engine Allocates Budget","item":"https://lemon-ai.com/resources/applovin-axon-creative-testing"}]},{"@id":"https://lemon-ai.com/resources/applovin-axon-creative-testing#webpage","@type":"WebPage","url":"https://lemon-ai.com/resources/applovin-axon-creative-testing","name":"AppLovin Creative Testing When the Engine Allocates Budget","description":"AppLovin decides which creative spends your money, then reports twelve delivery columns and no outcomes. What a creative comparison can and cannot prove.","isPartOf":{"@id":"https://lemon-ai.com/#website"},"publisher":{"@id":"https://lemon-ai.com/#organization"},"inLanguage":"en","datePublished":"2026-08-15","dateModified":"2026-09-15","about":{"@id":"https://lemon-ai.com/#software"},"breadcrumb":{"@id":"https://lemon-ai.com/resources/applovin-axon-creative-testing#breadcrumb"}},{"@id":"https://lemon-ai.com/#software","@type":"WebApplication","name":"Lemon AI","url":"https://lemon-ai.com/","description":"Creative intelligence and cohort-revenue forecasting for mobile app and game user-acquisition teams.","applicationCategory":"BusinessApplication","operatingSystem":"Web","browserRequirements":"Requires a modern web browser","provider":{"@id":"https://lemon-ai.com/#organization"},"featureList":["Creative-level spend, installs, purchases, revenue, and ROAS","Creative attribute analysis","Evidence-led creative generation","Cohort revenue and ROAS forecasting through D365","Read-only reporting API and MCP access"],"offers":[{"@type":"Offer","name":"Creative Intelligence annual billing","price":"209","priceCurrency":"USD","url":"https://lemon-ai.com/#pricing","description":"Effective monthly price per app when billed annually.","availability":"https://schema.org/OnlineOnly"},{"@type":"Offer","name":"Cohort Prediction monthly subscription","price":"679","priceCurrency":"USD","url":"https://lemon-ai.com/#pricing","description":"Monthly price per app after a $1,399 one-time account setup.","availability":"https://schema.org/OnlineOnly"}]},{"@id":"https://lemon-ai.com/authors/gregory-potemkin#person","@type":"Person","name":"Gregory Potemkin","jobTitle":"Founder & CEO","url":"https://lemon-ai.com/authors/gregory-potemkin","image":"https://lemon-ai.com/images/join-us/gregory.webp","sameAs":["https://www.linkedin.com/in/gregory-potemkin/"],"worksFor":{"@id":"https://lemon-ai.com/#organization"}},{"@id":"https://lemon-ai.com/resources/applovin-axon-creative-testing#article","@type":"Article","headline":"AppLovin Creative Testing When the Engine Allocates Budget","description":"AppLovin decides which creative spends your money, then reports twelve delivery columns and no outcomes. What a creative comparison can and cannot prove.","image":"https://lemon-ai.com/og/resource-applovin-axon-creative-testing.png","datePublished":"2026-08-15","dateModified":"2026-09-15","articleSection":"AppLovin creative testing","mainEntityOfPage":{"@id":"https://lemon-ai.com/resources/applovin-axon-creative-testing#webpage"},"author":{"@id":"https://lemon-ai.com/authors/gregory-potemkin#person"},"publisher":{"@id":"https://lemon-ai.com/#organization"},"inLanguage":"en"}]} ```