AdPilot MCP
Sign in
Browse documentation
Last reviewed

Apple Ads guide

Apple Ads (formerly Apple Search Ads) helps app teams reach customers while they are using the App Store. The best setup connects placement, audience intent, product-page message, bid, budget, and post-install value instead of treating campaigns as isolated traffic sources.

Choose a placement for the job

Apple Ads Advanced supports four App Store placements:

Placement Where it appears Typical job
Today tab The App Store front page Broad visibility and major launches
Search tab The suggested apps area before a search Reach people beginning discovery
Search results Above relevant App Store search results Capture explicit keyword intent
Product pages — while browsing On other App Store product pages Reach people comparing related apps

Eligibility and available creative options can vary by app category, country, or region. Start with the placement that matches the user’s stage. Search results are usually the clearest learning environment for a small team because search terms expose intent and support keyword-level decisions.

Understand the account hierarchy

Apple Ads reporting and controls follow a hierarchy:

  1. Organization and campaign group — access, billing context, currency, and account-level organization.
  2. Campaign — promoted app, placement, countries or regions, budget, schedule, and status.
  3. Ad group — audience settings, default max CPT bid, schedule, Search Match, and CPA goal where supported.
  4. Keyword — search results targeting with exact or broad match and an optional keyword-level bid.
  5. Search term — the query that actually produced an impression, tap, or install.
  6. Negative keyword — a rule preventing unwanted matching at campaign or ad-group level.

Campaign settings create the exposure envelope. Ad groups and keywords determine which demand can enter it. Search terms provide evidence about what customers actually wanted.

Align targeting with real product availability

Campaign countries should reflect where the app is distributed, localized, supported, and economically viable. A country with cheap installs is not attractive if onboarding is untranslated, pricing is unsuitable, or the service cannot deliver its core benefit there.

At ad-group level, customer type, device, age, gender, and location refinements can narrow delivery. Narrowing can improve relevance but can also reduce reach and slow learning. Use restrictions when they express a real product or experiment requirement, not simply because the option exists.

Separate countries when they need independent budgets, language strategy, or value assumptions. Group similar markets when volume is limited and the shared setup is genuinely comparable.

Treat bids and budgets as different controls

A max CPT bid is the maximum you are willing to pay for a tap. It affects auction competitiveness but is not a guaranteed tap price. An ad-group default bid applies unless a keyword-level bid overrides it.

A campaign daily budget controls potential daily spend. It is not the same as actual spend, and it is not a substitute for a profitability target. Raising a budget gives a campaign more room; raising a bid changes how aggressively it can compete.

Use these questions before changing either:

  • Is the campaign constrained by demand, rank, bid, audience, or budget?
  • Are high-intent terms losing volume while low-value terms consume spend?
  • Does current CPI or payer value support more exposure?
  • Would a product-page or targeting problem remain after a higher bid?
  • What is the maximum monthly exposure if the new daily budget is fully used?

AdPilot calculates spend projections and enforces workspace and confirmed app limits before eligible direct operations. Read Direct operations, limits, and audit before enabling writes.

Match the product page to the promise

Apple builds ads from approved App Store metadata and assets. Weak positioning cannot be repaired only with bid changes.

For search results, ad variations can use custom product pages to present screenshots and messaging aligned with an intent theme. A finance app might show a budgeting-focused page for “expense tracker” searches and a subscription-management page for another theme. The landing experience should still describe the real product accurately.

Product page optimization tests the default page. Custom product pages create alternative destinations for specific audiences or messages. They solve related but different problems.

Read performance as a funnel

Review delivery in order:

  1. Impressions — did Apple find eligible opportunities?
  2. TTR — did the ad and intent earn taps?
  3. Conversion rate — did the App Store experience produce installs?
  4. CPI or CPA — what did each attributed install cost?
  5. Activation, payer CAC, and ROAS — did installs become valuable customers?

A low-impression keyword may need more demand, broader coverage, or a competitive bid. High impressions with weak TTR usually call for a relevance or creative review. Strong TTR with weak conversion points toward the product page, audience promise, price, ratings, or product fit.

Use Apple Ads metrics and formulas for exact definitions and denominator rules.

Worked example: diagnose before bidding

Two ad groups each spend $300:

Ad group Impressions Taps Installs TTR Conversion CPI
Budgeting intent 12,000 720 180 6.0% 25.0% $1.67
Generic finance 30,000 600 60 2.0% 10.0% $5.00

The second ad group has delivery, so a higher bid is not the first answer. Its weaker TTR and conversion suggest less relevant intent or a mismatch between the search, ad, and product page. Review search terms and the landing promise before paying more for the same traffic.

How AdPilot uses Apple Ads data

AdPilot synchronizes organizations, campaigns, ad groups, keywords, negative keywords, search terms, and complete-day metrics. It maps campaigns to the app you configured, so your assistant can analyze structure and performance in the correct product context.

Read-only tools can explain serving state, budgets, countries, bids, mappings, and performance. Eligible write tools can create or update supported entities after workspace scoping, correctness validation, plan checks, and spend-limit enforcement. Every attempted operation receives an action ID and audit history.

Try: Explain why this app is under-delivering. Check serving state, budget, bids, countries, search-term coverage, and conversion evidence before recommending a change.

Setup checklist

  • Confirm the app and product page are ready in each target country.
  • Choose a placement and audience stage deliberately.
  • Separate budgets where markets or goals require independent control.
  • Define a bid rationale and profitability guardrail.
  • Map Apple campaigns to the correct AdPilot app.
  • Sync complete-day metrics before diagnosing performance.
  • Review search terms and product-page alignment before scaling.
  • Record meaningful changes and evaluate them over a comparable period.

Next steps

Official sources

Need help with AdPilot MCP?

Contact support at support@kovacssoftware.com

AdPilot is an independent service and is not affiliated with, endorsed by, sponsored by, or operated by Apple Inc. Apple and Apple Ads are trademarks of Apple Inc.