The ads are running, the budget is being spent, and the impressions are increasing in the dashboard — but you don’t see the ad either on Instagram or TikTok on your phone. This is a familiar situation for any arbitrage specialist. The reason is almost always the same: you are viewing from a different IP, a different device, and a different geo-zone than the target audience. In this article, we will discuss how to correctly test in-app ad displays through mobile IP addresses to ensure that the creative is genuinely reaching the user and not getting lost somewhere between moderation and the display algorithm.
Why test in-app displays at all
Arbitrage specialists who drive traffic to Facebook Ads, TikTok Ads, and Google Ads regularly encounter situations where the statistics in the ad dashboard are increasing, but the actual impressions of the creative are not visible "in the field." This is especially critical for in-app placements — ad blocks within the applications themselves like Instagram, TikTok, Facebook, YouTube, rather than in a mobile browser. The algorithms of these platforms generate the output based on many factors: geo, device, mobile operator, account behavior history, IP address. If you check impressions from a desktop via a regular Wi-Fi IP from a data center, the system may simply not show you the ad because you "do not resemble" the target audience based on formal criteria.
Testing in-app displays is necessary for several reasons. First, to ensure that the creative has passed moderation and is genuinely running, rather than being stuck in "under review" status despite the campaign appearing active. Second, to verify the accuracy of geo-targeting — it often happens that a campaign is set for the USA, but the impressions are predominantly shown in Canada or the UK due to auction peculiarities. Third, to assess how the ad appears on different devices and in different versions of the app — the banner layout may break on older Android versions or very small screens. And finally, to promptly notice "gray" patterns — for example, when the platform is spending the budget, but there are almost no real impressions for the target audience.
For SMM agencies managing client ad accounts, such checks are also important from a reporting perspective: the client wants to see that the ads are genuinely working in the region and format that were agreed upon.
How in-app ads differ from the web version
Many arbitrage specialists habitually test ads through a browser on a desktop, opening the mobile version of the site or emulating a mobile User-Agent. This is a gross mistake when working with in-app placements. Facebook, Instagram, TikTok, and YouTube generate ad output within their own applications differently than in the web version — they have different ad ranking algorithms, different formats (Stories, Reels, In-Feed, Rewarded Video), and different sensitivities to device parameters.
Within the app, the system analyzes the combination of IP address, mobile operator, device model, OS version, and behavioral signals of the account. If you open the TikTok app on a phone connected to office Wi-Fi with a data center IP, the platform may detect the mismatch of "mobile traffic — non-mobile IP" and show you a completely different set of ads than a real user on mobile internet in the same city. Therefore, for an honest test of in-app displays, you need to replicate the most similar conditions: a mobile device (or emulator with the correct parameters), the installed app, and an IP address that looks like real mobile internet from a mobile operator, not like a server.
A separate challenge is testing in different countries. If the campaign is set for Germany, and you are physically in another country, the only way to see the actual in-app output is to connect through the IP of a German mobile operator. Without this, you will either not see the necessary ads at all, or you will see a version adapted to your real geo.
Why mobile proxies are needed for testing
The main reason to use mobile IPs for testing in-app displays is the trust that platforms have in mobile operator networks. Facebook, TikTok, and Google see millions of real users accessing the app specifically from the IPs of mobile operators — MTS, Beeline, Vodafone, T-Mobile, and dozens of others worldwide. These IP addresses are used simultaneously by thousands of different people (CGNAT technology), so the platforms do not consider them suspicious and do not impose additional display restrictions on them.
If you use a data center IP instead, the algorithm is likely to detect atypical behavior: a mobile app but a server IP — this signals a bot or emulator, which often leads to reduced ad output, shadow account restrictions, or even blocking when entering the app. Residential proxies are closer to real conditions than data center ones, but they still represent IPs from home providers, not mobile operators — for most arbitrage tasks, this is sufficient, but specifically for in-app tests, mobile IPs provide the most accurate picture, as they replicate the exact profile of a mobile user.
Arbitrage specialists working with Facebook Ads and TikTok Ads often choose mobile proxies not only for account farming but also specifically for quality control of impressions — to see the ads just as a real user with a phone sees them.
Comparison of proxy types for ad testing
To choose the right tool for the task, it is useful to compare the three main types of proxies based on key parameters that are particularly important for in-app testing.
| Proxy Type | Suitable for in-app testing | Risk of atypical display | Speed |
|---|---|---|---|
| Data Center Proxies | No | High | High |
| Residential Proxies | Partially | Medium | Medium |
| Mobile Proxies | Yes, optimal | Minimal | Medium |
Data center proxies are good for mass scraping of pages from the Facebook Ads Library or checking banners on websites, but for in-app displays within a mobile application, they almost always lead to distorted or completely empty ad output. Residential proxies are suitable if you need to check how ads are displayed in a mobile browser or the web version of the app, but for a full test within the app itself, it is better to use mobile IPs — they signal to the platform "this is a real mobile user," which is critical for obtaining honest ad output.
Step-by-step setup for testing via anti-detect browser
For a correct test of in-app displays, it is recommended to use a combination of an anti-detect browser or mobile device emulator and a mobile proxy with the required geolocation. Let's break down the process using popular tools — Dolphin Anty, AdsPower, and GoLogin, which arbitrage specialists already use for farming and managing ad accounts.
Step 1. Create a separate profile for testing. Do not use your main working account from which the campaign is running — create a new clean profile or use a test account not linked to the ad account. This will protect the main account from unnecessary behavioral signals.
Step 2. Set up the mobile device fingerprint. In Dolphin Anty or AdsPower, select the mobile device parameters in the profile settings: phone model, Android or iOS version, screen resolution. This is important because platforms check the device parameters against the type of IP — if the fingerprint is desktop, and the IP is mobile, this also raises suspicion.
Step 3. Connect a mobile proxy with the required geo. In the proxy settings section of the profile, specify the protocol (usually SOCKS5 or HTTP), server address, port, username, and password from your mobile proxy provider. It is important to choose the country and, if possible, the mobile operator that corresponds to the targeting of your ad campaign.
Step 4. Check the IP before launching. Open any IP checking service in the profile and ensure that it identifies as a mobile operator from the required country, not a data center or residential provider. This can be done directly within the built-in browser of the anti-detect tool.
Step 5. Install and open the target app. If testing impressions through a real mobile device or Android emulator, install the official Instagram, TikTok, or Facebook app and log in with the test account. Scroll through the feed, Stories, or Reels for a few minutes — the algorithm needs time to start showing ads tailored to the new IP and geo.
Step 6. Record the results. Take screenshots or screen recordings of the displayed ads, noting the time, geo, and device. If the desired creative does not appear within 15-20 minutes of active scrolling, repeat the test with another IP from the same region — sometimes it’s not about blocking, but about the peculiarities of ad rotation within the auction.
Step 7. Repeat the test on several IPs. One successful impression does not guarantee stability — test at least 3-5 different mobile IPs in the target region to assess the actual reach and frequency of your creative.
Checklist before starting the test
Before spending time on testing, ensure that the basic conditions are met — this will save hours of wasted time and budget.
- A separate test account is used, not linked to the working ad account
- The mobile proxy corresponds to the country and, preferably, the mobile operator from the campaign targeting
- The device fingerprint in the anti-detect browser is set as mobile, not desktop
- The campaign in the ad account is active and has passed moderation (status "Active," not "In review")
- The campaign budget is not restricted so narrowly that there are physically too few impressions for testing
- The test is conducted at different times of the day, as the algorithm distributes impressions unevenly
- For each geo, at least 3-5 different IPs are checked, not just one
Common mistakes when testing impressions
The first and most common mistake is testing through regular home or office Wi-Fi without any proxy at all, hoping that "well, I’ll try from my phone." If your real IP does not match the geo of the campaign targeting, you will physically not see the ad because the system simply does not show it outside the selected region.
The second mistake is using data center proxies for in-app testing "for speed." Yes, such proxies are faster and cheaper, but platforms like TikTok and Instagram can recognize server IP ranges and either do not show ads at all or serve an atypical set of ads that are not related to the real output for live users.
The third mistake is testing for too short a duration. After scrolling through the feed for 30 seconds and not seeing the desired creative, many conclude "the ad is not showing" and start to panic, although the algorithm may need 10-20 minutes of activity in the app and even several sessions at different times to include your traffic in the target output.
The fourth mistake is testing from the same IP for too long and too frequently. If you constantly enter the app from one mobile proxy and scroll through the feed without real interaction (likes, comments, watching videos to the end), the behavioral profile of the account may appear suspicious to the system, distorting the test itself.
The fifth mistake is confusing visual verification of the creative with checking the effectiveness of the campaign. Even if you see your ad in the feed, it does not automatically mean a good CTR or conversion — the in-app display test solves a narrow task: to confirm that the ad is technically reaching the target audience in the required format and geo, rather than evaluating the marketing effectiveness of the creative as a whole.
Conclusion and recommendations
Testing in-app displays is a straightforward but essential procedure for any arbitrage specialist or SMM professional who wants to be sure that the advertising budget is not being wasted. The main rule is to replicate the conditions of a real mobile user: a mobile device fingerprint, the installed app, and an IP address that the platform recognizes as part of the mobile network, not a server or home range.
If you regularly launch campaigns in Facebook Ads, TikTok Ads, or Google Ads and want to control how ads actually look inside apps in different countries, we recommend trying mobile proxies — they provide the most accurate picture of in-app output thanks to IPs from real mobile operators. For related tasks, such as checking web versions of landing pages or scraping ad libraries, you can additionally use residential proxies, and for less trust-sensitive platforms — fast and affordable data center proxies.