Boost Your App
Please fill in the form below and we'll call you back in no time.

Mistakes in Apple Ads: What They Lead To and How to Fix Them

Paid User Acquisition
Dec 8, 2025

Apple Ads is a powerful tool for promoting apps in the App Store. However, even experienced advertisers often make mistakes that reduce campaign efficiency and lead to overspending.

Below, we’ll explore the most common mistakes, their consequences, and how to fix them.

The most common mistakes

Lack of Competitive and Market Demand Analysis

Understanding your main competitors, the search terms users use, and the problems they’re trying to solve is crucial. Without this insight, your budget may be spent on ads that fail to attract attention or stand out among other brands.

Consequences:

  • Irrelevant traffic — ads appear for non-targeted search terms; potential users don’t install the app or delete it shortly after.
  • Low conversion — the ads don’t match the real interests of your audience.
  • Losing to competitors — other brands better adapt their Apple Ads campaigns to user needs.
  • Budget loss — money is spent on clicks that bring no results.

How to fix it:

  • Research competitors — check who is advertising for your target keywords.
  • Study market demand — gather the most popular search terms in your category and filter out overly generic keywords; they’re usually expensive and rarely bring quality installs.
  • Identify your app’s unique advantages — clarify why users should choose your app and make this the foundation of your ad messaging.
  • Test and optimize — review key metrics regularly, remove underperforming keywords, and experiment with new ad variations.

Relying Only on Search Match as the Main Source of Keywords

Search Match is an automatic targeting mode where Apple determines which keywords to use for showing your ads. Relying solely on this mode can result in ads being shown for irrelevant terms.

Consequences:

  • Budget loss due to showing ads to a non-target audience.
  • Lower conversion rate (CR).
  • Higher cost per install (CPI).

How to fix it:

  • Use manual keyword targeting.
  • Combine Exact Match and Broad Match for better efficiency.

Incorrect Campaign Structure

Many advertisers create a single campaign and add all keywords into it. This leads to chaos and uncontrollable spending.

Consequences:

  1. Budget spent on ineffective search terms.
  2. Difficult to track advertising performance.

 How to fix it:
Break your ads into specific, clearly defined campaigns:

  1. Our brand — keywords containing the name of your app.
  2. Competitors brand — names of competing apps.
  3. Common terms — general terms related to your category.
  4. Discovery — a campaign designed to find new keywords.

Example: If you have a travel app, the term “Google Maps” belongs in the Competitors’ brand campaign, while “travel planner” fits under Common terms.

Ignoring Branded Campaigns and Branded Terms

Sometimes advertisers do not separate branded terms into a dedicated campaign or avoid running defensive ads altogether, assuming their app already ranks high organically.

Branded activity helps retain traffic, control install costs, and prevent competitors from appearing for your branded keywords.

Consequences:

  • You cannot see how many installs come specifically from branded terms. 
  • Loss of control over the budget and bids for branded keywords.
  • Competitors may intercept your traffic by targeting your brand.
  • Hard to manage bids for branded and generic traffic within a single campaign.
  • Inefficient budget allocation increases CPI.

How to fix it:

  •  Create a separate campaign for all search terms containing your app’s name.
  • Use Exact Match to maintain full control over bids.
  • Run brand-defensive campaigns to manage traffic and prevent losing potential users.
  • Expand your semantic coverage — include Broad Match, common misspellings of your brand, and related terms.
  • Allocate sufficient budget to ensure the campaign gets enough impressions to stay competitive.
  • Analyze performance regularly — review results, optimize bids, and add new keywords to maintain efficiency.

Focusing the Budget on a Limited Number of Keywords

Advertisers often spend the majority of their budget on just a select few keywords — mostly branded or generic terms. This approach limits growth and makes campaigns dependent on a narrow pool of search terms.

Consequences:

  • Campaigns become overly dependent on a small set of keywords.
  • Higher risk of sudden CPI increases due to competitive pressure.
  • Missed opportunities for scaling and reaching new audience segments.

