USE CASES
Cross-border commerce
The same product page can be two prices, two stock states and two promotions depending on where you look from. You want the buyer’s copy.
Why it has to be residential
Commerce sites compute price, availability and placement per visitor region, and the exit IP is the first input to that. Datacenter IPs are often treated as non-buyers and served a cached or default-region page — you get data, just not the data you asked for.
Target the city
Shipping, tax and delivery ranges vary by state and often by city. Selecting only a country hands you a random city in that country, mixing location drift into your daily numbers until the trend is unreadable.
The console targets country, state and city; pin one city per monitored target.
Run at the same local time
Promotions start and end on local time. Half an hour of drift in your schedule shows up as a step in the price curve that looks like a discount. Convert the schedule to the target market’s local time and then leave it alone.
- One SKU, one exit IP, one city
- Record the target time zone timestamp, not just server time
- Store the currency code — exchange rates are the biggest confounder in cross-border comparison