Subscription Offer Eligibility Debug: Why Your ASA Installs Convert Low (Even When TTR Is Solid)

Apple Search Ads can look “healthy” in the middle of the funnel—reasonable TTR, solid installs—while your ROAS still collapses. When that happens, many indie teams waste time tweaking CPT bids, even though the real problem is earlier/later in the chain: your App Store subscription offer doesn’t apply to the user who clicked.

This post is about subscription offer eligibility (intro offers, free trials, and existing-subscriber rules). It’s a common mismatch between what Apple shows on the subscription funnel and what your ASA audience can actually claim.

Why offer eligibility breaks ASA conversion

Apple Search Ads attribution tells you installs and downstream revenue via the install→purchase chain. But it can’t tell you which users were eligible for the offer, or why they converted at a lower rate.

Here’s the failure mode:

• Your ad drives a user who appears similar at click-time.
• They land on the App Store and tap “Subscribe.”
• Their offer eligibility is different than what you assumed (or different than what your marketing page implies).
• The paywall still shows options—but the best option isn’t available for that specific user.

Common triggers:

• Region mismatch (the user’s Apple account / billing region doesn’t match the offer rules you’re targeting).
• Existing subscriber status (they already used a trial/intro offer on the same app in the past—even years ago in some cases).
• Trial/intro offer configuration (you changed offers recently; the App Store shows different terms than older users expect).
• “New subscriber” gating that unintentionally affects your ASA-driven cohort.

Result: you see good taps → installs, then weak conversion rate (installs → subscriptions).

Step 1: Confirm you’re not chasing the wrong KPI

Before debugging offers, sanity-check the funnel with the core ASA metrics:

• TTR (taps / impressions): still decent? okay.
• Install conversion rate (installs / taps): okay means the store page and listing are doing their job.
• CPA / CPI vs ROAS: ROAS bad but CPI okay usually means revenue is the issue, not acquisition.

If your ROAS problem is mostly “installs happen, subscriptions don’t,” move to eligibility debugging.

Step 2: Compare “what you think the user sees” vs “what actually applies”

You need to test the subscription funnel under multiple account scenarios. Don’t rely on one Apple ID.

Do these checks (minimum viable)

1. Test a fresh Apple ID (one that never subscribed to your app).
2. Test an Apple ID that already subscribed (and cancels, if possible).
3. Test from the same region as your ASA country (since each ASA campaign targets one country/region).
4. If you use RevenueCat (common for indie teams): verify your mapping is correct for your actual subscription products and entitlements.

What you’re looking for:

• Does the App Store show the expected free trial/intro offer for the fresh test user?
• Does it show a different offer (or no trial) for the “existing subscriber” scenario?
• Do users end up on a paywall where the “best deal” is not available?

Why this matters for ASA

ASA doesn’t auction “subscription eligibility.” It auctions for taps. If your ad messaging attracts users who are systematically ineligible for your promo, you’ll see exactly the “installs but poor subscriptions” pattern.

Step 3: Audit your offer configuration like it’s a product

This is where indie teams often miss something small but fatal: the offer configuration changed, but the funnel assumptions didn’t.

In App Store Connect (or via your subscription setup process), verify:

• You actually enabled the intended intro/free-trial offer for the subscription group.
• The eligibility rules match your strategy (new subscribers vs existing subscribers).
• You didn’t accidentally create products that show different offers than your paywall expects.

If you recently changed pricing/subscription products:

• Consider that existing cohorts in the last day/week might have different entitlement histories.
• Don’t judge the effect instantly; offer changes can take time to show across account scenarios.

Step 4: Check your paywall implementation for “offer drift”

Even if the App Store offer is correct, your app can still break the user’s path.

If you use RevenueCat + StoreKit purchase flows:

• Confirm you request the same product identifiers you configured.
• Confirm you use the correct entitlement mapping (especially if you have multiple subscription tiers).
• Validate that you aren’t gating UI with stale state (e.g., assuming a trial exists when it doesn’t).

Symptoms of implementation drift:

• Users hit checkout but don’t land on the expected paywall state.
• Your app shows “trial available” messaging even when StoreKit reports otherwise.
• Entitlement updates don’t match purchases (RevenueCat can help, but you still need to verify products/entitlements).

Step 5: Use ASA targeting to reduce ineligible cohorts

Once you know eligibility is the bottleneck, you can address it with audience shaping, not bids.

Concrete levers you can use (ASA-accurate):

• Keyword and match type selection (Search Results keywords):
  • If broad keywords are pulling in users who are more likely to be prior subscribers (or just less aligned), clamp with better match types.
  • Remember: on Search Results keyword targeting you can use exact and broad manually; Search Match uses automatic matching and can surface discovery queries you didn’t explicitly choose.
• Separate discovery from “deal intent” in different ad groups/campaign structures.
  • Even if you don’t run separate campaigns, split ad groups so you can compare subscription conversion.

Goal: make sure the traffic you pay CPT for is more likely to be actually eligible for the offer you’re trying to monetize.

A practical heuristic

If your ROAS is great from one set of keywords but terrible from others, don’t assume a copy issue—assume an eligibility mismatch until proven otherwise.

Example (illustrative):

• “Focus app” keywords yield strong trial subscriptions.
• Broad “free / premium / lifetime” style queries yield installs but low trial conversion. In that scenario, ineligible users aren’t automatically “worse users”—they’re mismatched users for your offer.

Step 6: Measure it the right way (because you don’t get “per-keyword revenue” from Apple)

Apple Search Ads provides attribution for install→purchase resolution, but it’s not “revenue per keyword” directly.

So your measurement stack should answer:

• For a given keyword set / ad group, what is the subscription conversion rate and revenue per install?

If you use RevenueCat:

• Make sure you can map ASA-attributed installs to revenue events (entitlements / subscription purchases).
• Validate that your attribution pipeline resolves within the expected window (Apple resolves the attribution token within about a day).

Then you can compute:

• Installs → subscriptions conversion (not just taps → installs).
• ROAS at the ad group/campaign level once enough data accumulates.

What to change first (a prioritized action list)

Here’s the order I’d use when I see “good installs, bad subscription ROAS”:

1. Test offer eligibility using at least two Apple IDs (fresh vs existing) in the same region as your campaign.
2. Verify App Store subscription offer configuration is what you expect for that product group.
3. Confirm RevenueCat / StoreKit product IDs and entitlements are aligned with the subscription products you’re promoting.
4. Segment ASA by keyword intent (and separate Search Match experiments from your “known-good” exact/broad sets).
5. Only after eligibility is fixed (or you have strong evidence it isn’t the issue), revisit bids.

Changing CPT while your offer applies to only a fraction of your ASA audience is like increasing ad spend on a landing page that’s showing the wrong price.

A quick note on using AdsBuddy (optional)

If you want an extra set of eyes on where your funnel breaks, tools like AdsBuddy can read your Apple Search Ads performance plus revenue mapping and return a short list of prioritized changes to approve—often highlighting whether the problem is acquisition efficiency (CPT/taps) or post-install monetization (where offer eligibility lives).

Closing takeaway

When ASA taps and installs look fine, your ROAS problem is often not an auction problem. It’s usually an eligibility problem: the offer you’re driving people toward isn’t available to the exact users you’re paying CPT for.

Debug the subscription funnel with multiple account scenarios, confirm offer configuration and entitlement mapping, then adjust ASA keyword intent (and match behavior) to bring the right users into eligibility.

If you want, tell me your setup (subscription vs consumable, intro offer type, and whether you use RevenueCat). I can suggest a concrete keyword/match-type split to test eligibility impact first.