How to fix it:

  • Expand your semantics using Discovery campaigns.
  • Add new relevant search terms and test them on a wide sample.
  • Use Exact Match to control the performance of newly added keywords.
  • Gradually move high-performing terms into separate groups for more precise bid optimization.

Overbidding in Brand Protection Campaigns

This approach quickly drives up spending: you may continue winning most auctions, but you’ll pay unnecessarily high prices. Additionally, brand ads can cannibalize organic traffic — users searching for your app by name may click on ads instead of organic results, causing you to pay for installs that would have happened anyway.

Consequences:

  • Inflated CPI and overspending.
  • Organic cannibalization — paying for installs that would have occurred without ads.

How to fix it:

  • Set reasonable bid limits for branded terms based on acceptable CPI or CPA.
  • Analyze the share of organic vs. paid installs for branded search terms to assess and manage the level of cannibalization.

Incorrect Choice of Keywords

Selecting terms that do not accurately reflect the app’s content or core functionality can lead to irrelevant ad impressions.

Consequences:

  • Reduced campaign efficiency due to ads being shown to the wrong audience.
  • Wasted budget on taps that do not convert.

How to fix it:

  • Choose keywords that clearly reflect the app’s features and benefits.
  • Regularly review and update your keyword list to reflect changes in your app or the market.

Failing to Exclude Negative Keywords

Without excluding irrelevant search terms, ads may appear for unrelated searches and reach an untargeted audience.

Consequences:

  • Spending on non-targeted taps.
  • Reduced campaign relevance and effectiveness.

How to fix it:

  • Use Negative Terms to filter out irrelevant terms.
  • Regularly analyze the Search Term Report and add unnecessary search terms to your exclusion list.

Using the Same Keywords in Broad Match and as Negative in Exact Match

Adding a keyword in Broad Match while simultaneously listing it as a negative Exact Match creates conflicts that can prevent your ads from serving correctly.

Consequences:

  • Ads are blocked because irrelevant terms prevent them from showing.
  • Valuable traffic is lost.
  • Statistics are distorted — the campaign may appear ineffective due to configuration conflicts.

How to fix it: 

  1. Check for duplicate keywords in negative lists at both the campaign and ad group levels to avoid conflicts.

  1. Remove negative terms that match or are similar to active keywords in Broad or Exact Match.
  2. Use negative terms only for irrelevant keywords, not to control traffic between match types.
  3. Review the Search Term Report a few days after changes to ensure your desired keywords are being served.

For example, for a paid app, you can add “free” as a negative term to avoid spending budget on users looking for free alternatives.

Turning off Keywords Too Quickly

Gathering sufficient statistics takes time and enough clicks. Pausing a keyword too early may cause you to lose potentially profitable search terms that only required optimization.

Consequences:

  • Premature pausing reduces the number of effective search terms and limits scaling.
  • Potentially profitable search terms may be lost before their performance is fully revealed.
  • The campaign becomes dependent on a small number of stable search terms.

How to fix it:

  • Reduce bids instead of pausing. Almost any search term can become profitable with the right bid level.
  • Set an upper bid limit based on your target CPI and conversion rate (CR).
  • Periodically review results since CR may change over time, and a certain search term can become more effective.

Using Terms Without Checking Current SAP (Search Ads Popularity)

Previously, the SAP (Search Ads Popularity) metric allowed advertisers to estimate search frequency in the App Store and identify high-potential keywords.

In October 2025, Apple updated how this information is displayed. Previously, only dot indicators appeared in the advertising account, while exact numerical values were available via third-party ASO tools.

After the update, Apple introduced a Monthly Search Term Rank Report showing SAP for high-frequency keywords. Meanwhile, third-party tools lost access to detailed SAP values, no longer providing a complete view of term popularity.

As a result, it has become more difficult for advertisers to distinguish between high-traffic terms and low-popularity ones.

Consequences:

  • Minimum impressions — the campaign receives little to no traffic due to low term popularity.
  • Wasted budget — active keywords fail to generate installs.
  • Missed opportunities — resources are spent on low-demand search terms instead of medium- and high-frequency keywords.

