Web Profiles

Location and geolocation

Where the request appears to come from, and what the page is told when it asks the browser where you are. Two separate settings that people frequently confuse.

Location

Location is in the Basics section of the Web Profile form, and every profile needs one. It routes the capture through that country, so the site sees a visitor from there. Everything that follows from the visitor’s country follows automatically: the currency, the language variant, the regional home page, the legal notices, the products actually on sale.

Each entry shows its flag, ISO code and country name. A new profile starts on the first entry in the list, which is the United States.

Available countries

The list offers the countries we can capture from today, out of these eighteen. A country that is not offered at the moment is left out of the list rather than failing your captures later.

A profile used by a sitemap schedule needs a location with dedicated proxies; the form warns you when the one you pick has none.

US — United StatesGB — United KingdomDE — GermanyFR — FranceIT — ItalyES — SpainNL — NetherlandsBE — BelgiumPL — PolandSE — SwedenCA — CanadaBR — BrazilIN — IndiaSG — SingaporeHK — Hong KongJP — JapanKR — South KoreaAU — Australia

One country per profile

A profile captures from one location. To watch the same page from four markets, make four profiles and four schedules — which is also what gives you four separate, comparable archives.

Geolocation

Open Geolocation under Fine-tuning and switch on Report a position to the page. The fields below it are the coordinates the browser reports when the page calls the geolocation API — the same prompt a visitor answers with “Allow”.

Field	Type	Default	Description
`Latitude`Required	Number	—	−90 to 90, to six decimal places.
`Longitude`Required	Number	—	−180 to 180, to six decimal places.
`Accuracy (metres)`	Number	100	How precise the browser says the position is, 1 to 10,000 metres. Leave it empty for 100 m; a site that only acts on a tight fix (a store locator, a delivery radius) may need a smaller value.

This matters for anything that asks where you are standing rather than which country you are in: a store locator, delivery availability, a map that centres on the visitor, local search results.

The two are not the same

Location is the network route. The site infers your country from the address the request arrives on. Every site sees it, whether or not it asks.
Geolocation is a browser answer. Only a page that actually calls the geolocation API sees it, and only if it would have prompted a real visitor.

Set both when you are testing a specific place

Coordinates in Munich with the location left at the United States is a combination no real visitor produces, and some sites will handle it in ways you would not expect. Match the two.

What people use this for

Geo-targeted pricing — the same product page from six markets, daily, to see what each is actually being shown.
Proving a campaign ran where it should — a dated capture from inside the country, rather than a screenshot from your own desk.
Checking a regional redirect — confirming a visitor from Japan lands on the Japanese site rather than a broken country picker.
Compliance per market — capturing the notices, disclaimers and consent flows a given jurisdiction requires.

Did this page answer your question?

Tell us what is missing