Argentina proxies
In most countries collecting prices is a question of breadth. In Argentina it is a question of freshness: price tags get rewritten often, and a week-old snapshot here is a memory rather than data. The second thing almost everyone trips over: Buenos Aires is two different places, and confusing them in your data is expensive.
What we have in Argentina
Prices are the same as in every other country we cover.
What Argentine addresses get used for
Frequent price monitoring
Mercado Libre, Frávega, Coto, Carrefour AR, Jumbo: price tags move far more often than in Europe and need a denser pass.
Property and cars
Zonaprop, Argenprop, DeMotores: local platforms that serve something else from outside the country.
Local search and SEO
google.com.ar: results are their own set, and the vocabulary is Argentine, so Mexican lists do not transfer.
Ad verification
Clarín, La Nación, Infobae: campaigns are bought for the local audience and do not render for a foreign address.
What looks different from outside Argentina
These serve an Argentine visitor something other than what a foreign one sees, because of broadcast rights and local catalogues. We sell addresses rather than a way past detection.
Which type to take for an Argentine job
Cities people ask for here
Cities are set with the _city_ suffix. The capital region outweighs the rest, but Córdoba, Rosario and Mendoza resolve reliably.
The setups people take here most often
- 01Residential on a dense scheduleThe default: frequency matters more than the number of targets.
- 02A fifty minute sticky sessionWhen a job has to run start to finish on one address.
- 03Mobile addressApps and platforms expecting a carrier.
- 04City and province apartThe federal capital and the province are kept separate in the data rather than merged.
Connection strings for Argentina
The country code is AR, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Argentine addresses come through rotation and sticky sessions, with the lifetime set by the ttl suffix.
Argentine exits, four ways
curl -x login_c_AR:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# the federal capital and the province, which are not the same market
curl -x login_c_AR_city_Buenos-Aires_s_42_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
curl -x login_c_AR_city_La-Plata_s_43_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# held for fifty minutes, for a job that must not change address
curl -x login_c_AR_s_44_ttl_50m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# with the language header that matches the market
curl -H "Accept-Language: es-AR" -x login_c_AR:password@proxy.sotaproxy.com:10000 https://api.ipify.orgPrices here have a short shelf life
The main difference between collecting Argentina and collecting Europe, and it is about scheduling rather than access.
Price tags are rewritten far more often here than in countries with a stable currency. The practical conclusion is unwelcome for anyone used to measuring work by breadth: a week-old snapshot stops describing the market. You can still compare it against today, but the conclusion will be about time rather than about the product.
That reverses the priority. In Argentina it is better to collect fewer items more often than more items once a week. A thousand key listings daily is worth more than twenty thousand every seven days.
Then come the requirements on the data itself. Every record needs a collection timestamp rather than only a date. Averaging a price over a month is meaningless here and hides the movement. Compare periods on matching days and hours, or what you are measuring is your scraper’s schedule rather than the market.
One last thing: if your pipeline caches pages, shorten the cache lifetime. What saves traffic in Germany will quietly substitute yesterday’s prices for today’s here.
Buenos Aires is two different places
The second feature, and it breaks the data rather than the collection.
Two distinct units carry that name: the autonomous city and the province surrounding it. These are not a district and its outskirts but separate administrative entities with their own rules, logistics and delivery terms. Shops treat them separately.
The mistake shows up when data is joined: city and province collapse into one row because the text on the page says the same word. After that prices and delivery times mix, and the divergence looks like collection noise.
The rule: separate them explicitly on intake. Go by the region in the exit’s geodata rather than the name in the page text, and keep it as its own field on the record.
The same applies to targeting. A request for the capital and a request for a point in the province produce different conditions on many platforms, so if that spread is what interests you, collect two points rather than one.
What actually blocks you on Argentine targets
The familiar split.
Marketplaces and the large chains filter server ranges and expect a home address: that means residential.
Publishers and government sites serve requests calmly.
Apps and the platforms grown out of them sometimes expect a carrier address: that is where mobile helps.
Search results are reachable but rate limited per address: more addresses rather than a different type. On a dense schedule that limit arrives sooner than it would on a sparse one.
Which exits you get here, and how stable they are
The Argentine pool in practical terms.
The pool is decent: a country of over forty million people, with enough addresses for a dense schedule, which matters more here than elsewhere.
The capital region outweighs the rest, but Córdoba, Rosario and Mendoza resolve reliably, so regional slices are possible.
Line quality varies: fast in the large cities, slower in the distant provinces. Do not shorten the thirty second timeout.
Sticky sessions hold an address for up to fifty minutes, and mobile rotates by physical reconnect: seconds rather than milliseconds, and the same address sometimes comes back.
Choosing the type for an Argentine target
A short order, because there are two types.
- Start with country-level residential: it passes on marketplaces and retail, and you pay only for the gigabytes you pull.
- Plan frequency before breadth: on this market that is the main budget decision.
- If a job has to run on one address, add a sticky session with a lifetime.
- If the target is an app and residential runs into a check, try a mobile address.
- A 429 on a dense schedule is a per-address rate limit: more addresses rather than a sparser pass.
What Argentine sites check beyond the address
An Argentine address opens the first gate; language and number parsing decide the rest.
Send es-AR. Argentine Spanish differs noticeably from both the European and the Mexican varieties: different address pronouns, different verb forms, different everyday vocabulary. Keyword lists from Mexico transfer about as badly as Spanish ones.
The number format is continental: 1.299,90, a dot for thousands and a comma for decimals. That is the opposite of Mexico, so one parser shared across both markets will almost certainly break on one of them.
Some platforms display two prices in different currencies side by side. Record which one you captured as its own field: without that, comparing your own records against each other is meaningless.
The time zone is UTC-3 with no daylight saving, and it is the same across the country.
What a month of Argentine work costs
Three scenarios at our prices, so you have something to check a quote against.
- A dense pass, 5,000 key listings three times a day with images blocked, roughly 110 KB per page. That is about 1.65 GB a day, around 50 GB a month: $50 on residential.
- The same budget spent on one wide pass gives you more rows and less value: on this market frequency costs more than breadth.
- Capital and province as two points add volume only in the categories where the conditions genuinely differ.
The legal part, stated plainly
Argentina is not in the European Union, and GDPR does not apply here directly. Its own personal data protection law does, with its own regulator, and collecting data that identifies people in Argentina is governed by it regardless of where your company sits.
This is general information rather than legal advice. Our terms require lawful use and we act on abuse reports. Where the answer carries commercial risk, ask a lawyer.
Verifying an Argentine exit
Under a minute. The second command is the main one here: it shows that the capital and the province really are giving you different regions.
Three checks
# 1. is the exit Argentine, and where
curl -s -x login_c_AR:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# 2. capital against province, which must not be merged
curl -s -x login_c_AR_city_Buenos-Aires:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json | grep -i region
curl -s -x login_c_AR_city_La-Plata:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json | grep -i region
# 3. does the fifty minute session hold
for i in 1 2 3; do
curl -s -x login_c_AR_s_42_ttl_50m:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
doneQuestions people ask before buying Argentine addresses
How often should prices be collected here?
More often than in Europe. Price tags are rewritten far faster, so a thousand listings daily is worth more than twenty thousand once a week.
Can I average a price over a month?
No, that hides the movement. Keep a collection timestamp and compare matching days and hours.
What is the difference between the city and the province of Buenos Aires?
They are separate administrative units with different logistics and delivery terms. Separate them explicitly in the data, going by the exit region rather than the name in the page text.
Will Mexican keywords work?
Poorly. Argentine Spanish differs in vocabulary and verb forms alike. Build the list separately and send es-AR.
Why is my price parser wrong?
It is most likely set up for the Mexican format. Here it is a dot for thousands and a comma for decimals, the other way round.
Do Argentine addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, mobile from $5.76 per day.