How to fix it:

  • Use the Monthly Search Term Rank Report in Apple Ads or third-party tools to assess term popularity.
  • Focus on terms with real impressions.
  • Regularly analyze the report, replacing low-TTR or zero-impression search terms with ones that reliably generate taps and installs.

Not Tracking Terms with Punctuation or Mixed Languages

In Apple Ads, keywords containing punctuation or mixed languages (e.g., English and Chinese) often show low SAP, even when they are relevant.

Consequences:

  • Ignoring these search terms can lead to losing potential users who search with similar combinations.
  • A significant portion of your target audience may be overlooked.

How to fix it:

  • Consider all possible spellings, including punctuation and mixed-language search terms.
  • Add these search terms to campaigns and track their performance, even if SAP is low.
  • To avoid irrelevant impressions, also include negative keywords for similar search terms that don’t match your audience.

Incorrect Bid Settings (CPT Bidding)

Bidding too high or too low directly affects ad impressions and spending.

Consequences:

  • Overbidding — rapid budget depletion without an optimal number of installs.
  • Underbidding — ads barely appear, resulting in few installs.

How to fix it:

  • Use CPT with optimal bids — focus on cost per conversion and ROAS.
  • Test different bid levels and analyze results.

Not Optimizing Bids for Different Keywords

Setting the same bid for all terms without considering their individual performance can lead to inefficient spending and missed opportunities.

Consequences:

  • Overpaying for less effective keywords while missing out on traffic from high-performing ones.

How to fix it:

  • Analyze the performance of each keyword and adjust bids based on their results.

Daily Budget Cap Too Low

The Daily Cap limits daily campaign spending. If set too low, the campaign may exhaust its budget early, causing ads to stop showing.

Consequences:

  • Loss of peak impressions and traffic; the campaign “stops” while competitors continue running.
  • Distorted analytics — data may appear stable, but ads aren’t active for part of the day.
  • Uneven budget distribution.

How to fix it:

  • Check average daily spend. If the Daily Cap equals or is below this, the limit is too strict.
  • Increase the daily budget by 20–30% above average to cover peak hours.
  • Regularly review the cap after changes to bids, keywords, or seasonal traffic patterns.

Not Tracking ROAS / TTR (Tap-Through Rate)

ROAS shows the revenue generated per $1 spent on ads.
TTR indicates ad clickability in Apple Ads.

Many advertisers focus only on CPI, ignoring ROAS and TTR. This can result in cheap installs that don’t generate profit or in misjudging overall campaign effectiveness.

Consequences:

  • Uncertainty about whether ads are generating revenue.
  • High CPI doesn’t always indicate losses — revenue per install must be assessed.
  • Low TTR may signal ad or creative irrelevance.

How to fix it:

  • Track ROAS via analytics platforms (e.g., AppsFlyer, Adjust) to assess profitability per keyword or term group.
  • Optimize TTR — test different creatives, screenshots, and ad copy.
  • Evaluate performance holistically — consider the entire user journey from click to purchase, not just CPI.

Not Monitoring Impression Share (IS) Daily

IS shows the percentage of total potential impressions your ads are receiving. Without regular monitoring, campaigns can silently lose visibility.

Consequences:

  • Reduced visibility in search results.
  • Decreased traffic, installs, or conversions.
  • Delayed optimization decisions — problems may only become apparent after results decline.

How to fix it:

  • Monitor IS trends regularly via Apple Ads reports.
  • Investigate drops to determine whether they are caused by budget limits or ranking issues.
  • Adjust bids and budgets when IS falls due to competition or insufficient funding.

Lack of Analytics

Failing to track essential metrics — conversions, LTV, ROAS, and TTR — leads to a distorted view of campaign performance.

Consequences:

  • Impossible to identify campaigns with positive ROI.
  • Wasted budget on irrelevant traffic.
  • Lack of data for bid adjustments or campaign optimization.

How to fix it:

  • Use an MMP (Mobile Measurement Partner) or SKAdNetwork to collect accurate data.
  • Track the user lifecycle — LTV, Retention Rate, ROAS.
  • Regularly analyze the Search Term Report to optimize keywords.
