Written by Ar.Bhavesh Panse, AI app growth marketer | ZuAI: 10K → 2M users at $0.02 CAC | $300k/mo ad spend managed
AppGrowth Marketer

Apple Search Ads payback period: how to calculate it (and ROAS) Judge every campaign on the day it pays you back.

How to calculate Apple Search Ads payback period and ROAS per campaign: the formulas, cohort steps, joining AdServices to revenue, and a payback ceiling.

the Apple Search Ads payback period is the number of days it takes for revenue from users you bought with Apple Ads (formerly Apple Search Ads, renamed in 2025) to cover what you spent on them. calculate it per campaign and per install week, using revenue after Apple’s commission and refunds, never as one blended account number.

the short version sits in my Apple Ads for apps guide. this is the full method.

What is the Apple Search Ads payback period formula?

payback day is the first day after install when cumulative net revenue from a cohort is at least the Apple Ads spend on that same cohort. a cohort is a group of users who installed in the same week from the same campaign. net revenue means what you keep after Apple’s commission and refunds, not the sticker price.

payback day = the first day where cumulative net revenue from the cohort is greater than or equal to the Apple Ads spend on the cohort

ROAS on day N = cumulative net revenue from the cohort by day N, divided by the Apple Ads spend on the cohort

How do you calculate payback per campaign, step by step?

work one campaign and one install week at a time. take that week’s spend from Apple Ads, find the users the campaign brought in that week, add up what they paid by day 7, 30, 60 and 90, and divide by spend at each checkpoint. the first checkpoint at or above 1.0 is your payback window.

  1. pick the cohort. one campaign, one install week. ten minutes.
  2. pull spend. export spend for that campaign and week from Apple Ads reporting. five minutes.
  3. know what an install means. Apple’s reporting definitions count new downloads and redownloads, tap-through within a 30 day window and view-through within one day.
  4. pull revenue by day since install. net revenue from those exact users at day 7, 30, 60 and 90.
  5. divide. cumulative revenue over spend at each checkpoint. that is ROAS. the first one at 1.0 or above is the payback window.
  6. repeat weekly. one row per campaign per week in a sheet. once the data join below exists, this takes about an hour a week.

How do you get revenue per Apple Ads cohort?

you join two records: Apple’s attribution, which says which campaign, ad group and keyword brought a user, and your purchase data, which says what that user paid. Apple’s AdServices API supplies the first. RevenueCat or a mobile measurement partner (MMP, a tool that tracks installs across ad channels) does the join for you.

in plain steps:

  • the app asks Apple once. on first launch, an SDK requests an AdServices attribution token and exchanges it with Apple for campaign, ad group, keyword and ad IDs. Apple’s measuring ad performance page shows the payload. Apple’s attribution overview says this data is kept for up to 21 days, so collect it at first launch.
  • RevenueCat route. its Apple Search Ads integration collects the token through the Purchases SDK, fetches the data within 24 hours, and lets charts break revenue down by campaign, ad group and keyword.
  • MMP route. Apple’s MMP help page notes that MMPs count an install at first open and may use different windows, so their numbers will not match the Apple Ads dashboard exactly.
  • pick one source of truth. spend from Apple Ads, users and revenue from your join.

What is the difference between ROAS and payback period?

ROAS is a ratio on a fixed day, such as revenue by day 30 divided by spend. payback is a date, the first day that ratio reaches 100 percent. ROAS shows progress toward getting your money back. payback shows when cash returns. read both, because each one hides something the other shows.

metricformulaanswersmisleads when
ROAS (day N)net revenue by day N ÷ spendhow much came back so farthe window is too short, or revenue is gross
payback periodfirst day ROAS is 100% or morewhen the spend is coveredusers churn right after payback
  • ROAS misleads when you read day 7 for a monthly subscription that earns most of its money in renewals, or when revenue is counted before Apple’s commission and refunds.
  • payback misleads with annual plans, where one upfront payment makes payback look instant even if nobody renews. it also ignores what happens after: a campaign that pays back on day 40 and then stops earning can be worse than one that pays back on day 70 and keeps going.

for the lifetime side of this, see LTV to CAC ratio for apps.

Why do brand campaigns flatter your average?

people who search your app’s name already decided they want it. many came from TikTok, word of mouth or press, and a share would have installed without the ad. so brand cohorts convert well, pay fast and pull the blended payback down, hiding category and competitor campaigns that never pay back.

never judge the account on its average. report brand on its own line and budget every other campaign on its own payback. the four campaign types are set out in the Apple Ads guide.

A worked example with illustrative numbers

this example uses illustrative numbers for one install week, not data from a real account. it shows how a blended view says “paid back around day 90” while two of the three campaigns have not paid back at all. read it row by row, not from the bottom line.

campaignspendday 7 revenueday 30 revenueday 90 revenueday 90 ROASpayback
brand$400$260$520$800200%around day 20
category$1,200$240$600$1,08090%not yet
competitor$600$60$180$33055%not yet
all campaigns$2,200$560$1,300$2,210100%around day 90

the blended row looks fine. underneath, brand is doing all the work. category is close and worth watching for another month. competitor is far off: cut bids, narrow keywords or pause it.

How do you set a payback ceiling?

a payback ceiling is the longest payback you will accept before cutting a campaign. it comes from two things: how long you can wait for cash to return, and how long your users keep paying. the ceiling must be shorter than both, with a margin, or you are lending money you may not get back.

  1. cash. how many months can spend sit unrecovered without hurting payroll or runway?
  2. retention. from your own data, how long does a typical paying user keep paying? the ceiling must sit well inside that.
  3. pick the shorter of the two, and write it down before you look at campaign results.
  4. apply it at a fixed check day. if a campaign’s ROAS curve cannot reach 100 percent by the ceiling, lower bids or cap budget. if it pays back well inside the ceiling, raise bids carefully.

at the budgets i have managed, up to $300k a month in ad spend, a blended number is too easy to hide behind, so i read payback per campaign every week. to sanity check the lifetime side, run your numbers through the LTV to CAC calculator.

what to measure every week: spend, attributed users, day 7 and day 30 ROAS, and projected payback day, per campaign, with brand always on its own line.

Frequently asked questions

What is a good payback period for Apple Search Ads?

there is no universal number, and anyone quoting one is guessing about your app. a good payback period is one shorter than your own ceiling, which comes from how much cash you have and how long your users keep paying. a funded subscription app can wait longer than a bootstrapped one. set the ceiling first.

What is the difference between Apple Ads ROAS and payback?

ROAS is a ratio at a fixed day: revenue from a cohort by day 30, for example, divided by what you spent on it. payback is a day: the first day that ratio reaches 100 percent. ROAS tells you how far along you are, payback tells you when your money comes back.

Do I need ATT consent to measure Apple Ads revenue?

not for the basic campaign level join. Apple Ads attribution runs through Apple's AdServices API, and RevenueCat's docs say its standard attribution needs no user consent, while detailed attribution requires App Tracking Transparency consent. check your own measurement partner's docs, because each one handles consent and data fields a little differently.

keep reading

More from the playbooks