Apple Ads placements are not four versions of the same inventory. They intercept four different moments in an App Store journey: an explicit query, the moment before a query, the storefront entry point, or a visit to another app's product page. A placement decision should therefore begin with the user state you want to test, the destination you can support, and the evidence you can reconcile—not with whichever placement reports the lowest last-click cost per acquisition.
The short answer: start with Search Results when you need query-level control and can operate keywords. Add Search Tab when you have a credible broader discovery proposition. Test Today Tab only when an approved custom product page and wider-reach message are ready. Consider Product Pages when adjacency to other app pages is strategically useful and the default-page destination is sufficient. None is universally the highest-quality placement.
Apple Ads Advanced currently offers four App Store placements: Search Results, Search Tab, Today Tab, and Product Pages while browsing. Apple also warns that placement eligibility can vary by app category, country, or region (Apple Ads, Ad placement options). Check eligibility in the account before building a budget model around inventory your app cannot buy.
Apple Ads placements comparison
Criterion Search Results Search Tab Today Tab Product Pages while browsing --- --- --- --- --- User context The person has entered a search The person is on Search before entering a query The person has opened the App Store front page The person is viewing another app's product page Primary control Keywords, Search Match, bids, negatives, audience settings Bid and audience settings Bid and audience settings Bid and audience settings, including category refinement Keyword control Yes No No No Maximize Conversions Yes, as a Search Results bid strategy No No No Destination support Default product page or Search Results ad variation from a custom product page; eligible CPPs may include a deep link Default product page or custom product page; eligible CPPs may include a deep link Approved custom product page required; eligible CPPs may include a deep link Default product-page assets and destination; Apple's feature table does not list CPP or deep-link integration Creative prerequisite App Store product-page metadata; optional approved CPP for an ad variation Default page or approved CPP Approved CPP plus approved app name, icon, subtitle, and CPP assets Existing default App Store product-page assets Buying model Cost per tap Cost per tap Cost per tap Cost per tap Best question to test Which expressed search demand merits budget? Can a broader discovery proposition earn qualified attention before a query? Can a storefront-level message create qualified discovery at the entry point? Does relevant app-page adjacency produce valuable discovery? Main interpretive risk Brand demand and high-intent queries can make results look more incremental than they are A cheaper or costlier tap says little about downstream value without cohort data Scale and visibility can be mistaken for causal lift Adjacency can be mistaken for intent, and no CPP means less message-to-destination control
Apple's current feature table places keywords, suggested ad-group bids, Maximize Conversions, target CPA, keyword recommendations, and custom-product-page ad variations only in Search Results. It lists cost-per-tap pricing, daily budgets, optional audience settings, insights, and API support across all four placements. The same table lists custom-product-page and deep-link integration for Today Tab, Search Tab, and Search Results—not Product Pages (Apple Ads, Ad placement options).
That is the operational dividing line. Search Results is a search-demand system. The other three placements are discovery surfaces with bids and audience controls but no keyword layer. Treating all four as one blended campaign question hides what each is capable of proving.
Which Apple Ads placement should you start with?
Choose the first placement whose prerequisites are satisfied and whose user context matches a specific growth question.
Start with Search Results when intent is the variable
Search Results reaches people after they enter a query. Apple offers two routes there: Manage Bids for manual keyword control and Maximize Conversions, which uses Search Match to prioritize queries likely to lead to installs. Search Results can use the default product page or ad variations based on custom product pages (Apple Ads, Ad placement options).
Use it first when your team can:
define brand, category, competitor, and discovery jobs separately;
maintain keywords, negatives, search terms, and bid ceilings;
distinguish branded demand from nonbrand discovery;
reconcile taps and App Store downloads with first opens and post-install events;
avoid reading observed brand conversions as proof that ads created all of that demand.
The detailed operating work belongs in our Apple Ads keyword strategy, while account and ad-group architecture belongs in the Apple Ads campaign structure guide. This article answers the prior allocation question: which App Store surface deserves a controlled test.
Add Search Tab when the proposition can work before a query
Search Tab appears at the top of the suggested-apps list before the user searches. Apple allows the default product page or a custom product page as the tap destination; a CPP can include a deep link where supported (Apple Ads, Ad placement options).
That makes Search Tab a discovery test, not a keyword expansion tactic. It may fit when the app has a recognizable category promise, the icon and store-page narrative make sense without query context, and the team can judge post-install value separately from Search Results. It is a weak test when the product requires a narrow query to become relevant or when the destination tells a generic story to every visitor.
Add Today Tab only after the destination is ready
Today Tab reaches people on the App Store front page. Apple requires a custom product page as the tap destination, and the app name, icon, subtitle, and CPP assets must be approved for advertising before the ad can run. Apple also says deep links from these CPPs are available on supported devices running iOS 18 or later (Apple Ads, Ad placement options).
The custom product page is therefore a gate, not a decorative upgrade. The message, selected assets, store destination, localization, and post-install path need to form one coherent proposition. Apple's developer documentation says custom product pages can vary screenshots, promotional text, and app previews, and can be measured in App Analytics for impressions, downloads, redownloads, conversion, retention, and proceeds-related indicators (Apple Developer, Custom product pages). Those are capabilities and reporting dimensions, not evidence that a CPP or Today Tab will improve a particular app's economics.
Add Product Pages when adjacency is a real hypothesis
Product Pages while browsing reaches people after they scroll to the bottom of another app's product page, where the ad can appear in the You Might Also Like area. Apple says this inventory can run across app categories or be refined to categories (Apple Ads, Product pages). It is unavailable in mainland China, and the current feature table excludes Product Pages from custom-product-page and deep-link integration (Apple Ads, Ad placement options).
This placement needs an adjacency thesis: which browsing contexts could make your app relevant, and why? “More reach” is not a thesis. Because the destination control is narrower, the default product page must carry the promise without a placement-specific CPP. If your acquisition message depends on a tailored store narrative or exact in-app destination, repair that mismatch before funding the placement.
Use a placement eligibility contract before budget allocation
Create one row per proposed placement and do not launch until each required field has an owner.
Contract field Required decision Evidence before launch Owner --- --- --- --- User state Querying, pre-query discovery, storefront discovery, or app-page browsing Written job for the placement UA lead Eligibility App, category, country, region, and account can use the placement Account or API eligibility check UA operations Destination Default page, CPP, or supported CPP deep link Approved destination in target storefront Store owner Message Promise fits the placement's context Message-to-asset review Creative and product marketing Buying control Bid method and financial ceiling Approved CPT ceiling and daily budget Growth and finance Measurement Tap-through, view-through, total, new download, redownload, and post-install definitions Signed metric dictionary Analytics Cohort outcome Activation or value event and maturity window Event QA and cohort query Product analytics Decision Keep, repair, expand, constrain, or stop Predeclared rule and review date Growth owner
Apple's API journey documentation says teams can query app eligibility by placement and country or region, and should use the app's available storefronts before selecting campaign targets (Apple Developer, Advertising Your App on the App Store). Eligibility is a prerequisite, not a forecast.
The feature table currently lists Today Tab, Search Tab, and Search Results in 91 countries and regions, and Product Pages in 90, excluding mainland China. Category restrictions may vary by country or region (Apple Ads, Ad placement options). Record the exact storefront scope used in the test instead of referring loosely to “global Apple Ads.”
Measurement: do not compare placements on one reported CPA
Apple's Campaigns dashboard can separate the placement and expose tap-through, view-through, and total installs; it also reports new downloads and redownloads in tap-through, view-through, and total forms (Apple Ads, View Campaigns dashboard metrics). These are different numerators. A comparison becomes invalid when one placement is judged on tap-through new downloads and another on total installs that include views and redownloads.
Build a placement scorecard with three layers.
1. Apple Ads delivery and App Store response
Record spend, impressions, taps, tap-through rate, average CPT, and the selected download measure. Keep these definitions identical across placement rows. If view-through is included, show it separately rather than only in “total.”
2. Acquisition type and app-entry continuity
Separate new downloads from redownloads. Then reconcile App Store-reported downloads with first opens or another first-party app-entry event. A redownload may be commercially useful, but it is not the same acquisition job as a first-time user. Likewise, a download that never becomes a first open should not carry the same value as a verified app session.
3. Post-install value at a fixed cohort age
Compare a defined activation, trial, purchase, subscription, qualified lead, retained use, or contribution measure at the same maturity window. If one cohort has had 21 days to mature and another has had three, the apparent winner may be calendar age rather than placement quality.
This is why last-click CPA is not automatically comparable across placements. The surfaces occur at different user moments, view-through exposure may contribute differently to reported totals, the share of redownloads can differ, and brand Search Results can harvest demand that already existed. Platform CPA describes attributed App Store activity under the selected definition. It does not, by itself, establish incremental acquisition or downstream profitability.
For broader channel context, use the Apple Ads versus Google App campaigns comparison. Do not use that channel-level decision to substitute for placement-level measurement.
The brand cannibalization caveat
Brand Search Results often sit closest to explicit existing demand. Strong attributed conversion on an exact app-name query can coexist with limited incremental value.
Do not solve that uncertainty by declaring all brand spend wasteful or all brand traffic defensive. Instead:
separate brand from nonbrand Search Results;
record organic search visibility and competitor presence where observable;
avoid pooling brand Search Results with discovery placements;
define what risk the brand campaign addresses;
use a suitable incrementality design only when volume and operational conditions support one.
The same caution applies in reverse: a discovery placement may look worse on last-click CPA while contributing to later search or organic behavior. That is not proof of halo; it is a reason to avoid false comparability and consider a causal test.
A controlled Apple Ads placement test workflow
Step 1: Write one question per placement
Examples: “Can nonbrand Search Results produce activated first-time users within our allowable cost?” Never launch two placements under the shared question “Which performs best?”
Step 2: Pass the prerequisites
Confirm app and storefront eligibility, destination approval, event reliability, budget authorization, and a meaningful cohort window. Today Tab needs an approved CPP. Search Results keyword operation needs maintained terms and negatives. Product Pages needs a default product page that can carry the message. Search Tab needs a proposition that works without a query.
Step 3: Freeze the metric contract
Choose tap-through, view-through, and total fields deliberately. Fix the date range, time zone, currency, new-download/redownload treatment, first-open reconciliation, activation event, and cohort age. Apple's dashboard exposes the relevant breakdowns, but the team still owns the comparison definition (Apple Ads, View Campaigns dashboard metrics).
Step 4: Control what can reasonably be controlled
Keep geography, app version, offer, cohort window, and downstream event definitions aligned. Document unavoidable differences: placement context, destination options, creative format, and keyword availability are features of the treatment, not noise to erase.
Avoid simultaneous store-page, onboarding, price, tracking, and bidding changes. If one is necessary, timestamp it and restart the interpretation window where appropriate.
Step 5: Monitor gates, not daily winners
Check delivery, approvals, spend pace, destination continuity, data freshness, and material tracking breaks. Do not call a winner from an early CPA fluctuation. Small samples, delayed post-install events, redownload mix, and view-through attribution can all move the result.
Step 6: Reconcile placement to cohort
Join the placement-level report to the closest privacy-safe first-party or measurement-system cohort available. Compare the same definition of activated new user, payer, retained user, or contribution at the same age. Keep unmatched records and reporting differences visible rather than forcing totals to agree.
Step 7: Make one of five decisions
Keep: the placement answers its assigned job within the approved economics and evidence quality.
Verify: data is immature, small, delayed, or definitionally inconsistent.
Repair: destination, tracking, eligibility, bid, budget, or asset readiness is broken.
Expand: the evidence supports a bounded next test, not an unrestricted rollout.
Stop: the placement lacks a credible job, cannot meet prerequisites, or produces mature cohort economics outside the decision boundary.
Hypothetical placement arithmetic
This example is fictional and illustrates denominator discipline. It is not an Apple benchmark or a Sharply Labs result.
An app spends $8,000 across two placement tests:
Metric Search Results nonbrand Search Tab --- ---: ---: Spend $4,000 $4,000 Taps 2,000 2,500 Tap-through new downloads 800 750 Tap-through redownloads 80 250 First opens reconciled 720 680 Activated users at day 14 216 170
Using tap-through total installs, Search Results has 880 installs and a reported-style cost of $4,000 / 880 = $4.55 per install. Search Tab has 1,000 and a lower $4.00 per install.
But if the acquisition job is a newly activated user, use the consistent post-install denominator. Search Results produces $4,000 / 216 = $18.52 per activated user. Search Tab produces $4,000 / 170 = $23.53. The lower install cost did not become the lower activation cost because the redownload mix and activation continuity differed.
The example does not prove Search Results is better. Another app, geography, category, message, or period can reverse the result. It proves only that a placement decision changes when the denominator matches the commercial job.
Product pages and custom product pages are not interchangeable
A custom product page is a distinct App Store destination with tailored screenshots, promotional text, and app previews. Apple says teams can create up to 70 additional versions, assign unique URLs, and measure each page in App Analytics (Apple Developer, Custom product pages).
Within Apple Ads, CPP support depends on placement:
Today Tab requires a CPP.
Search Tab can use the default product page or a CPP.
Search Results can use a default ad or ad variations based on CPPs.
Product Pages while browsing is not listed for CPP or deep-link integration in Apple's current placement feature table.
Do not confuse Product Pages, the ad placement shown while people browse other apps, with custom product pages, the tailored destination mechanism. They solve different problems. Our App Store screenshots and paid UA guide covers how store assets affect the conversion path; it does not decide which Apple Ads placement deserves budget.
When not to add another placement
Do not add a placement when:
the app, category, or target storefront is ineligible;
Today Tab lacks an approved and coherent CPP;
Product Pages requires destination specificity the placement does not support;
Search Tab or Today Tab has no discovery proposition beyond “get more installs”;
Search Results keywords, negatives, and brand separation are not maintained;
download, redownload, first-open, and activation definitions are unresolved;
the team cannot fund a test long enough for the chosen post-install event to mature;
another store-page, onboarding, pricing, or tracking change will make attribution impossible;
the current placement has not yet produced a stable operational baseline;
the decision would be made from platform last-click CPA alone.
Adding inventory increases the number of surfaces that can spend. It does not automatically increase learning. A second placement deserves budget only when it asks a new question.
A practical allocation framework
Score each candidate from zero to two on five gates:
Eligibility: zero if unavailable, one if uncertain, two if confirmed.
Context fit: zero if the user moment conflicts with the proposition, one if plausible, two if the message is designed for that moment.
Destination readiness: zero if unsupported or unapproved, one if generic but functional, two if approved and message-matched.
Measurement readiness: zero if downloads cannot be reconciled, one if install-only, two if new/redownload and mature post-install value are comparable.
Decision capacity: zero if no action follows, one if the test changes a limited bid or budget, two if keep/repair/expand/stop rules are agreed.
An unavailable placement is disqualified. For eligible candidates, a higher score identifies readiness, not expected performance. If two placements score equally, choose the one that answers the more valuable unresolved business question with the smaller reversible budget.
For an iOS team deciding how this fits into a broader acquisition program, Sharply Labs' mobile app growth work connects media decisions to store conversion and post-install value. Our growth services cover paid acquisition, creative, conversion, retention, and attribution as one operating system.
What a scoped placement review should deliver
For app teams already spending or ready to run a meaningful test, a placement-and-measurement review should examine:
the job assigned to each current or proposed placement;
eligibility and destination prerequisites by storefront;
keyword and bid controls where they exist;
CPP, default-page, and deep-link constraints;
tap-through, view-through, new-download, and redownload definitions;
first-open, activation, and value reconciliation;
brand-demand cannibalization risk;
a prioritized keep, verify, repair, expand, or stop test plan.
That is the scope of the conversation we offer. It is not a promise of better CPA, more installs, incremental lift, or qualification for any Apple Ads placement. The deliverable is a defensible allocation and measurement plan your team can operate.