Apple Ads campaign structure should make business decisions easier, not merely make the account look tidy. The familiar Brand, Category, Competitor, and Discovery model is a useful starting point for search-results campaigns. It becomes an operating system only when each campaign has a distinct job, overlapping queries are controlled, creative matches the search intent, and install data is connected to activation, retention, and economic value.
This guide explains how to build that system, when to use Manage Bids or Maximize Conversions, and when the standard structure is too fragmented for the evidence available.
The direct answer: structure around decisions, not naming conventions
For many established apps, a practical Apple Ads search-results account begins with four intent areas:
Brand captures searches for the app or company name.
Category covers nonbrand searches that describe the app, its use case, or the problem it solves.
Competitor isolates searches for relevant alternatives.
Discovery uses broad match and Search Match to uncover queries that deserve further investigation.
Apple recommends these four themes and advises using exact match with Search Match off in Brand, Category, and Competitor, while Discovery uses separate broad-match and Search Match ad groups. Apple also recommends adding exact-match negatives to Discovery for keywords already managed elsewhere. (Apple Ads campaign-structure guidance)
That architecture is a baseline, not a universal prescription. The right account may split further by country, product, customer value, budget owner, or distinct landing experience. A low-volume app may need fewer campaigns so that evidence is not scattered across dozens of nearly empty cells. A team using Maximize Conversions may deliberately exchange keyword-level control for automation. The structure should follow the decisions the team can realistically make.
Begin with the decision the account must support
Before creating another campaign, write down the business question it will answer. Useful questions include:
Does branded demand require different incrementality treatment from category demand?
Which nonbrand themes acquire users who complete the activation event?
Do competitor queries produce retained subscribers or only expensive first opens?
Which discovery terms should move into controlled exact-match groups?
Does a market deserve its own budget because customer value, language, or product economics differ?
Does a distinct intent require a custom product page rather than the default listing?
If two campaigns have the same audience, budget logic, destination, optimization method, and decision rule, the split may be administrative rather than analytical. Every additional campaign creates another budget boundary and another place where limited data can become inconclusive.
Use the following test:
Create a separate campaign only when the separation enables a different budget, bid strategy, market decision, message, measurement treatment, or stop rule.
This avoids two common extremes: one undifferentiated campaign that hides intent, and an overbuilt account whose segments never accumulate enough evidence to act on.
The four-part structure and the job of each campaign
Campaign role Query type Default control Primary business question Main risk --------------- Brand App and company names, close brand variants Exact match; Search Match off Are paid brand placements adding value that would not otherwise occur? Mistaking captured organic demand for incremental acquisition Category Nonbrand problem, feature, use-case, and outcome terms Exact match; themed ad groups Which qualified needs can the app serve economically? Mixing distinct intent and sending every query to one generic page Competitor Relevant app or company alternatives Exact match; narrow clusters Can the app credibly win a comparison or switching moment? Paying for navigational intent the product cannot satisfy Discovery Broad-match seeds and Search Match Dedicated routing with negatives Which queries deserve promotion, exclusion, or more research? Leakage into terms already controlled elsewhere and opaque low-volume reporting
Brand: measure incrementality, not just cheap acquisition
Brand campaigns often report strong conversion because the user already knows the app. That makes them useful for defense, message control, or re-engagement analysis, but it does not prove the ads created the demand.
Keep Brand separate so its apparent efficiency does not mask weaker category acquisition. Distinguish new downloads from redownloads where the available reporting permits it, and use a controlled holdout when the commercial importance justifies an incrementality test. The decision is not automatically “always bid” or “never bid.” It depends on organic coverage, competitor presence, query mix, market conditions, and the cost of running a defensible test.
Category: organize around a user job
Category is usually where the clearest scalable nonbrand intent lives. Do not put every generic term into one ad group simply because the keywords share an App Store category.
Group terms when they share a user job, a product promise, a suitable destination, and a post-install expectation. A budgeting app might separate “expense tracker,” “shared household budget,” and “subscription tracker” if each theme warrants different screenshots, activation events, or downstream value. If the listing and onboarding cannot support that distinction, more campaign granularity will not solve the underlying product-message gap.
Competitor: require a credible switching case
Competitor queries can be commercially meaningful, but the user may be looking specifically for another product. Before bidding, verify that the app offers a truthful reason to consider it and that the product page communicates that reason without misrepresenting the competitor.
Use narrow clusters, review trademarks and local requirements, and treat strong tap-through or install rates as incomplete evidence. The decisive question is whether those users activate and produce acceptable value after acquisition.
Discovery: build a routing loop, not a dumping ground
Discovery is valuable when it creates decisions. Apple’s recommended Manage Bids structure uses one broad-match ad group with Search Match off and a separate Search Match ad group with no keywords. Exact-match negatives prevent Discovery from matching terms already controlled in Brand, Category, or Competitor. (Apple Ads structure help)
For each meaningful search term, choose one action:
Promote: add it as an exact-match keyword to the correct controlled theme, then add it as an exact negative in Discovery.
Continue learning: leave it in Discovery because relevance is plausible but evidence is insufficient.
Exclude: add a negative when the meaning is irrelevant, unsupported, or economically inappropriate.
Investigate: review the product, listing, attribution, or search-term context before changing exposure.
For the full operating detail behind these decisions — evidence thresholds, negative routing, and bids derived from post-install payer economics — see our Apple Ads keyword strategy guide.
Do not promote a term because it produced one install, and do not exclude it because of one expensive tap. Decision thresholds should reflect conversion delay, expected value, evidence volume, and the cost of a wrong decision.
Manage Bids versus Maximize Conversions
Apple Ads currently offers two approaches for search-results keyword selection and bidding. Manage Bids uses max cost-per-tap controls at the ad-group and keyword levels. Maximize Conversions uses an auto-bidder and Search Match to pursue installs around a target CPA, without requiring ordinary keyword-bid management. (Apple Ads campaign creation, Apple Ads bid guidance)
Decision factor Manage Bids Maximize Conversions --------- Primary control Keywords, match types, max CPT bids, negatives, themed ad groups Target CPA, daily budget, automated matching and bidding Best fit Teams that need query routing, intent-specific creative, and granular control Teams willing to automate query selection to simplify management or expand discovery Evidence visibility More explicit relationship between targeting keywords, search terms, and bid decisions Less need for manual keyword operation; analysis should respect the automated strategy Main risk Excessive manual fragmentation and reactive bid changes Optimizing toward installs when post-install quality varies materially Practical test Can the team act differently on the added detail? Is install CPA a sufficient proxy for the business outcome?
Apple states that Maximize Conversions optimizes bids using a target CPA, recommends enough daily budget for at least five conversions per day, and advises allowing at least two weeks before assessing impact. It is described for post-launch rather than pre-order campaigns. Those are platform recommendations, not a guarantee that the resulting users will meet a particular retention or revenue target. (Apple Ads Maximize Conversions guidance)
The key tradeoff is objective alignment. If two keyword themes produce similar install CPA but sharply different activation or payer rates, an install-focused automated strategy can appear healthy while the economics deteriorate. That does not make automation wrong; it means the measurement system must supply an independent value check.
A sensible account can also use both approaches for different jobs. For example, a team might retain controlled Manage Bids campaigns for proven category themes and run a bounded Maximize Conversions test for broader discovery. The test should have a stated budget, duration, primary outcome, guardrails, and a comparison that accounts for cohort maturity. Avoid changing the target, budget, product page, and onboarding simultaneously; otherwise the result becomes difficult to interpret.
Decide when to split countries and regions
Country separation is valuable when it creates a real control boundary. Apple notes that a single country or region can be appropriate for large markets requiring dedicated budgets or unique objectives, while grouped markets can simplify management when customer value, language, goals, or regional operations are similar. (Apple Ads country and region guidance)
Split a market when one or more of these differ materially:
language and App Store metadata;
product availability or pricing;
activation and monetization behavior;
allowable acquisition cost;
legal or operational constraints;
budget ownership;
custom product page requirements;
the decision to scale, hold, or stop.
Do not create a country campaign merely because the platform allows it. If several low-volume markets share language, value assumptions, and the same operating decision, grouping may produce more useful evidence. Revisit the grouping when volume or economics justify a separate treatment.
Match creative to the promise behind the query
Campaign structure and creative structure should describe the same intent. Apple Ads ad variations can use custom product pages created in App Store Connect. Apple recommends connecting the custom page content with the ad group’s keyword theme; the custom page becomes the destination after the tap. (Apple Ads ad variations)
Build the mapping explicitly:
search intent → user job → product promise → screenshots and preview → objection handled → in-app destination → activation event
For a meal-planning app, “family meal planner” and “macro tracker” may both sit under the same category, yet imply different screenshots, proof, onboarding paths, and activation events. A custom product page is useful only if the product genuinely supports the promise and the traffic volume can support a meaningful decision.
Do not assume a custom product page creates a fixed conversion lift. It can improve message continuity, but the result depends on the query, creative, listing, product, audience, and measurement window. Evaluate tap-to-install behavior alongside downstream quality. A page that produces more installs but fewer activated or paying users is not necessarily an improvement.
Connect Apple Ads reporting to post-install value
An account structure becomes commercially useful when each segment can be evaluated at the highest reliable outcome available. Use a measurement ladder:
impressions and taps;
attributed downloads, separated into new downloads and redownloads when available;
first opens;
a defined activation event;
trial, purchase, subscription, lead, or another monetization event;
retained contribution or payback at a stated cohort age.
Each rung comes from a different measurement context. Apple Ads reports App Store activity; an MMP or product analytics system may use first open; a subscription backend may define payer and net revenue; finance may define contribution margin. These values should be reconciled, not forced to match.
Apple describes AdServices and AdAttributionKit as complementary privacy-preserving approaches. AdServices can provide Apple Ads campaign, placement, ad-group, and keyword-level attribution. Apple also notes that AdServices uses Apple’s first-party data and may disagree with AdAttributionKit when another registered network participates in the path. (Apple Ads attribution documentation)
Apple further explains that MMPs can incorporate Apple Ads data, but reporting may differ because Apple Ads counts App Store-verified downloads following a tap or view while an MMP commonly bases an install on first open. Attribution windows and redownload handling may also differ. (Apple Ads guidance for mobile measurement providers)
Document these definitions before comparing dashboards. At minimum, record:
account time zone and reporting date range;
currency;
tap-through, view-through, or total attribution;
new downloads versus redownloads;
download versus first-open definitions;
conversion windows;
cohort age for revenue or retention;
privacy-suppressed or aggregated rows;
the join logic between acquisition and downstream events.
Without that record, a disagreement between platforms can look like campaign failure when it is actually a difference in event definition.
A calculation framework for bid and value decisions
For Manage Bids, a team can translate downstream economics into a directional cost-per-tap ceiling. The arithmetic is straightforward; the input quality is the difficult part.
Use net or contribution value rather than gross revenue when the required cost inputs are available. Align all rates to comparable cohorts, markets, attribution rules, and dates. Treat the result as a sensitivity model, not a platform truth. Small samples, delayed revenue, trial conversion, refunds, fees, and retention uncertainty can materially change the answer.
Example with deliberately hypothetical inputs: if an app can afford $40 per new payer, 8% of new downloads become payers, and 35% of taps become new downloads, the directional max CPT is:
This is not a benchmark or a recommended Sharply Labs bid. It demonstrates the dependency chain. If the payer rate falls from 8% to 4%, the same model cuts the directional ceiling in half. The correct response is often to improve the evidence and product funnel before increasing bidding complexity.
Diagnostic matrix: what to inspect before changing structure
Symptom Inspect first Working hypothesis Appropriate next step ------------ No impressions Status, eligibility, demand, relevance, market, bid strategy The campaign cannot enter or win enough eligible auctions Fix the blocker before rebuilding the account Strong tap-through, weak install rate Query-to-page match, listing, ratings, product availability The ad earns attention but the destination does not resolve the intent Narrow the query or align the product page Efficient installs, weak activation Search-term intent, onboarding, technical quality, redownload mix The acquisition metric is disconnected from product value Segment cohorts and inspect the activation path Discovery spends but yields few visible terms Privacy aggregation, search-term reporting, market volume Evidence is concentrated in aggregated or low-volume rows Keep uncertainty explicit; do not invent term-level conclusions Brand looks dramatically better than Category New-download mix and incrementality Existing demand is being compared with demand creation Separate reporting and consider a holdout Many campaigns have no usable evidence Budget fragmentation and duplicated decision rules Structure is more granular than the account can support Consolidate around decisions and markets Maximize Conversions meets install target but payer quality falls Cohort mix and objective alignment Automation is optimizing the stated install outcome, not downstream value Apply an independent value guardrail and reassess fit
Treat each row as a hypothesis, not a diagnosis. Campaign symptoms can originate in the product, App Store listing, attribution layer, or economics—not only in Apple Ads settings.
When the standard structure does not fit
The four-theme framework is less useful when:
the app has too little search demand or budget to support multiple independent campaigns;
Brand and Category terms cannot be evaluated separately with the available evidence;
the product has no stable activation or monetization event;
markets have been fragmented before localization and value differences are understood;
the team cannot maintain search-term routing and negative-keyword hygiene;
the app is pre-order only and the proposed bidding strategy is not eligible;
one generic product page cannot truthfully support the different promises being advertised.
In these cases, reduce structural ambition. Start with a constrained learning design, define what will be learned, preserve a clean control, and expand only when evidence creates a new decision.
A practical 30-day implementation workflow
Days 1–3: define the measurement contract
Choose the business outcome, activation event, market, cohort window, attribution definitions, allowable acquisition range, and stop conditions. Confirm which systems supply download, first-open, activation, payer, revenue, and retention data.
Days 4–7: map intent and destinations
Classify existing keywords and search terms into Brand, Category, Competitor, Discovery, irrelevant, or unresolved. Map each meaningful theme to the default product page or a verified custom product page. Remove claims the product cannot support.
Days 8–10: implement routing controls
For Manage Bids campaigns, separate controlled exact-match themes from broad-match and Search Match discovery. Add exact negatives to prevent known terms from leaking back into Discovery. Preserve a written change record.
Days 11–21: accumulate evidence without constant editing
Monitor delivery, holds, spend, search-term relevance, and measurement integrity. Avoid daily structural changes simply because the dashboard refreshes daily. Allow delayed events to mature according to the chosen cohort window.
Days 22–30: make one level of decision at a time
Promote, continue, exclude, or investigate discovery terms. Compare product-page variants only where the query and traffic justify it. Evaluate acquisition together with activation and value. Consolidate cells that remain too small to support distinct decisions.
The output should be a decision log, not just a cleaner dashboard: what changed, why, what mechanism was expected, what risk was accepted, and how the result will be evaluated.
The operating principle
The best Apple Ads structure is the simplest one that preserves the distinctions your team can measure and act on. Start with intent, give Discovery a controlled routing role, choose bidding automation according to the objective and available evidence, align the product page with the query, and keep installs connected to post-install value.
If your app team is already investing in Apple Ads and cannot tell which structures, search terms, or product pages produce activated users, Sharply Labs can examine the campaign segmentation, overlap controls, creative-to-intent map, and measurement chain. The output is a prioritized diagnostic map of decisions and evidence gaps—not a promise of lower CAC, higher ROAS, or a particular scale outcome. Learn more about our mobile app growth work and integrated growth capabilities.
If the open question is whether Apple Ads should carry the next dollar at all, compare it with automated multi-network delivery in Apple Search Ads vs. Google App Campaigns.