← All posts
November 17, 2026

Today Tab and Product Page Placements in Apple Search Ads: Why Turning Them On Muddies Your Search Results Numbers

Apple Search AdsASOindie iOS devpaid acquisitioncampaign structureApp Store marketing

Most indie developers who run Apple Search Ads start in one place: Search Results. You pick keywords, set bids, and watch taps and installs come in from people who typed something into the App Store. That is a clean setup to reason about. The trouble starts when you enable the other placements, the Today tab and Product Pages, because they change the traffic mix behind the same campaign and the same numbers. This post explains what those placements are, why they blur your reads, and how to keep your decisions honest.

What the other placements actually are

Apple Search Ads can show your app in several places. Search Results shows your ad when someone searches the App Store, and it is the placement you control most directly through keywords, match types, and bids. The Search tab is a separate surface for people browsing search suggestions there. The Today tab shows ads in the editorial feed people see when they open the App Store. Product Pages, sometimes called browse placements, show ads on other apps' product pages in the App Store.

The key difference is intent. A person who searched for a term has told you what they want. A person scrolling the Today tab or looking at a neighboring app's page has not. Their tap is still a tap, and it still costs you CPT, but the reason for it is different, and that difference is what distorts your data.

Why mixing them muddies every number

Suppose you enable Today and Product Pages on a campaign that was previously Search Results only. Your impressions go up, taps go up, and installs may go up. Then your blended TTR drops, your conversion rate changes, and your CPI moves. You might conclude that a keyword got worse, or that your product page slipped, when the real change was the audience mix.

Three things get confused:

  • TTR. Search Results taps usually come from people already interested in the category. Browse taps often come from people with no search intent, so TTR can fall even if your listing is performing exactly as before.
  • Conversion rate. Installs from browse placements can convert differently from installs driven by a search, so your install-per-tap figure shifts for reasons unrelated to your page.
  • Cost per install. A higher CPI on a blended campaign can hide the fact that your search traffic is fine and the browse traffic is what is expensive.

The result is that you start making bid and keyword changes to fix a problem that was introduced by the placement mix.

A practical way to keep reads clean

Start with Search Results alone

For most indie apps, the first useful question is whether your search-driven traffic pays back. Keep one campaign focused on Search Results until you have a stable picture: which keywords get impressions, which get taps, and which produce installs at a cost you can live with. Only then is it worth asking what the other placements add.

Separate placements into their own campaigns

If you want to test Today or Product Pages, put them in a separate campaign rather than toggling them on in your search campaign. Separate campaigns give you separate budgets, separate bids, and separate reports, so neither traffic type contaminates the other. Check your own reporting first, because breakdowns by placement are not always available in every view, and the separate-campaign approach does not depend on that.

Read each placement against its own baseline

Do not compare a browse campaign's TTR to your Search Results TTR. They measure different behavior. Judge each campaign against its own history: is this week's CPI within the range this campaign has previously shown, and does it produce installs at a rate that suits your economics? A browse campaign can be a fine acquisition channel even if its TTR looks weak next to search.

Watch revenue, not just installs

Installs from different placements can have very different downstream behavior. Once attribution data flows through a tool that maps installs to purchases, compare revenue per install across campaigns, not only cost per install. A cheap install that never pays is not a win, and a pricier install from a higher-intent surface may be worth more. Remember that revenue takes time to arrive, so give a new campaign enough days before drawing conclusions.

Change one thing at a time

When you do turn on a new placement, avoid changing bids, keywords, and the product page in the same week. If you do, you will not know which change moved which number. Enable the placement, leave everything else steady, and let it run long enough to produce a meaningful sample before the next change.

Common mistakes to avoid

  • Toggling browse placements on in your main search campaign and then reading the blended TTR drop as a keyword problem.
  • Judging a Today or Product Pages campaign by search-style TTR expectations.
  • Setting one shared budget across placements with very different costs, so the cheaper surface quietly absorbs spend.
  • Adding placements and product page changes in the same week, then guessing which caused the result.

Takeaway

The Today tab and Product Page placements are legitimate ways to reach people, but they are a different kind of traffic than someone typing a query. Keep your Search Results campaign as a clean, intent-driven baseline, put other placements in their own campaigns, judge each against its own history, and track revenue as well as installs. Clean structure is what makes every later decision easier to trust.

If you find this kind of reconciliation tedious, AdsBuddy reads your Apple Search Ads and revenue data and suggests a short, prioritized list of changes each day. You review and approve every one before anything is applied, so the judgment stays with you.

Run Apple Ads with AdsBuddy

Connect Apple Ads and RevenueCat, then get a short prioritized list of changes to review and apply. Plans from $29/mo.

Get started
Get new posts in your inbox
Practical Apple Search Ads tactics for indie iOS devs. No spam, unsubscribe anytime.