The graph from Adjust shows the KPI — campaign revenue.

Data Mismatch Between Apple Ads and Analytics Platforms (Mmps)

Installs and performance metrics in Apple Ads often differ from data in third-party analytics platforms like Adjust or AppsFlyer. This is due to differing attribution models: Apple uses its own SKAdNetwork and LAT (Limit Ad Tracking) approach, while MMPs rely on their own tracking methods.

Consequences:

  • Incorrect ROI/ROAS assessment.
  • Optimization decisions based on inaccurate data.
  • Premature pausing of profitable keywords or targeting regions.

How to fix it:

  • Compare data from both sources and understand the differences in attribution.
  • Use SKAdNetwork as the reference for Apple Ads and MMPs for more detailed insights.
  • Explain attribution differences to clients to avoid misinterpretation.

Not Using Custom Product Pages (CPP)

Apple allows creating Custom Product Pages for different audiences, yet many advertisers rely solely on the default page.

Consequences:

  • Low conversion rates due to a mismatch between ads and the landing page.
  • Lost potential users who may not find relevant content.

How to fix it:

  • Create CPPs with unique content tailored to each ad group.
  • Use A/B testing to identify the most effective page versions.

Ranking Cannibalization

This occurs when Apple Ads impressions overlap with organic search results. High-ranking apps may see paid installs cannibalizing what would have been organic installs.

Consequences:

  • Wasted budget — paying for installs that would have occurred organically.
  • Excessive self-competition — higher bids reduce ad efficiency.

How to fix it:

  • Run branded campaigns selectively — only for search terms where competitors are advertising on your brand.
  • Analyze overlap between Apple Ads and ASO — reduce bids or pause ads for high-organic terms.
  • Use SKAdNetwork and MMPs to measure Apple Ads’ true impact on organic installs.

Localization Errors

Incorrect localization significantly reduces campaign performance.

Common mistakes:

  • Using machine translation without verification.
  • Not targeting local search terms used by native users.
  • Ignoring cultural and language nuances.
  • Using universal creatives for all markets without adaptation.

Examples of bad localization: the second, third, and fifth screenshots are not translated.

Consequences:

  • Ads appear unnatural or unclear to local users.
  • Brand communication seems low-quality or untrustworthy.
  • Lost taps and high CPI due to low engagement.
  • Insufficient reach due to irrelevant or unpopular search terms.

How to fix it:

  • Work with native speakers or professional translators to review and refine all localized texts and ad copy.
  • Test multiple localized versions — headlines, descriptions, visuals, and color schemes adapted for each market.
  • Use local keyword research tools that provide market-specific data with country or region filters.
  • Analyze actual search terms in Apple Ads reports and adjust your campaigns accordingly.
  • Study local competitors to understand regional communication styles and adapt yours to fit user expectations.
  • Set up Custom Product Pages (CPPs) to create tailored pages for each market.

Launching Apple Ads in Unsupported Countries

Some countries have their own App Store (e.g., Lithuania), but Apple Ads is not supported. Users in these regions can download the app organically, yet these countries do not appear in the list of locations available for Apple Ads campaigns.

Consequences:

  • Inability to launch campaigns in unsupported countries.
  • Wasted setup time and budget planning risks.

How to fix it:

  • Verify the list of Apple Ads supported countries and target available markets only.

Ignoring Fallback Locales

In some countries (for example, the Dominican Republic, Iraq, or Slovenia), App Store Connect does not provide a dedicated locale. In these cases, the app is displayed using a fallback locale — typically English (US) or English (UK). As a result, both the default product page and any Custom Product Pages (CPPs) will appear in English, regardless of the developer’s preferred localization settings.

Consequences:

  • Lower conversion rates due to a mismatch between the user’s language and the page content.
  • An invalid semantic core — non-English keywords will not trigger ads.
  • Wasted budget on campaigns targeting audiences that cannot see localized content.

How to fix it:

  • Check available target locales in App Store Connect before launching campaigns.
  • Prepare product pages and Apple Ads assets in English when working with fallback locales.
  • Collect semantic search terms in English.
  • Separate fallback-locale countries in reporting to ensure realistic expectations and clearer performance analysis.

