An offer page opens in the wrong language. A colleague sees a different landing page. A redirect works on a laptop but fails inside a browser profile. These are familiar campaign QA problems, and changing several settings at once usually makes them harder to explain.
A short connection check gives you a starting point. It helps you separate a network observation from an assumption about the offer, browser or tracking setup. The aim is a repeatable test you can share with a teammate, not a score that promises anonymity or campaign acceptance.
1. Define the experience you want to check
Before opening the campaign URL, write down the expected country, device category and landing-page language. Note whether you are checking the creative, redirect chain, page layout or a specific tracking event. Use the test or preview method agreed with the advertiser; avoid creating real orders or conversions just to see what happens.
Keep the environment identifiable. A label such as “English desktop QA, profile B” is more useful than “the other browser.” Record the browser version, operating system and whether a proxy or VPN is configured. Do not put passwords, access tokens or private customer details in the test log.
2. Why does my IP location look wrong in this browser profile?
Open WHOER's IP lookup in the same browser profile that will run the campaign check. Record the visible public IP, reported country and network or ISP information. A check in a separate browser might use a different connection and therefore tell you little about the campaign environment.
Treat IP location as an estimate. Different databases can assign different locations to the same address, and a city label is not proof of a person's physical position. Likewise, a proxy dashboard's selected country describes the requested configuration; the browser check shows what that particular request actually used.
For example, suppose you select Germany for a regional landing-page review but the browser reports another country. First confirm that the intended profile uses the intended proxy. If the public IP is correct but the country labels disagree, record both results and ask the provider about that specific address. Replacing every browser setting would hide useful evidence.
3. Look at DNS separately
DNS resolves a domain name to an address. The resolver used for a lookup is a different observation from the public IP used to reach a web page. A browser's secure DNS setting, operating-system configuration or network service can influence the resolver you see.
Run the available DNS check and record the resolver results alongside the public IP. An unfamiliar resolver, or one labeled in another country, does not by itself prove a leak. Public resolver networks can serve users in many locations, and location labels are imperfect. What matters is whether the observed behavior matches the connection's documented setup and your privacy requirements.
If you need a second view of browser-exposed information, WHOER's free tools directory links to additional diagnostic services. Compare like-for-like observations and note which tool produced each result. Do not turn several unrelated indicators into a single unsupported verdict.
4. Separate browser preferences from network location
An IP change does not automatically change a browser's language, time zone, stored site preferences or previously granted location permissions. These signals can explain why two people with similar network locations see different content.
Browser geolocation is also distinct from an IP database lookup. When a site requests location access, the browser asks for permission and can use the device's available location capabilities. A proxy does not automatically replace that device location. Check the existing permission setting without granting location access merely to make a test “pass.”
Imagine an English-language offer displaying a different language even though the IP country is expected. Compare the browser language and the site's saved preference before changing the proxy. A remembered language cookie or account preference may be the relevant difference. Keep an untouched baseline profile so that you can compare the result after a deliberate change.
5. Change one variable, then repeat
Once the baseline is recorded, reproduce the issue with the same URL and test steps. Change only the setting connected to your hypothesis, then repeat the check. Useful comparisons include:
• The same browser profile before and after applying its intended proxy configuration.
• The same connection with the site's saved language preference changed.
• The same page in an agreed clean QA profile, without unrelated extensions.
• The same test at a later time, with the visible IP checked again.
If the connection rotates addresses, record the IP for each test rather than assuming it stayed constant. A successful first request does not establish how the rest of a session behaved. For a failed redirect, note the step and time of failure, not just that “the proxy did not work.”
6. Make the handoff useful
A teammate should be able to understand what happened without asking you to reconstruct the session from memory. A compact record can include:
• Date, time and time zone.
• Environment label and browser version.
• Expected experience and the actual result.
• Visible IP, reported country and resolver observations.
• The single setting changed between attempts.
• A screenshot of the relevant result, with credentials and personal data removed.
Keep sensitive evidence in the team's approved private location. Before sharing a tracking URL, remove personal identifiers and secret tokens; use a test URL when possible. If redaction prevents reproduction, agree on a secure way to provide the necessary information rather than posting it publicly.
A repeatable check beats a perfect-looking score
Connection diagnostics describe observations at a particular time. They cannot guarantee account eligibility, conversion attribution, acceptance by an advertiser or invisibility to a website. A matching country label is useful evidence, but it does not verify every part of a campaign setup.
The practical habit is simple: define the expected experience, check from the correct environment, separate IP and DNS observations from browser preferences, and record one change at a time. That gives affiliates a clearer conversation with developers, providers and account managers—and a much better starting point for the next QA run.
Using this checklist with a CIPIAI offer
Let’s use a TikTok Shop US preview to see what to check and which details your manager will need. What if TikTok Shop US opens an unexpected page?
- With the US proxy selected, open WHOER in the same browser profile as the preview. Record the country WHOER reports.
- If WHOER shows the US, send your CIPIAI manager offer ID, the final domain and path, your device and the test time with its time zone. Ask which page the advertiser expects.
FAQ
WHOER shows a different country from my proxy provider. What should I record?
Run WHOER in the browser profile you use for the offer preview. Note the time, the public IP WHOER sees, the country it reports and the country you selected with your provider. If the provider lists an exit IP, compare the two addresses. When they match but the country labels differ, send both readings to the provider.
How can I check which language a first-time visitor sees?
Ask the advertiser which language to expect for the country and device you’re testing. Open the preview in a fresh browser profile with the intended browser language and connection. Record the language on the first page before touching the site’s language menu.
Can WHOER tell me why my preview opened a different offer?
WHOER reports the country it associates with the IP address it sees. Ask your account manager whether the route can be checked for that preview. Send the preview ID, the time with its time zone, and the expected and actual destinations. Include a test click ID if the preview generated one.
My DNS resolver shows another country. Should I change it?
A country label alone gives you too little information to justify a change. If the test calls for a specific resolver, compare the resolver IP and provider shown in the DNS check you used with the provider’s documented setup.