By Dilhan · · 5 min read
Apple Search Ads Installs but No Subscriptions: What to Check
Diagnose the gap between Apple Ads installs and paying subscribers with a tracking check, a post-install funnel, and a worked campaign example.
Start with the gap between download and first payment
If Apple Search Ads reports installs but your app has no subscriptions, check four things in order: whether purchases are recorded, whether users reach the paywall, whether they start trials, and whether those trials have had time to finish. Changing bids before these checks makes it harder to identify the problem.
Apple now uses the name Apple Ads. Its reporting terminology also matters: the platform's acquisition and conversion metrics describe downloads. They do not mean a subscriber has paid. Apple distinguishes new downloads from redownloads and tap-through from view-through installs. Compare the same definition throughout your investigation. Apple's reporting definitions explain these measures.
1. Prove that one purchase reaches your analytics
Before interpreting an empty revenue chart, follow a test customer through the purchase path. Use your billing provider's test environment and keep test transactions separate from production reporting.
Record the identifiers at first app open, account creation, trial start, and the billing event. Check that the subscription belongs to the same person in the product and billing systems. A successful checkout with no matching analytics customer is a measurement issue, even if the user experience worked.
When using OnRamp with RevenueCat, follow the RevenueCat identity setup. Also check that the webhook was delivered and that its environment and project match your app. A purchase button click is purchase intent; use the billing event to confirm payment.
Treat acquisition coverage separately. Some product users may have no usable campaign attribution. Keep them in an unknown-source group rather than assigning them to a keyword because it looks plausible.
2. Build a funnel from first open to payment
Use events that represent completed actions. A screen becoming visible and a user successfully completing its task are different events.
| Milestone | Question it answers |
|---|---|
| First app open | Did the downloaded app actually run? |
| Onboarding started | Did the user enter the intended flow? |
| First useful outcome | Did the app deliver what the ad promised? |
| Paywall viewed | Did the user see an offer? |
| Trial started | Did the billing system confirm a trial? |
| First paid transaction | Did that customer make an initial payment? |
The order depends on your app. An upfront paywall can precede the first useful outcome; a freemium app may expose the offer much later. Model the path users actually take. Do not force a single funnel across two different offers.
Use the onboarding funnel calculator to inspect your step counts. For instrumentation, start with the mobile conversion tracking guide.
3. Locate the loss with actual counts
Here is a hypothetical campaign, with every rate calculated from the previous row. These numbers are illustrative, not category benchmarks.
| Step | Users | Conversion from previous step |
|---|---|---|
| Attributed first opens | 100 | — |
| Onboarding completed | 60 | 60% |
| Paywall viewed | 40 | 66.7% |
| Trial started | 8 | 20% |
| First payment | 0 so far | Pending investigation |
This funnel contains at least two different questions. Twenty onboarding completers did not reach the paywall: check its trigger and whether the route to it is clear. Thirty-two paywall viewers did not start a trial: inspect offer eligibility, purchase errors, price comprehension, and whether the offer matches the search intent.
The final zero is still ambiguous. If all eight trials started yesterday and last seven days, a paid-conversion verdict is premature. If their observation window has ended, examine cancellations and payment outcomes. The trial cohort guide explains how to separate those states.
4. Compare keyword intent with the promise inside the app
For search results campaigns, inspect search terms alongside keyword targeting. Ask what the visitor expected to get immediately after downloading.
Someone searching for a free photo utility may react differently to a subscription offer than someone searching for a specialised professional workflow. That is a hypothesis to investigate, not proof that a keyword is bad.
Compare each cohort's onboarding, paywall, and trial outcomes. Keep country, offer, trial length, and app version comparable. If two cohorts receive different prices or trial eligibility, the keyword alone cannot explain their conversion difference.
When keyword-level attribution is unavailable, work at the campaign level you can support. Do not present a keyword revenue estimate as measured revenue.
5. Give the cohort enough time to pay
Decide the observation window before comparing cohorts. It should account for when the offer appears, the trial duration, and any billing outcome delay you intend to include.
A useful report shows paid customers, ended trials without payment, and unresolved trials separately. An active trial scheduled to renew is not yet a paid subscriber. A cancellation during an active trial is also different from a final expired trial.
For a young campaign, document what you know now and when the next decision becomes possible. You can fix a confirmed purchase error immediately. You cannot infer a mature trial-to-paid rate from trials that started this morning.
6. Change one diagnosed problem, then measure the same cohort definition
Write a short decision record: the failing step, the evidence, the proposed change, and the outcome window. Examples include repairing a paywall trigger, clarifying an offer, or tightening targeting around a supported use case.
Avoid redesigning onboarding, changing price, and replacing the campaign simultaneously. You may improve results, but you will lose the ability to explain which change helped.
OnRamp can put Apple Ads acquisition data, funnel events, and connected billing events alongside one another. Use the ROAS calculator for planning assumptions and the product for observed outcomes. Try OnRamp when you want to investigate the path from campaign to customer.
