What changes the page?
A coarse city, the local hour, a forecast, and a landmark from a built-in set. The panel names which of those signals were actually present.
Last updated
A coarse city, the local hour, a forecast, and a landmark from a built-in set. The panel names which of those signals were actually present.
Only after you opt in. The point is snapped to a one-mile cell before it is sent. It is used for that response and not stored.
No. If the request carries one, the panel says it was ignored.
Compare a straight-line radius with a drive-time shape for the same point. That gap is why delivery zones and local ads miss on a circle. Nothing is stored.
Same page, five people, plus you. Each card names the signals and the rule that changed the hero, the offer, and the notes. Tweaks stay in this browser.
The signals used to measure a visit can also change the page.
Geo page
A page shaped by place. The same layout reads a coarse city, the local hour, the weather, and a nearby landmark. The panel under the map names the signals that wrote it.
Why you'd want to
The page can be shaped from the request headers, a labeled sample, or a browser point snapped to a cell. Weather and landmarks fill in for that point, and this lab queues no event of its own.
How to use it
The page is using the coarse place already on this request for Columbus. A precise point was not asked for.
Map data © OpenStreetMap contributors. Landmarks are a built-in teaching set.
The request version uses Vercel’s IP headers, rounded to two decimals. A browser point is snapped to a one-mile cell before it is sent, and it is not stored.
Every value that could have changed the page is listed. A postal code on the request is ignored. Nothing in this table is stored.
| Signal | Value | Use | Why |
|---|---|---|---|
| x-vercel-ip-city | Columbus | Used | Used to write this version of the page. |
| x-vercel-ip-country-region | OH | Used | Used to write this version of the page. |
| x-vercel-ip-country | US | Used | Used to write this version of the page. |
| x-vercel-ip-timezone | America/New_York | Used | Used to write this version of the page. |
| x-vercel-ip-latitude | 39.96 | Used | Rounded to two decimals before the forecast. |
| x-vercel-ip-longitude | -83.00 | Used | Rounded to two decimals before the forecast. |
| x-vercel-ip-postal-code | present | Ignored | A postal code can be on the request. This page does not read it into the layout. |
| browser geolocation | — | Absent | Not shared. |
Open-Meteo https://api.open-meteo.com/v1/forecast?latitude=39.96&longitude=-83.00¤t=temperature_2m%2Cweather_code%2Cis_day%2Cprecipitation%2Cwind_speed_10m&daily=weather_code%2Ctemperature_2m_max%2Ctemperature_2m_min%2Cprecipitation_probability_max%2Cuv_index_max%2Csnowfall_sum&temperature_unit=fahrenheit&wind_speed_unit=mph&timezone=auto&forecast_days=1
The headers are already there. The browser point waits for a yes.
// Coarse place from the request. A postal code is ignored.
const city = request.headers.get("x-vercel-ip-city")
const timezone = request.headers.get("x-vercel-ip-timezone")
const latitude = Number(request.headers.get("x-vercel-ip-latitude"))
const longitude = Number(request.headers.get("x-vercel-ip-longitude"))
const point = Number.isFinite(latitude) && Number.isFinite(longitude)
? { latitude: latitude.toFixed(2), longitude: longitude.toFixed(2) }
: null
// A browser point is a second step, and only after a yes.
const cell = consent === "opt-in" ? snap(browser.latitude, browser.longitude) : nullExample vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The geo page builds a view from request headers, a labeled sample, or a browser point snapped to a cell, and fills weather and landmarks for that point without queueing its own event. The lab does not call Adobe.
Read the coarse edge place
readEdgePlace decodes the city, region, country, and timezone headers. Coordinates are rounded to two decimals and dropped when they are out of range. A postal code is recorded as present or absent and is not returned as a value.
Choose sample, browser, or request
buildGeoView in sample mode uses the Portland sample point. Browser mode snaps a consented point to a one-mile cell and ignores the IP point except for the city, and the timezone when the browser has none. Otherwise it uses the edge place.
Ask for weather and landmarks
weatherFor calls the same forecast helper as the weather lab and returns unavailable when that call fails. landmarksFor uses the built-in landmark set. The view sets stored to false.
Reload from the browser only after a yes
The client load function asks for geolocation, snaps the point, and fetches /api/lab/geo. The section is marked data-track-ignore. This component does not call trackLabEvent.
Reading path transitions…
Headers become a coarse place. The postal code is a flag, not a returned value.
export function readEdgePlace(source: HeaderSource): EdgePlace {
const latitude = headerNumber(source.get("x-vercel-ip-latitude"))
const longitude = headerNumber(source.get("x-vercel-ip-longitude"))
const roundedLat = latitude != null ? roundPlaces(latitude, 2) : null
const roundedLng = longitude != null ? roundPlaces(longitude, 2) : null
const pointOk = roundedLat != null && roundedLng != null && coordinatesInRange(roundedLat, roundedLng)
return {
city: decodePlace(source.get("x-vercel-ip-city")),
region: decodePlace(source.get("x-vercel-ip-country-region")),
country: decodePlace(source.get("x-vercel-ip-country")),
timezone: decodePlace(source.get("x-vercel-ip-timezone")),
latitude: pointOk ? roundedLat : null,
longitude: pointOk ? roundedLng : null,
postalPresent: Boolean(decodePlace(source.get("x-vercel-ip-postal-code"))),
}
}Sample mode ignores the live point and uses the labeled sample.
export async function buildGeoView(input: {
source: HeaderSource
mode: "request" | "browser" | "sample"
browser?: { latitude: number; longitude: number; timezone: string | null } | null
now?: Date
}): Promise<GeoView> {
const edge = readEdgePlace(input.source)
const now = input.now ?? new Date()
const browserPoint =
input.mode === "browser" && input.browser && coordinatesInRange(input.browser.latitude, input.browser.longitude)
? snapToCell(input.browser.latitude, input.browser.longitude)
: null
if (input.mode === "sample") {
const zone = safeTimeZone(SAMPLE_EDGE.timezone)
const place = landmarksFor(SAMPLE_EDGE.latitude!, SAMPLE_EDGE.longitude!)
const weather = await weatherFor(SAMPLE_EDGE.latitude!, SAMPLE_EDGE.longitude!)
return {This lab does not queue its own event. The Google block shows an example of how you would track the interaction. Adobe is an example too.
This lab does not queue an analytics event of its own. After Accept, the site still queues virtual_page_view for the page, with page_path and page_title. Clicks inside a data-track-ignore region are not recorded. The push below is an example, not a call this page makes. This site does not call gtag('set') or Adobe.
Example only. This page does not push this object.
// Example only. This lab does not queue this event.
dataLayer.push({
event: "geo_page_view_example",
place_mode: "request",
})Example implementation. This site does not call Adobe. eVar74, prop74, and event74 are example variable numbers. In Launch, a data element reads the value and a rule sends it when the value changes. In the report suite, enable eVar74 with Most Recent allocation and expire it on the hit. A processing rule is unnecessary if the data element maps straight to that eVar.
Example alloy payload. _example is a placeholder schema, not a real tenant.
alloy("sendEvent", {
xdm: {
eventType: "web.webinteraction.linkClicks",
_example: {
geoPlace: "request",
},Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Place mode
GA4. Not sent. geo_page_view_example is a fake name. The view’s mode stays on the page.
Adobe. Example eVar74, expire on the hit. Not sent.
Scope. A view state for this hit. It is not a user property and it does not last for the visit. It is an event on the hit, not a user property, and it does not last for the visit.
City
GA4. Not sent.
Adobe. Example prop74. Not sent.
Scope. Shown on the hit. Do not copy the city onto the user for the visit. It is an event on the hit, not a user property, and it does not last for the visit.
Postal code
GA4. Not sent. The signal is ignored or absent.
Adobe. Example eVar74 must not hold a postal code. Not sent.
Scope. Not an event, not a user property, and not a hit or visit value.
Browser point
GA4. Not sent. It is snapped to a cell and the view says stored is false.
Adobe. Example prop74. Not sent.
Scope. Used for this hit after a yes. It is not a user property and it is not kept for the visit. It is an event on the hit, not a user property, and it does not last for the visit.
Example hit. eVar74 is hit-scoped in this example. prop74 dies at the same hit.
s.eVar74 = "request"
s.prop74 = "request"
s.events = "event74"
s.linkTrackVars = "eVar74,prop74,events"
s.linkTrackEvents = "event74"
s.tl(true, "o", "geo_page_view_example")