Ignoring Apple Ads Rules and Updates

Apple regularly updates its rules, introduces new features, and adjusts algorithms. Ignoring these changes increases the risk of policy violations and puts you at a competitive disadvantage.

Consequences:

  • Ad rejection — causing campaigns to fail and wasting time.
  • Loss of effectiveness, as competitors adopt new features and you fall behind.
  • Analytics inaccuracies when important settings or policy changes are overlooked.

How to fix it:

Expecting High TTR in Search Tab Ads and Today Tab Ads

In Search Tab Ads and Today Tab Ads formats, the TTR (Tap-Through Rate) is typically lower than in standard search campaigns. Users see ads in these App Store tabs but often do not intend to interact with them immediately, resulting in fewer taps.

Many advertisers compare the TTR of Search Tab Ads and Today Tab Ads with standard search campaigns, where users are actively searching for an app. This often leads to the mistaken perception that low TTR indicates poor performance, causing them to prematurely pause campaigns that are actually effective.

Consequences:

  • Campaigns with low TTR are often paused prematurely, even if they generate installs and revenue.
  • A portion of the audience never reaches the install stage, although repeated impressions could have converted them.
  • Overall app visibility in the App Store declines, as Today Tab Ads and Search Tab Ads serve as brand advertising that builds awareness.

How to fix it:

  • Evaluate campaigns based on CPI, conversion rate (CR), and retention rate, not just TTR.
  • Test different visuals to improve user engagement.

Targeting by Age and Gender

Apple Ads settings allow you to set restrictions based on age and gender. But in practice, this often hurts campaign performance. Many users do not share personal data in their Apple ID, so Apple Ads automatically excludes anyone without this information. This results in a significantly narrower audience than intended.

Consequences:

  • Significant audience narrowing, as users without specified age or gender are automatically excluded.
  • Distorted analytics — campaigns may appear ineffective due to artificially limited reach.

How to fix it:

  • Avoid age/gender restrictions.
  • Optimize campaigns using keywords, CPPs, and CR/CPI analysis.

Insufficient ASO Before Apple Ads Launch

Many Apple Ads campaigns are launched before completing proper ASO work. As a result, metadata — including the app title, description, keywords, and visuals (icon, screenshots) — in App Store Connect may not align with the ad. Users may click the ad (resulting in high CTR), but upon visiting the app page, they don’t find what they expected, leading to a low conversion rate (CR).

Consequences:

  • Low CR despite good CTR.
  • Increased CPI.
  • Wasted advertising budget.

How to fix it:

  • Conduct a full ASO audit before launching campaigns.
  • Optimize metadata — title, subtitle, description, and keywords.
  • Update visuals — screenshots and app icon that reinforce ad messaging.
  • Use Custom Product Pages (CPPs) to align the ad experience with the app page.

Ignoring Country-Specific Apple Ads Legal Requirements

Apple Ads enforces specific regulatory requirements in certain countries that go beyond the platform’s standard settings.

In France, advertising is regulated by the Sapin II law, which requires advertisers to ensure transparency and compliance with local regulations. When creating a campaign targeting France in Apple Ads, a special checkbox appears to confirm adherence to these requirements. If this checkbox is not selected, the campaign will not run and will remain in a Not Running status.

In mainland China, campaigns require additional legal approval. Advertisers must upload business documents, such as licenses, permits, or other proof of activity. Campaigns will not run without prior approval.

For more information about launching ads in China, see Apple’s official guide.

Consequences:

  • Campaigns will not start, even if all other settings are correct.
  • Time wasted on official inquiries as to why the ad is not running.

How to fix it:

  • Check local legal requirements before launching campaigns.
  • Follow Apple Ads prompts and instructions for regions with special regulations.

A complete list of country-specific requirements can be found in Apple Advertising Services: Countries and Regions Specific Terms.

