---
title: "Your AppLovin Asset Rows Add Up to 162% of Your Spend"
description: "AppLovin's asset report and creative-set report disagree on the same creative set's spend. We measured the gap on 579,887 creative-set-days."
canonical: "https://lemon-ai.com/resources/applovin-asset-report-reconciliation"
markdown_url: "https://lemon-ai.com/resources/applovin-asset-report-reconciliation.md"
language: "en"
image: "https://lemon-ai.com/og/resource-applovin-asset-report-reconciliation.png"
image_alt: "Ratio of AppLovin asset-report spend to creative-set-report spend, grouped by how many assets delivered that day, against the parity line."
date_published: "2026-09-08"
date_modified: "2026-09-08"
authors: ["Gregory Potemkin"]
schema_types: ["Article","BreadcrumbList","Organization","Person","WebApplication","WebPage","WebSite"]
---

# Your AppLovin Asset Rows Add Up to 162% of Your Spend

[LEMON AI](https://lemon-ai.com/)/RESOURCES

AppLovin reporting evidence

AppLovin's asset report and creative-set report disagree on the same creative set's spend. We measured the gap on 579,887 creative-set-days.

AppLovin reporting evidence

AppLovin's asset report and creative-set report disagree on the same creative set's spend. We measured the gap on 579,887 creative-set-days.

**AppLovin publishes asset-level performance through one API and creative-set performance through another. We matched them on the same account, day, campaign and creative set across 6 advertiser accounts, 18,466 creative sets, 579,887 creative-set-days and $17.4 million of creative-set-reported spend, from June 1 to August 9, 2026\. The asset rows carry 1.62 times the spend and 1.65 times the impressions, and 0.45 times the clicks. Both numbers in every comparison are AppLovin's own.**

Neither report is wrong. They answer different questions, and only one of them is a partition of your budget.

[ ![Ratio of summed AppLovin asset-report spend to the same creative set's reported spend, grouped by how many assets actually delivered that day, across the 570,978 creative-set-days carrying spend in both reports. With one asset delivering, 208,445 creative-set-days return a ratio of 0.99. With two, 149,793 days return 1.77. With three, 1.54. With four, 1.47. With five, 1.48. With six or more, 106,156 days return 1.65. The parity line sits at 1.00.](https://lemon-ai.com/images/resources/applovin-asset-report-reconciliation.svg) ](https://lemon-ai.com/images/resources/applovin-asset-report-reconciliation.svg)

When one asset delivers, the two reports agree. Every part of the gap arrives with the second asset.

## AppLovin tells you to judge assets on spend

The guidance is specific and, read literally, correct. AppLovin's campaign analysis page says [“Asset reporting is available in the Media Library and includes impressions, clicks, CTR, and spend for each video, image, and HTML file”](https://applovin.com/en/resources/analyzing-campaigns), that [“Spend is the most useful signal at the asset level”](https://applovin.com/en/resources/analyzing-campaigns), and that [“Revenue, ROAS, and CPP are not available at the asset level. Those metrics are reported at the creative set level.”](https://applovin.com/en/resources/analyzing-campaigns) Verified September 8, 2026.

The [Asset Reporting API](https://support.applovin.com/en/growth/promoting-your-apps/api/asset-reporting-api) returns `asset_id`, `asset_name`, `asset_url`, `campaign`, `campaign_id`, `campaign_package_name`, `clicks`, `cost`, `creative_set`, `creative_set_id`, `ctr` and `impressions`. There is no revenue column, and there is no statement anywhere in that documentation about whether those asset metrics sum to the creative set they belong to. Verified September 8, 2026.

So a team that follows the advice ends up holding two exports and joining them. Spend comes from the asset endpoint because that is the only place it exists per asset. Revenue comes from the [advertiser Reporting API](https://support.applovin.com/en/growth/promoting-your-apps/api/reporting-api) because that is the only place it exists at all. The join is the normal thing to do. It is also the moment the arithmetic stops meaning what it looks like it means.

## What we compared

For every account, day, campaign and creative set, we summed the asset report's assets and compared the result with the creative-set report's own row for that same key.

Campaign is part of the join key on purpose. AppLovin notes that a single creative set can serve more than one campaign at a time, which is the obvious innocent explanation for a reconciliation gap. Joining inside the campaign removes it. Whatever remains is not creative sets being shared.

Coverage is not the explanation either. Creative-set-days that carry spend and have no asset rows at all account for under 0.03% of spend in every one of the six accounts.

| Column      | Asset report divided by creative-set report |
| ----------- | ------------------------------------------- |
| Cost        | 1.617                                       |
| Impressions | 1.649                                       |
| Clicks      | 0.447                                       |

## The rows record participation, not a partition

Split the same comparison by how many assets actually delivered on that creative-set-day and the mechanism is unambiguous.

| Assets delivering | Creative-set-days | Cost  | Impressions | Clicks |
| ----------------- | ----------------- | ----- | ----------- | ------ |
| 1                 | 208,445           | 0.991 | 1.016       | 0.726  |
| 2                 | 149,793           | 1.771 | 1.821       | 0.461  |
| 3                 | 43,785            | 1.542 | 1.636       | 0.582  |
| 4                 | 35,644            | 1.474 | 1.449       | 0.531  |
| 5                 | 27,155            | 1.478 | 1.446       | 0.503  |
| 6 or more         | 106,156           | 1.646 | 1.623       | 0.351  |

On the 208,445 creative-set-days where exactly one asset delivered, the two reports agree on spend to within 0.9% and on impressions to within 1.6%. Add a second asset and the ratio jumps to 1.77.

That is what a participation record looks like. An AppLovin ad can show more than one asset, and the pattern here is what you would see if every asset that took part in an impression were credited with that impression and the money behind it. AppLovin does not document the behaviour either way, so that is our reading of the numbers rather than a stated rule. Row by row the asset report is telling the truth about what each asset was involved in. It is only when you add the rows together that you are counting the same impression once per asset that appeared in it.

A partition would sum to the whole. This sums to more than the whole, by an amount set by how many assets your creative sets run.

This split is also the control on our own arithmetic. If we had made a data-handling mistake in preparing either export, single-asset creative sets would be distorted in exactly the same way as the rest. They are not. They land on parity.

## The price per impression survives the crossing

Cost and impressions inflate together, which is the useful half of the news. Taking the week of July 1, 2026 and computing cost per thousand impressions inside each report separately:

| Creative-set report CPM | Asset report CPM |
| ----------------------- | ---------------- |
| $18.80                  | $18.82           |
| $26.02                  | $27.10           |
| $34.16                  | $35.08           |
| $8.80                   | $8.55            |
| $30.71                  | $30.25           |
| $14.42                  | $14.79           |

Each row is one account. The duplication replicates whole impressions at the price they were bought at, so a rate computed from two columns of the asset report at the same grain is intact. A total, a share, or a ratio that crosses into the other report is not.

## The click column does not follow the pattern

Every other finding here has a mechanism. This one does not.

Clicks are short by more than half overall, at 0.447\. Unlike cost and impressions, they are already short when a single asset delivers, at 0.726, and they do not recover at any asset count. Across the six accounts the click ratio runs from 0.039 to 1.013, a spread far wider than anything cost or impressions do.

We are reporting this and not explaining it. AppLovin's documentation does not describe the relationship between the two endpoints' click columns, we have not found a public account of it, and we are not going to invent one. Two practical consequences stand regardless of the cause:

- Do not compute a click-through rate on one report and compare it with a click-through rate from the other. They are not the same measurement.
- Treat any asset-level metric with clicks in it as unreconciled until you have checked it on your own account.

One caution about reading click rates on this inventory at all. In these accounts the creative-set report's own clicks divided by its own impressions comes out between 78% and 90% on the app accounts. Whatever AppLovin is counting in that column on Axon placements, it does not behave like a classic click-through rate, so we are not publishing either report's CTR as one.

## The gap holds still

This is a structural property of the reporting, not a bad month.

| Month       | Creative-set-days | Cost  | Impressions | Clicks |
| ----------- | ----------------- | ----- | ----------- | ------ |
| June 2026   | 157,041           | 1.643 | 1.659       | 0.499  |
| July 2026   | 324,484           | 1.619 | 1.649       | 0.435  |
| August 2026 | 98,362            | 1.567 | 1.634       | 0.415  |

Per account the spend ratio runs 1.456, 1.584, 1.719, 1.769, 1.893 and 1.999\. Every account is above parity, and the spread between them is roughly the spread in how many assets their creative sets carry.

An independent single-day check we ran on one account on July 21, 2026, before this panel existed, returned +20.2% cost, +23.6% impressions and -88.9% clicks against the advertiser report. Different day, different method, same three directions.

## Only a third of creative sets sum to their own spend

The pooled 1.62 is not a correction factor. Per creative-set-day the ratio has a tenth percentile of 0.927, a median of 1.097 and a ninetieth percentile of 2.000.

Of 570,978 creative-set-days with spend in both reports, 35.0% have asset rows that sum to within 5% of that creative set's own spend, 27.2% to within 2%, and 35.7% overstate it by more than half again. You cannot divide the gap out, because for any given creative set you do not know which of those three groups you are in without doing this comparison.

## If you run this yourself, deduplicate first

This one is worth the paragraph, because it nearly produced the opposite article.

Both AppLovin endpoints restate history, so any sane ingestion re-fetches a rolling window and stores several versions of the same key. In our warehouse on July 15, 2026, the creative-set table held 1,202,723 rows for 545,417 distinct keys while the asset table held 60,358 rows for 60,358 keys. Duplication on one side only. Summing those tables without collapsing each key to its latest version returns a ratio of 0.87, which reads as the asset report being a third short, and every conclusion drawn from it would have been backwards.

If you are reproducing this on your own exports, collapse to one row per key per day on both sides before you add anything up, and check that the single-asset creative sets land on parity. If they do not, the problem is in your pipeline rather than in AppLovin's.

## What you can and cannot compute

| You want to know                                 | Safe                                                              | Not safe                                                               |
| ------------------------------------------------ | ----------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Which asset in this creative set got more budget | Compare asset rows against each other inside the one creative set | Reading the number as dollars that partition the set                   |
| What this asset cost per thousand impressions    | Cost and impressions from the asset report at asset grain         | Any CPM that mixes one report's numerator with the other's denominator |
| This asset's share of campaign or account spend  | Nothing here supports it                                          | Asset cost divided by summed asset cost, or by campaign spend          |
| Total spend for the period                       | The creative-set or campaign report                               | Summing the asset report                                               |
| Asset-level ROAS                                 | Nothing in AppLovin's asset report supports it directly           | Creative-set revenue over asset cost, presented as a rate              |
| Whether clicks tell you anything at asset grain  | Nothing, until you have checked your own account                  | Any cross-report click-through rate                                    |

The row that matters most is the last two. AppLovin's own advice already points you at the creative set for revenue and ROAS, and this measurement is the arithmetic reason why: the denominator you would reach for lives on a different basis from the numerator.

That does not make asset-level outcomes impossible, but it does make them a construction rather than a lookup, and a construction has to declare itself. If you are building one, [the five checks for auditing an asset-level creative ROAS](https://lemon-ai.com/resources/asset-level-creative-roas) cover what to establish before it decides a budget. And before you conclude that pooling assets into creative sets is the way out, [we tested whether the creative-set revenue ranking is more stable than the asset one, and it is not](https://lemon-ai.com/resources/concept-level-creative-analysis).

## What this does not show

- It does not show that AppLovin is reporting incorrectly. Every row we compared is internally consistent, and the asset report does not claim to be additive.
- It is six advertiser accounts, weighted heavily toward one of them, over ten weeks. The direction is the same in all six and in all three months, but your ratio is your own and depends on how many assets your creative sets run.
- It says nothing about revenue. The asset endpoint has no revenue column, so there was nothing to compare.
- It does not explain the click column.
- It is a measurement of two reports, not of delivery. It cannot tell you which asset a viewer actually watched.

## Where Lemon fits

You can run this yourself. It is two AppLovin exports, a join on account, day, campaign and creative set, and a deduplication step. If your team can schedule both reports, the whole check is an afternoon.

What Lemon does is stop the two reports being silently mixed in the first place. [Creative Analytics](https://lemon-ai.com/creative-analytics) keeps AppLovin's asset-reported figures and its creative-set-reported figures on separate provenance, recomputes ratios from aligned components instead of averaging rows, and marks reconstructed values apart from network-reported ones so a column that came from a construction is labelled as one. [The methodology page](https://lemon-ai.com/methodology) sets out how that separation is defined and where it stops.

If you take one thing from this into your next reporting review, make it a single query. Sum your AppLovin asset export for a month, and compare it with what the platform says you spent. The distance between those two numbers is how much of your creative reporting has been standing on an addition that was never available. For the accounts here, it was 62%.

## Primary sources

- [AppLovin: Asset Reporting API](https://support.applovin.com/en/growth/promoting-your-apps/api/asset-reporting-api)
- [AppLovin: Reporting API](https://support.applovin.com/en/growth/promoting-your-apps/api/reporting-api)
- [AppLovin: Analyzing campaign performance](https://applovin.com/en/resources/analyzing-campaigns)
- [AppLovin: How to create creative sets](https://support.applovin.com/en/growth/promoting-your-apps/welcome-to-applovin/how-to-create-creative-sets)

On this page

- [AppLovin tells you to judge assets on spend](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#applovin-tells-you-to-judge-assets-on-spend)
- [What we compared](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#what-we-compared)
- [The rows record participation, not a partition](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#the-rows-record-participation-not-a-partition)
- [The price per impression survives the crossing](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#the-price-per-impression-survives-the-crossing)
- [The click column does not follow the pattern](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#the-click-column-does-not-follow-the-pattern)
- [The gap holds still](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#the-gap-holds-still)
- [Only a third of creative sets sum to their own spend](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#only-a-third-of-creative-sets-sum-to-their-own-spend)
- [If you run this yourself, deduplicate first](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#if-you-run-this-yourself-deduplicate-first)
- [What you can and cannot compute](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#what-you-can-and-cannot-compute)
- [What this does not show](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#what-this-does-not-show)
- [Where Lemon fits](https://lemon-ai.com/resources/applovin-asset-report-reconciliation#where-lemon-fits)

---

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 September 8, 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-asset-report-reconciliation#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":"Your AppLovin Asset Rows Add Up to 162% of Your Spend","item":"https://lemon-ai.com/resources/applovin-asset-report-reconciliation"}]},{"@id":"https://lemon-ai.com/resources/applovin-asset-report-reconciliation#webpage","@type":"WebPage","url":"https://lemon-ai.com/resources/applovin-asset-report-reconciliation","name":"Your AppLovin Asset Rows Add Up to 162% of Your Spend","description":"AppLovin's asset report and creative-set report disagree on the same creative set's spend. We measured the gap on 579,887 creative-set-days.","isPartOf":{"@id":"https://lemon-ai.com/#website"},"publisher":{"@id":"https://lemon-ai.com/#organization"},"inLanguage":"en","datePublished":"2026-09-08","dateModified":"2026-09-08","about":{"@id":"https://lemon-ai.com/#software"},"breadcrumb":{"@id":"https://lemon-ai.com/resources/applovin-asset-report-reconciliation#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-asset-report-reconciliation#article","@type":"Article","headline":"Your AppLovin Asset Rows Add Up to 162% of Your Spend","description":"AppLovin's asset report and creative-set report disagree on the same creative set's spend. We measured the gap on 579,887 creative-set-days.","image":"https://lemon-ai.com/og/resource-applovin-asset-report-reconciliation.png","datePublished":"2026-09-08","dateModified":"2026-09-08","articleSection":"AppLovin reporting evidence","mainEntityOfPage":{"@id":"https://lemon-ai.com/resources/applovin-asset-report-reconciliation#webpage"},"author":{"@id":"https://lemon-ai.com/authors/gregory-potemkin#person"},"publisher":{"@id":"https://lemon-ai.com/#organization"},"inLanguage":"en"}]}
```