US city testing when a state-level location is enough
Choose between US city and state-level proxy tests using the actual rule your site applies. Record requested and observed location separately.

Buying city-level traffic can add cost without improving a test. A state-level eligibility notice and a shop locator near a specific neighborhood have different geographic requirements. Decide which decision the customer is asking the site to make.
Choose the smallest useful geography
For a state-wide campaign on your own site, select fixtures on opposite sides of the state boundary and record the expected outcome. For a store locator, explicitly identify the postal area and branch. An IP-based location estimate may point to a nearby metro even when the connection belongs to the intended state. BrowserStack documentation on IP geolocation.
Record disagreement instead of averaging it away
Compare the location requested from XtremeProxy with the region your application actually used. If the two disagree, inspect the application’s location source and fallback path. A pass means the intended behavior occurred under an understood location signal. A test that merely displays a city name has not established that the business rule used that city.
For a state-rule test, a pair of exits in different cities within the same state provides an additional control. Both should receive the same approved state treatment if city does not enter the rule. A difference between them gives the application team a narrower investigation.
A statewide rule and a city-specific delivery promise
A fictional store shows the same product advice throughout Colorado but offers same-day delivery only near one depot. A state-level network check can exercise the first rule. The second also needs the merchant's service-area boundary and an approved delivery postcode. Compare two test postcodes on opposite sides of that boundary while holding the network constant. Purchasing city-level targeting cannot compensate for an application that makes the decision from the supplied delivery address.
Tie precision to the customer's decision
A test concerning a state banner needs reliable state classification. A same-day delivery promise requires the actual service-area rule, which may depend on a postcode or selected depot. Record uncertainty if location databases disagree. More specific ordering language cannot make a backend use a different decision input.
Use a pair of test locations that cross the policy boundary in the requirement. A state-level rule is best tested on opposite sides of that state boundary. Two cities within the same state exercise consistency within it. A city-specific delivery rule needs the merchant’s supported address or zone fixture as well.
Measure the rule at its actual boundary
Pick an approved pair of neighboring postcodes that receive different delivery treatment according to the merchant's service map. Use the same regional route and basket for both. If eligibility flips with the postcode, the shop is sensitive to that business boundary. The observation does not establish street-level geographic precision of the exit address.
Inspect the location classification used by the application itself. A test provider may label an exit with a city while the merchant's own routing service recognizes only a state or assigns a neighboring city. Check the state decision in the merchant's authorized diagnostic record for the same synthetic request. If the observed state is correct and the feature reads only that state field, the exact city label adds little to the finding. Save the application's evaluated field with the visible response.
A metropolitan area can straddle more than one state. If a release brief names the metro area and the production rule reads state, use approved fixtures from each state rather than treating the metro label as one jurisdiction. Keep the merchant's defined state outcome and the central city used in marketing as different fields. If the two sides intentionally receive different offers, a report grouped only by metro will make a correct split appear inconsistent. The comparison belongs at the rule's actual level.
Related fieldwork
Give the buyer the smallest geographic requirement that can reproduce the business rule and document any postal or store inputs the test also needs. Dealer locator territory assignments illustrates territory assignment on a locator. Country, city and ASN targeting in a proxy order explains how city, country and network-operator labels describe distinct properties of an order. Compare XtremeProxy network types.
Frequently asked questions
When should a US test specify a metropolitan area?
Specify the finer area when the application behavior or approved acceptance rule depends on it and the provider can document the relevant granularity. Preserve the actual source of the location decision used by the application.


