Anchor Browser geo routing uses lowercase country_code - each session gets its own residential IP
Anchor Browser geo routing uses lowercase country_code - each session gets its own residential IP: For geo-targeted scraping on Anchor Browser, pass the country as a lowercase ISO code: anchor.sessions.create(proxy={'active': True, 'country_code': 'de'}, ...).
For geo-targeted scraping on Anchor Browser, pass the country as a lowercase ISO code: anchor.sessions.create(proxy={'active': True, 'countrycode': 'de'}, ...). The official example uses lowercase codes (us, de, au, gb, sg) - do not send uppercase. Each session gets its own residential IP and fingerprint, so firing parallel sessions across regions with asyncio.gather gives you per-region snapshots that look like separate visitors. Set idletimeout low (30s) on geo jobs since each region holds its own session, and stop sessions in a finally block or you stack up billing.
Context: Official Anchor Browser blog (Geo-Targeted Price Monitoring): set countrycode to any ISO 3166-1 alpha-2 code and Anchor routes the session through a residential IP in that country - the worked example uses lowercase codes (REGIONS = ['us', 'de', 'au', 'gb', 'sg']) passed as proxy={'active': True, 'countrycode': country_code}. Each parallel session gets its own isolated context, IP, and fingerprint via asyncio.gather, so geo comparison jobs look like separate visitors.
Matched source
Source: Source: https://anchorbrowser.io/blog/geo-targeted-price-monitoring-anchor-vpn-python Original query: "Anchor Browser geo routing uses lowercase country_code - each session gets its own residential IP" Key terms: anchor, browser, code, country, each, gets, lowercase, residential, routing, session, uses
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.