AppSkale.AI
Back to blog

Impressions but No Taps, or Taps but No Installs

By Sam H

A keyword can fail in two different rooms. People see the ad and do not tap. Or they tap, land on the product page, and do not install. Raising the bid only helps the first room if the problem was never getting seen. It does nothing useful for the second.

Apple’s names for those rooms are tap-through rate and tap-through conversion rate. Read them before you touch CPT.

The two rates

TTR is taps divided by impressions. The ad was on screen. Did anyone choose it?

CR (tap-through) is installs from taps divided by taps. Apple counts those installs in a 30-day window after the tap, and the count includes new downloads and redownloads.

There is also a view-through install: someone saw the ad, did not tap, and downloaded within one day. That is a different column. Do not fold it into a story about the product page, and do not ignore a weak tap rate because view-throughs made the total look kinder.

Impressions, almost no taps

The auction already decided you were relevant enough to show. The searcher disagreed with the ad. Usual causes:

  • The query is adjacent, not the job you do. A Broad or Search Match term is the common source. See the search terms report.
  • The name, subtitle, icon, or first screenshot answers a different search than the one you bought.
  • You are on a competitor’s name and the ad still looks like theirs. See competitor keywords.

A metadata edit can take up to two hours to show on the ad in the App Store, and up to 24 hours to show in the ad preview inside the account. Do not judge the new subtitle the same afternoon.

If impressions themselves are missing, that is a different diagnosis: bid, relevance, volume, or an audience you narrowed. See impression share and age and gender targeting.

Taps, almost no installs

They already chose the ad. The product page did not close. Bid is the wrong knob. Look at screenshots, ratings, the subtitle’s promise, and whether the first screen matches the search. A custom product page can help once you know the intent. It will not rescue a page that also fails organic traffic. See when custom product pages are worth it and CPI looks great, paywall conversion is terrible.

Installs are not subscribers. A healthy tap-through CR can still die at the paywall. Keep that third room in AppSkale, next to the keyword, or you will scale a page that only wins the download.

A short order of operations

  1. Wait until the row has enough impressions to talk about taps, and enough taps to talk about installs. A handful of either is noise. See how long to run a keyword.
  2. Low TTR: fix the query or the ad’s first impression. Pause clear mismatches. Do not raise CPT to force taps on a term people scroll past.
  3. Low CR after a real number of taps: fix the product page before you buy more of those taps.
  4. Both rates fine and revenue weak: the leak is after the install. Stop tuning the auction.

Where to go next

TTR asks whether the ad matched the search. Conversion rate asks whether the page matched the tap. Revenue asks whether the install was worth it. Change the room that is actually empty.

Related: CPT vs CPI, Exact vs Broad, and ROAS with RevenueCat.