Attribute
Value
Format
PNG
Color space
Display P3 (wide-gamut color), sRGB (color), or Gray Gamma 2.2 (grayscale).
See Color Management.
Layers
Flattened with no transparency
Resolution
Shape
Square with no rounded corners
Attribute
Value
Format
PNG
Color space
Display P3 (wide-gamut color), sRGB (color), or Gray Gamma 2.2 (grayscale).
See Color Management.
Layers
Flattened with no transparency
Resolution
Shape
Square with no rounded corners
Word
Frequency in service
Qimai(China)*
AppTweak
Mobileaction
Appfollow
课程 (course)
5387 (high)
56 (mid)
5 (low)
34 (mid)
外语 (foreign language)
5699 (high)
35 (mid)
5 (low)
34(mid)
播放 (play)
5496 (high)
35 (mid)
5 (low)
35 (mid)
*Search index in China provided by Qimai and based on multidimensional calculations such as search results, downloads and relatable keywords.
App Store
Google Play
1. Icon impact on user choice
Important, but not more than a video with screenshots, as they take up most of the screen
Icon is displayed with several other icons in search results, and therefore it has the greatest impact on the user's choice
2. Icon localization
1 icon for all locales
Can be localized for each country
3. Screenshots quantity, orientation
From 1 to 10, any orientation
From 2 to 8, any orientation
4. Screenshots the most important are the ones that are visible before you start scrolling
  • Vertical screenshots: 3 are visible
  • Horizontal screenshots: only the first one is visible
  • Vertical screenshots: 4 are visible
  • Horizontal screenshots: only the first one is visible
5. Screenshots size
Large — the content is legible
Much smaller — the captions are quite illegible
6. Video quantity
Up to 3
One video that must be uploaded to YouTube
7. Video orientation
Any orientation
Horizontal orientation prioritized
8. Video autoplay
Plays automatically for 30 seconds without sound
You need to click on it to play
9. Application cover
Displayed on the application and developer pages
There is no cover
10. Graphics update
After release only
Whenever

Glossary

  1. TTR (Tap-Through Rate): Percentage of users who tap an ad after seeing it.
  2. CR (Conversion Rate): Percentage of users who install the app after tapping an ad.
  3. CPT (Cost per Tap): Cost per ad click (tap).
  4. CPI (Cost per Install): Cost per app install.
  5. CPA (Cost per Action): Cost per user action (registration, purchase, etc.).
  6. SAP (Search Ads Popularity): Metric indicating the popularity of a search term in the App Store.
  7. ROAS (Return on Ad Spend): Profit earned per $1 spent on ads.
  8. ROI (Return on Investment): Overall return on investment.
  9. IS (Impression Share): Percentage of total potential impressions your ad receives.
  10. LTV (Lifetime Value): Revenue a user generates over their lifetime.
  11. MMP (Mobile Measurement Partner): Partner for tracking app installs and user interactions.
  12. CPP (Custom Product Pages): Custom product pages used to test different creatives or audiences.
  13. Retention Rate: Percentage of users returning to the app over a given period.
Device or context
Icon size
iPhone
60x60 pt (180x180 px @3x)
60x60 pt (120x120 px @2x)
iPad Pro
83.5x83.5 pt (167x167 px @2x)
iPad, iPad mini
76x76 pt (152x152 px @2x)
App Store
1024x1024 pt (1024x1024 px @1x)
Source language
Target language
How much longer (+) or shorter (–) the text in the target language is
English
French
21.18%
English
Spanish
19.52%
English
Italian
17.91%
English
Deutsch
16.67%
English
Dutch
13.80%
English
Portuguese (Portugal)
14.29%
English
Portuguese (Brazil)
12.96%
English
Polish
9.33%
English
Russian
9.11%
English
Czech
3.70%
English
Arab
–6.25%
English
Japanese
–39.68%
English
Korean
–44.04%
English
Chinese (Simplified)
–61.97%
English
Chinese (Traditional)
–63.80%
*Search Ads Popularity (SAP)shows the popularity of the search term from 5 to 99.
Device
Spotlight icon size
Settings icon size
Notification icon size
iPhone
40x40 pt (120x120 px @3x)
29x29 pt (87x87 px @3x)
38x38 pt (114x114 px @3x)
40x40 pt (80x80 px @2x)
29x29 pt (58x58 px @2x)
38x38 pt (76x76 px @2x)
iPad Pro, iPad, iPad mini
40x40 pt (80x80 px @2x)
29x29 pt (58x58 px @2x)
38x38 pt (76x76 px @2x)
Search term
Translation
SAP* English (U.S.)
SAP* English (U.K.)
truck games
games with trucks
62
39
lorry games
games with trucks
32
jail games
prison games
29
8
prison games
prison games
32
24
*Search Ads Popularity (SAP)shows the popularity of the search term from 5 to 99.
Google Play
App Store
What can be tested?
  • Short description
  • Long description
  • Icon
  • Feature graphics
  • Screenshots
  • Videos
  • Screenshots
  • Videos
  • Icon (has to be uploaded to the build*)
