t1k:marketing:analytics:applovin-exports
| Field | Value |
|---|---|
| Module | analytics |
| Version | 1.21.13 |
| Effort | medium |
| Tools | — |
Keywords: ad format mix, analyze them for me, analyze this, applovin campaign export, arpdau, axon ua report, campaign name taxonomy, clone decision, cohort maturity, compare competitor games, competitive intelligence ad export, competitor ua analysis, competitor ua data, competitor ua teardown, creative concept ranking, d28 retention filtering, d28 total roas, d7 retention filtering, dau dedup, days to peak spend, drop-a-csv, follow decision framework, follow or not, imp/dau, is this game worth copying, matured roas, max activity report, max mediation export, retention shape vs level, roas goal, scaling velocity, should we build something like this competitor, should we follow this game, size/type, strip the iap test, user_activity_mediation_report, which game has more potential
How to invoke
Section titled “How to invoke”/t1k:marketing:analytics:applovin-exportsAXON UA & MAX Mediation Export Analysis
Section titled “AXON UA & MAX Mediation Export Analysis”Read a manually-exported AppLovin AXON UA campaign CSV or MAX mediation/activity CSV correctly — for your own apps or for a competitor’s. Both exports look like flat rows you could average straight down a column. Doing that is silently wrong: cohort columns report partial values until they mature, DAU repeats across format rows, and the interesting signal (geo, creative concept, optimization window) lives only in free-text campaign names.
Executed by
Section titled “Executed by”Only the mechanical column math (§1–2, §5) is cheap-tier work: recompute, the §2 maturity filter, DAU dedupe and token decoding are specified before the run. Creative ranking, scaling classification and follow/clone calls (§3–4, §6) read the result and stay on a reasoning tier (routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”):
| Step | Agent |
|---|---|
| Recompute a grouped ratio (CPI/CTR/IR/CPM, ARPDAU) from Σnumerator/Σdenominator per the stated formula | t1k-metrics-reporter |
Apply the §2 maturity filter (age >= K + 1) and report matured-spend coverage per metric | t1k-metrics-reporter |
Dedupe DAU/DAV on (package, platform, day) before a DAU-denominated figure | t1k-metrics-reporter |
| Decode campaign-name tokens against Goal type / Day target / Bidding strategy (§3) | t1k-list-classifier — the token-classification rubric is stated in §3 |
| Rank creative concepts, classify scaling status, or make a follow/clone call (§3–4, §6) | stays on a reasoning tier — these read the computed numbers and form a judgment |
The maturity, dedup and ratio math is where the correctness rules live. Delegate that arithmetic; keep the interpretive axes (§6) on a reasoning tier. A cheap agent should never decide whether a game is worth cloning.
When to Use
Section titled “When to Use”- Analyzing a dropped AXON UA campaign CSV (own app or competitor) — spend, installs, CPI, ROAS, retention
- Analyzing a dropped MAX mediation/activity CSV — DAU, ARPDAU, eCPM, fill rate per ad format
- Decoding what a competitor’s campaign names encode (geo / creative concept / optimization window) and ranking creative concepts by performance
- Classifying a campaign’s scaling status (ramping / live / throttling / ended) from its daily spend curve
- Building competitive-intel or portfolio recommendations that combine the UA side (what they buy) with the monetization side (what they earn)
- Deciding whether to follow/clone a competitor game from its exports — “which of these games has more potential”, “should we build something like this”, “is this worth copying”
Not this skill: live API pulls across networks (→ t1k-marketing-analytics-crawldata) or
MAX SDK/mediation setup and the Reporting/Management APIs (→
t1k-marketing-monetization-applovin-max) — see Related skills below.
Recognizing this data with little or no prose
Section titled “Recognizing this data with little or no prose”In practice a CSV shows up as a bare path or “analyze this for me” with no other context — match on the file, not the sentence:
| Signal | AXON UA export | MAX mediation/activity export |
|---|---|---|
| Default export filename | report_<timestamp>.csv (e.g. report_2026-08-11_11_11_14_7714.csv) | user_activity_mediation_report_<timestamp>.csv |
| Distinctive header columns | Campaign name, Spend, ROAS goal, Goal type, Day target, D7 retention, D28 total ROAS | Size/Type, DAU, DAV, ARPDAU, Fill Rate, Display Rate, Imp/dau |
If the filename alone is ambiguous (AXON’s report_*.csv is generic), open the file and check
the header row against the column list above — either table (§1 / §5) confirms which export
you’re holding within the first line.
1. AXON UA CSV column reference
Section titled “1. AXON UA CSV column reference”One row per campaign per day. Core columns: Date, Package name, Account Name,
Campaign name, Platform, Spend, Installs, Impressions, Clicks, CPI, CPM, CTR,
IR, Goal type, Day target, Bidding strategy, ROAS goal. Then, per K in
{1,3,7,14,28}: DK retention; per K in {0,1,3,7,14,28,60,90,180,1Y}: DK IAA ROAS,
DK IAP ROAS, DK total ROAS. Full 68-column reference:
references/axon-ua-columns.md.
Recompute a grouped ratio from Σnumerator / Σdenominator, never average the per-row value. Averaging overstates CPI by about 25% and CPM by about 26% on the corpus; the IR tolerance note and the evidence are in references/axon-ua-columns.md.
Recompute: CPI = Σspend / Σinstalls, CTR = Σclicks / Σimpressions, IR = Σinstalls / Σimpressions, CPM = Σspend / Σimpressions × 1000. The MAX mediation export has the identical
trap for ARPDAU — see §5.
2. Cohort maturity filtering — the correctness rule
Section titled “2. Cohort maturity filtering — the correctness rule”DK retention and DK ROAS are cohort metrics: a row for installs acquired on day D
only carries a trustworthy DK value once the cohort has actually aged that long. The
threshold is age >= K + 1, not age >= K — a cohort acquired on D is measured on
D+K, and at exactly age == K that measurement day is still in progress, so the export
reports a fraction of the true value. The bias is always downward.
Retention zero-fills and ROAS carries a running cumulative-to-date, so an immature DK cell is a live lower bound, never a completed read. Evidence: references/cohort-maturity-methodology.md.
Filter to matured rows PER METRIC, independently, then spend-weight. D7 and D28 have different matured row sets from the same export — don’t reuse one filter for both.
matured(row, k) := (export_max_date - row.date).days >= k + 1d28_roas = spend_weighted_avg(row.d28_total_roas for row in rows if matured(row, 28))Always report matured-spend coverage next to any DK claim. State the coverage percentage every time you state a DK figure past D7 — recently-launched apps skew this hardest, since the covered slice is also the earliest and best-performing.
Below ~5% of matured spend, emit n/a (coverage X%) instead of a number. A coverage
footnote is not enough — readers compare adjacent table cells and skip footnotes.
Coverage % is necessary but not sufficient: a segment with ≥10% of spend and <10% of its own spend matured makes the figure segment-biased (hard rule below).
Exception: a DK/D1 ratio or DK→DJ accrual multiple needs ONE row-set, filtered on the longer horizon (hard rule below).
Detection when reading a table, and the band is genre- and mix-specific (NEVER transplant it): compare the implied multiple against the per-cohort-week distribution measured on rows matured for the longer horizon; an outlier is a population-mismatch suspect, not a discovery. Full procedure in references/cohort-maturity-methodology.md.
The export’s final day is a partial day. It was pulled mid-day, so the last calendar date always under-reports spend. Exclude it from status classification, peak-spend detection, and trailing-window comparisons — including it falsely reads every live campaign as “throttling” (see §4).
3. Campaign-name taxonomy decoding
Section titled “3. Campaign-name taxonomy decoding”Geo, creative concept and optimization window usually have no dedicated column; they live in Campaign name tokens. Decode by tokenizing on _ / - and confirming tokens against Goal type, Day target and Bidding strategy. Drop buyer-handle tokens present on every campaign. Rank concepts by spend, then matured spend-weighted ROAS, never by CTR. Cross-tab spend by both factors before any two-factor cut. Method, ranking detail and the worked example: references/campaign-taxonomy-worked-example.md.
4. Scaling-velocity methodology
Section titled “4. Scaling-velocity methodology”Classify a campaign from its daily spend series, relative to the export’s last complete day — never wall-clock “today” and never the partial final day (§2):
launch= first day with spend > 0.peak_spend,peak_date= max daily spend and the day it occurred.days_to_peak=(peak_date - launch).days + 1.status, evaluated against the last complete day’s spend vspeak_spend:- ended — no spend for 2+ consecutive days before the last complete day
- throttling — last complete day’s spend < 60% of peak
- live — otherwise (holding or still climbing)
A short days_to_peak (1–2 days) on a large budget is a burst test, not organic growth; flag it separately. Cadence reading: references/scaling-velocity-notes.md.
5. MAX mediation CSV column reference + traps
Section titled “5. MAX mediation CSV column reference + traps”One row per ad format per app-day (typically 7 formats × N days). Core columns: Day,
Package Name, Platform, Country, Size/Type (ad format), DAU, DAV, Requests,
Impressions, Clicks, Est. Revenue, eCPM, No Fills, Loads, Load Errors,
Fill Rate, Display Rate, Req/dau, Imp/dau. Full column reference + the four verified
derivation formulas: references/max-mediation-columns.md.
-
DAU/DAVrepeat the app-level total on every per-format row. Summing the column inflates DAU by roughly the number of formats reported (typically 7×). Deduplicate on(package, platform, day)before any DAU-denominated figure (ARPDAU, imp/DAU) — take the value once per app-day, never sum across format rows. -
Platformcarries trailing whitespace ("android ", not"android"). Strip every key before grouping or joining, or one platform silently becomes two. -
Recompute ARPDAU yourself:
Σ Est. Revenue / Σ deduplicated DAU. The providedARPDAUcolumn is per-format (format revenue / app DAU) and reads as a plausible per-app number if you don’t check — trust the recomputation, not the column. -
A zero row means “format not running,” not “zero performance.” Averaging an inactive format’s zero row into a per-format metric understates every active format. Omit inactive rows (all-zero impressions and revenue) and report the absence as a finding — which formats a competitor doesn’t run is itself signal.
-
Banner
imp/DAUin the hundreds is refresh, not an anomaly. Compare banner to banner, and use revenue per DAU (not eCPM) across formats. Evidence:references/max-mediation-columns.md. -
Requestsmay be filled-requests-only, not total demand — verify before relying on it. Re-derive theFill Rateidentity against your own export first; evidence inreferences/max-mediation-columns.md.
6. UA + monetization synthesis
Section titled “6. UA + monetization synthesis”Join the decoded UA side (§1–4: what a title buys, at what efficiency, with what creative/geo
mix) against the decoded monetization side (§5: what it earns per user, per format) to produce
recommendations — a target ROAS goal and CPI ceiling from the UA side’s payback curve, a
creative-concept starting point from the taxonomy ranking, an ad-format mix from the mediation
side’s revenue-per-DAU split. This is read/analysis-only — nothing here calls a live
ad-network API or mutates a campaign, bid, budget, or placement. See
rules/ad-network-mcp-write-safety.md.
Follow/clone decision — “should we build something like this?”
Section titled “Follow/clone decision — “should we build something like this?””Exports also answer the question they are pulled for: which competitor has more potential, and should this studio build something like it. Eight axes, each independently decisive enough to flip a recommendation: (1) retention SHAPE (D28/D1) beats retention LEVEL; (2) strip the IAP and recompute D28 from the IAA column against CPI; (3) matured-spend coverage is a confidence gate; (4) revenue-per-install required is set by CPI, so rank by profit contribution, never ROAS% alone; (5) observed payback beats projected payback; (6) category TAM evidence; (7) genre adjacency to the portfolio; (8) what to steal even from a rejected candidate.
Each axis is explained in depth in references/follow-decision-framework.md.
A follow decision from these exports alone is under-informed — always state which of these apply: single network only (AppLovin, not Meta/Google/TikTok), no organics (paid installs only, no k-factor), no geo dimension, no ARPPU, no monetization data unless a MAX export is also present, and long windows (D60+) unreadable on recently-launched apps. Cheapest gap-closer: re-pull in ~30 days once matured-spend coverage (§2) would be near-full.
Full worked example (real numbers), the eight axes in depth, the limits checklist, and the
cross-candidate comparison table shape:
references/follow-decision-framework.md.
Hard rules
Section titled “Hard rules”age >= K(notK + 1) silently understates every DK metric — always add the +1.- Averaging a DK column with immature rows still in it drags the number toward zero (retention zero-fill) or understates it (ROAS carries a running cumulative-to-date, not a stale forward-fill) — filter first, per metric, then spend-weight.
- An immature
DKcell is a valid lower bound, not noise — usable for bounding an in-flight cohort, just never averaged in as a completed read. - A
DK/D1ratio orDK→DJaccrual multiple is the one case where per-metric filtering is wrong — filter both metrics on the longer horizon’s matured set, or the ratio compares two different cohort populations. Then sanity-check the resulting multiple against the per-cohort- week distribution — an outlier is a population-mismatch suspect, not a discovery. - Below ~5% matured-spend coverage, print
n/a (coverage X%)rather than a number — a footnote does not survive contact with a reader comparing adjacent cells. - Coverage % is not sufficient: if a segment holding ≥10% of app spend has <10% of its own spend matured, the figure is segment-biased even at healthy headline coverage.
- A ROAS percentage without its spend is not comparable to another — rank tables by profit
contribution (
spend × (ROAS − 1)), never by ROAS% alone; treat a high ROAS at low spend as a hypothesis until it’s held up as CPI rose — and never carry a fixed pp-per-dollar decay coefficient between datasets, the relationship is non-linear even within one. - Coverage answers “can I trust this number”; spend-relevance and scale-durability answer “does this number matter, and will it hold” — clearing one does not mean the other clears too.
- Never average a per-row ratio column (
CPI,CTR,IR,CPM) — each is correct per row, but averaging overstates CPI/CPM by ~25% on this corpus. Recompute fromΣnumerator / Σdenominatorover the group;IR = installs/impressions, not installs/clicks despite the name. Same principle as the ARPDAU trap below (§5). ROAS goalis a target, never an observation;Goal type(IAA/IAP/Blended) +Day targettell you which of the three ROAS columns the campaign is actually optimizing toward — an IAA/D28 campaign and a Blended/D7 campaign are not comparable at face value.- The export’s final calendar day is always partial — exclude it from status/peak/trend calls.
- Buyer/team-handle tokens that appear on every campaign from one account are not creative concepts — drop them from concept ranking.
- CTR is not a creative-quality signal on AppLovin exports; use IR (installs ÷ impressions).
- Two dimensions can be perfectly (not just partially) confounded — cross-tab spend by both before a two-factor cut, or an empty off-diagonal will get misread as a real effect.
- Summing
DAU/DAVacross an app’s format rows inflates by the format count — dedupe first. - Trust recomputed ARPDAU (
revenue ÷ deduped DAU), not the provided per-format column. - Zero-impression/zero-revenue format rows mean “not running” — omit, don’t average in as zero.
- Banner imp/DAU in the hundreds is refresh, not anomalous; never compare banner to full-screen formats on imp/DAU or eCPM — use revenue/DAU.
Related skills
Section titled “Related skills”t1k-marketing-analytics-crawldata(live multi-network API crawl, own portfolio) andt1k-marketing-monetization-applovin-max(MAX SDK, ad-unit config, Reporting API). Full bullets:references/related-and-status.md.
Security
Section titled “Security”Read/analysis-only. Any mutating ad-network call (pause, budget, bid, waterfall) is a separate,
high-risk action gated by rules/ad-network-mcp-write-safety.md — never inferred or triggered
from this skill.
Status
Section titled “Status”Domain-knowledge playbook, no bundled scripts. Any project-level executable SSOT is pointed to from CLAUDE.md and kept in sync via /t1k:sync-back. Full status text: references/related-and-status.md.