UA Report

Overview

UA Report provides a unified view of acquisition cost, user behavior, and monetization, allowing you to evaluate not just traffic volume, but its actual value and payback over time.

Unlike event date-based reports (such as Product Report and Custom Events Report), where metrics are analyzed based on the date an event occurred, the cohort approach groups users by their install date and enables analysis of their behavior over time — from the moment of acquisition.

This allows you to track revenue, retention, and user value dynamics throughout the entire user lifecycle.

The report enables you to evaluate campaign efficiency, compare traffic quality, and understand how quickly users start generating revenue.

The report helps answer key questions:

- How quickly users start generating revenue

- Whether advertising campaigns are profitable

- Which traffic sources bring higher-value users

- How user behavior and monetization evolve over time

All data in the report is grouped into cohorts — users who installed the app within a selected time period.

How data is structured

This is the core principle of the report — all metrics are aligned to user lifetime after installation.

  • Each row represents a cohort of users grouped by install date
  • All metrics are calculated relative to D0 (install day)
  • Metrics labeled as D{x} represent cumulative values over X days after install
  • Unless stated otherwise, all values are cumulative

Data is updated daily and available for up to 720 days since install. Aggregation is performed based on selected filters.

How to find the report

To access the UA Report in Magify:

Magify > Analytics > Reports > UA Report

Magify-Analytics-UA-Report

Data types

The report combines two types of metrics:

  • Fact — actual data collected from sources
  • Predict — forecasted values generated by ML models

Predict metrics allow estimating future cohort performance at early stages, before full data is available.

Predict metrics are recalculated as additional fact data becomes available.

Metrics can be divided into:

  • accumulated (lifetime) metrics
  • fixed-period metrics (D0, D1, D7, etc.)

Data sources

The report combines data from multiple sources at the user level.

It includes:

  • acquisition data (impressions, clicks, cost) from UA grabbers
  • install and attribution data from MMPs
  • revenue data (ads, IAP, subscriptions) from SDK and app stores
  • predicted metrics calculated by internal ML models

The install date is used as the reference point for cohort formation.

Purchase and subscription data are collected and/or validated through app stores, while user activity and ad revenue are tracked via the Magify SDK.

All monetary values are converted to USD for consistency. Store fees are excluded from revenue metrics.

Main sources

  • UA Grabbers — cost, impressions, and clicks
  • MMP (Adjust / AppsFlyer) — installs, attribution, traffic sources
  • Transaction Validator (Magify / RevenueCat) — purchases and validation
  • Ad Mediation (AppLovin MAX / LevelPlay) — ad revenue
  • Magify SDK — sessions, user activity, events
  • Predict models — forecasted revenue and ROAS based on historical data

Filters / Dimensions

Dimensions are structured from higher-level groups to more granular ones:

Media Source > Campaign > Promo Creative > Creative Type > Adset > Ad

Not all traffic sources support the same structure. Depending on the source, Adset and Promo Creative fields may contain publisher IDs or names.

Metrics

Metrics labeled as D{x} represent cumulative values over X days after install.

Examples:

  • D7 Revenue — revenue within 7 days
  • D30 Revenue — revenue within 30 days

General metrics

These metrics provide a high-level overview of traffic acquisition performance and are calculated for all users within the cohort.  They are used to evaluate the efficiency of user acquisition campaigns.

Revenue metrics

These metrics represent the total revenue generated by the cohort and its components. Total revenue consists of multiple monetization sources:

Total Revenue D{x} = Ad Revenue D{x} + IAP Revenue D{x} + Subs Revenue D{x}

Revenue metrics are available in different formats:

  • before ref — before refunds
  • Net — after refunds
  • Ref. — refunds

Predicted metrics are derived from predicted revenue:

  • Predicted ARPU = Predicted Revenue / Installs
  • Predicted ROAS = Predicted Revenue / Cost
  • Predicted ARPPU = Predicted Revenue / Paying Users

Paying users analysis

These metrics include all types of purchases and are used to evaluate campaigns focused on acquiring paying users.

Subscription analysis

These metrics include only subscription-related events and are used to evaluate campaigns focused on subscription conversions.

IAP analysis

These metrics include only one-time purchases and are used to evaluate campaigns focused on in-app purchases.

Customer loyalty

These metrics are used to track user retention and understand how users return to the app over time.

Retention may differ depending on the data source:

Predict-specific metrics

These metrics are used to estimate future cohort performance based on early data. 

Predictions are calculated for the following horizons: D1 / D7 / D30 / D90 / D180 / D360 / D720

How the ML revenue prediction model works

The model uses a baseline + residual prediction approach.

Predictions are calculated at the user level (client_id) and then aggregated at the report level.

Baseline

Uses early-stage revenue:

  • D1
  • D7
  • D30

Residual

Predicts additional revenue beyond baseline.

How revenue prediction is built

The model uses early user data:

  • revenue progression
  • behavioral patterns
  • contextual attributes (country, app, source, device)

Based on this, it predicts:

  • Total Revenue
  • Ad Revenue
  • IAP Revenue
  • Subscription Revenue

Derived metrics:

  • Predicted ARPU
  • Predicted ROAS
  • Predicted ARPPU
  • Prediction Error

Data requirements

  • At least 1000 users within the analyzed time window (depending on the prediction horizon)
  • Availability of early revenue (D1 / D7 / D30)
  • D1 Revenue > $100 recommended
  • Historical data improves prediction accuracy

When to use Predict

  • early performance evaluation
  • campaign scaling decisions
  • traffic quality comparison

Use case

The report is used to monitor performance and optimize acquisition campaigns.

Analysis typically starts at the overall app level and can be broken down into traffic sources, campaigns, and geographies.

Common metrics:

  • Spend
  • CPI
  • ARPU
  • ROAS
  • Retention
  • payer conversion

Weekly analysis is recommended due to strong seasonality in traffic acquisition.

Glossary

Related articles

Understanding Parent And Nested Campaigns

Revenue Type Cohorts Report

Ad Revenue

Campaign Analysis

Product Report

User Activity