Number of simultaneously running tests
5 tests (each test is valid within a single country.

You can choose a default country test (details below): then it will run in all countries where there are no localized graphical or textual materials.
1 test (the test can be immediately extended to all countries where the application is available or opt for specific countries as needed)
The number of test variants that can be tested with the current version in the store
Compared with a maximum of 3 new variants
Can a test be launched while another item is under review?
Yes
No
Mandatory formats for screenshots uploaded to the store
6.5
  • 6.5
  • 5.5
  • 12.9 (if there is an iPad version)
*Build – is a new version of the application. Updating the icon is only possible when updating the application version in the store. In other words, the term "build" refers to a specific version or variant of the application that is ready to be downloaded and installed on the users' devices. It contains all the necessary files and data for users to install and use the application.
More about optimizing graphic elements in the App Store and Google Play can be found in the article 'Graphics in Mobile App Promotion in the App Store and Google Play (ASO) – How to Optimize Graphic Elements.'
Device size or platform
Screenshot size
Requirement
Screenshot source
6.5 inch (iPhone 13 Pro Max, iPhone 12 Pro Max, iPhone 11 Pro Max, iPhone 11, iPhone XS Max, iPhone XR)
1284 x 2778 pixels (portrait)2778 x 1284 pixels (landscape)1242 x 2688 pixels (portrait)2688 x 1242 pixels (landscape)
Required if app runs on iPhone
Upload 6.5-inch screenshots
5.8 inch (iPhone 13 Pro, iPhone 13, iPhone 13 mini, iPhone 12 Pro, iPhone 12, iPhone 12 mini, iPhone 11 Pro, iPhone XS, iPhone X)
1170 x 2532 pixels (portrait)2532 x 1170 pixels (landscape)1125 x 2436 pixels (portrait)2436 x 1125 pixels (landscape)1080 x 2340 (portrait)2340 x 1080 (landscape)
Required if app runs on iPhone and 6.5 inch screenshots are not provided
Default: scaled 6.5-inch screenshotsAlternative: upload 5.8-inch screenshots
5.5 inch (iPhone 8 Plus, iPhone 7 Plus, iPhone 6s Plus)
1242 x 2208 pixels (portrait)2208 x 1242 pixels (landscape)
Required if app runs on iPhone
Upload 5.5-inch screenshots
5.5 inch (iPhone 8 Plus, iPhone 7 Plus, iPhone 6s Plus)
2048 x 2732 pixels (portrait)2732 x 2048 pixels (landscape)
Required if app runs on iPad
Upload 12.9-inch iPad Pro (3rd generation) screenshots
5.5 inch (iPhone 8 Plus, iPhone 7 Plus, iPhone 6s Plus)
2048 x 2732 pixels (portrait)2732 x 2048 pixels (landscape)
Required if app runs on iPad
Upload 12.9-inch iPad Pro (2nd generation) screenshots
Price
Traffic Source (Self Reporting Networks)
Facebook
Google
X (Twitter)
Apple Search Ads
Cohort reports
Impression tracking
Audience segmentation
At extra charge
Custom Dashboards
Custom Reports
At extra charge
Advertisement Cost
DAU/MAU (Stickiness)
Raw Data Export
At extra charge
At extra charge
At extra charge
API Reporting
Search term
Translation
SAP* French
SAP* French (Canada)
soldes
sale
25
5
aubainerie
sale
14
*Search Ads Popularity (SAP)shows the popularity of the search term from 5 to 99.
Device
Icon size
iPhone
180px × 180px (60pt × 60pt @3x)
120px × 120px (60pt × 60pt @2x)
iPad Pro
167px × 167px (83.5pt × 83.5pt @2x)
iPad, iPad mini
152px × 152px (76pt × 76pt @2x)
App Store
1024px × 1024px (1024pt × 1024pt @1x)
Icon format
PNG
Color models
sRGB or P3 (see "Color Management")
Layouts
Aligned without transparency
Sizes
Shape
Square without rounded corners
All the current requirements for icons are specified in the specification.
Icon format
32-bit PNG (with alpha channel)
Color models
512 х 512 pixels
Layouts
1024 КБ
Sizes
square, without rounding and shadows (Google automatically rounds the corners and adds shadows)
All the current requirements are specified in the specification.

Traffic
Popularity
Keyword
1
385 585
99
instagram
2
325 480
98
whatsapp
3
201 485
95
telegram
4
177 737
94
facebook
5
119 067
91
tik tok
6
92 427
90
ifood
7
80 473
87
tinder
8
69 379
87
capcut
9
65 120
87
nubank
10
64 602
86
uber

Traffic
Popularity
Keyword
Translate (EN)
1
233 158
99
snapchat
snapchat
2
209 668
98
instagram
instagram
3
114 577
94
tik tok
tik tok
4
92 500
93
telegram
telegram
5
70 286
91
facebook
facebook
6
59 302
90
tinder
tinder
7
51 352
89
whatsapp
whatsapp
8
42 468
87
youtube
youtube
9
36 646
86
tiktok
tiktok
10
36 420
86
messenger
messenger

Traffic
Popularity
Keyword
Translate (EN)
1
243 626
99
instagram
instagram
2
122 131
95
snapchat
snapchat
3
74 161
91
tik tok
tik tok
4
67 431
91
whatsapp
whatsapp
5
55 634
89
reddit
reddit
6
40 775
87
youtube
youtube
7
39 319
87
tinder
tinder
8
37 889
87
facebook
facebook
9
37 600
86
telegram
telegram
10
26 225
84
brawl stars
brawl stars

Traffic
Popularity
Keyword
1
123 159
99
instagram
2
91 584
97
snapchat
3
52 253
93
facebook
4
28 524
89
tik tok
5
25 788
88
reddit
6
23 972
88
youtube
7
23 005
88
tinder
8
20 257
87
whatsapp
9
17 652
86
messenger
10
14 431
84
discord

Traffic
Popularity
Keyword
Translate (EN)
1
96 271
99
인스타그램
Instagram
2
66 339
97
vpn
vpn
3
47 883
94
카카오톡
KakaoTalk
4
40 069
93
유튜브
YouTube
5
39 041
93
배달의민족
Delivery ethnicity
6
33 538
92
x
x
7
32 794
92
트위터
Twitter
8
29 047
90
쿠팡플레이
Coupang Play
9
21 262
89
네이버
Naver
10
18 882
88
티빙
Tibing

Traffic
Popularity
Keyword
1
144 520
99
instagram
2
102 720
97
snapchat
3
70 760
94
facebook
4
45 775
91
tik tok
5
26 665
88
youtube
6
25 880
87
reddit
7
24 777
87
tinder
8
21 923
86
whatsapp
9
21 702
86
messenger
10
15 312
84
spotify

Traffic
Popularity
Keyword
Translate (EN)
1
38 906
98
телеграм
telegram
2
24 281
95
telegram
telegram
3
20 773
93
бравл старс
brawl stars
4
17 750
91
пабг
YouTube
5
16 308
91
дія
Delivery ethnicity
6
15 075
91
tik tok
x
7
12 534
90
instagram
Twitter
8
11 554
89
вайбер
viber
9
11 418
89
brawl stars
brawl stars
10
11 205
89
viber
viber
Home
Up