---
title: "How to ask for a visitor's precise location"
description: "Get the GPS location of a QR code scan, with the visitor's permission: a Location request step asks them to share it, their browser asks for consent, and the latitude, longitude and accuracy are recorded on the visit. Refused or skipped visits take another branch. On every plan."
canonical: "https://linkbreakers.com/help/article/how-to-ask-for-a-visitors-precise-location"
last-updated: 2026-11-09
---

# How to ask for a visitor's precise location

> Get the GPS location of a QR code scan, with the visitor's permission: a Location request step asks them to share it, their browser asks for consent, and the latitude, longitude and accuracy are recorded on the visit. Refused or skipped visits take another branch. On every plan.

![The Location request page a visitor sees after scanning: "Share your location", a short reason, a Share my location button and a Skip button](/screenshots/location-request-visitor-page.jpg)

## Short answer

A QR code scan normally tells you only the city it came from, guessed from the phone's internet address. To know **where exactly** someone scanned (the GPS position of the phone, to the meter accuracy the phone reports), you have to ask them, and their browser asks for their permission. In Linkbreakers you do that with a **[Location request](/workflow-steps/location-request)** step in the link's workflow: the visitor sees a page with your reason and a "Share my location" button, the browser shows its own prompt only after they tap it, and if they agree the latitude, longitude and accuracy in meters are recorded on the visit. If they refuse, skip, or the phone cannot find its position, the visit goes on along another branch, so nobody is stuck.

What you end up with: for the people who agree, the real spot of the scan next to the rest of the visit, on a map in your dashboard, in Slack and in your webhooks, and saved on the visitor's profile if you want it there. You can see which poster, van or store window was scanned where, and send a visitor to the store nearest to them. It is available on every plan, and it never runs without the visitor's consent.

:::try-ai-prompt {"prompt":"Add a Location request step before the redirect that asks visitors to share their location so we can show the nearest store. Send people who share to the store finder and everyone else to the main website.","description":"Try adding a Location request step with the AI builder."}:::

## How location sharing works in a browser

Before Linkbreakers, the mechanism itself, because it explains everything the step can and cannot do.

### Two kinds of scan location

- **Approximate location, from the IP address.** Every device online has an IP address, the number that identifies its internet connection. Databases map IP addresses to places, so any website can guess a visitor's country, region and usually city without asking. It is often wrong at street level, and a VPN or a mobile network can move it to another city. This is what every QR code tool, Linkbreakers included, records on every scan. See [does a QR code show location? Accuracy limits and examples](https://linkbreakers.com/help/article/does-a-qr-code-show-location-accuracy-limits-and-examples).
- **Precise location, from the device.** Browsers have a standard feature, the Geolocation API, that lets a web page ask the phone where it is. The phone works it out from GPS satellites and from nearby Wi-Fi networks and cell towers, and returns a **latitude and longitude** (the two numbers that pin a point on a map, the ones you can paste into Google Maps) plus an **accuracy**, a radius in meters around that point.

### What the visitor sees

A web page cannot read the precise location on its own. When it asks, the browser shows its own permission prompt, asking whether the site may use your current location, with an Allow and a Don't Allow choice (the exact wording depends on the browser and the phone). Nothing is shared unless the person agrees. A few rules come with it:

- **Secure pages only.** Browsers only offer location on https pages. All Linkbreakers links are https.
- **Refusing is final for that request.** The page is simply told "denied" and gets no position. Depending on the browser and the answer, the browser may remember the choice for that site, and the person can change it later in the browser's settings.
- **Already allowed.** If the person allowed location for that site before, the browser can give the position again without a new prompt.
- **Accuracy varies.** Outdoors with GPS the radius is usually small; indoors, or on a laptop with only Wi-Fi, it can be much wider. The accuracy figure tells you which case you are in, so you can trust a 10 meter reading and treat a 2 kilometer one as "somewhere in this area".

### Why ask with a page first

If a page triggers the browser prompt the moment it opens, people refuse without knowing why they were asked. Showing a short reason first ("so we can show you the nearest store") and a button that the visitor taps when they are ready gives them the context before the browser asks. That is how the Location request step works.

## How to set it up in Linkbreakers

A **workflow** is the chain of steps a visit goes through between the scan and the final destination ([what is a workflow](https://linkbreakers.com/help/article/what-is-a-workflow-in-linkbreakers-and-how-it-powers-automation)). The Location request step is one of its interaction steps: a page the visitor sees, with two **branches** (two possible ways out) depending on the answer.

1. Go to [Links](https://app.linkbreakers.com/workspace/dashboard/links) and open the QR code or link. Its workflow opens.
2. Click the **+** button on the connector where you want to ask, for example between the scan and the destination.
3. In the interaction steps, choose **Location request** ("Ask visitors to share their precise location, with their permission").
4. Fill in the step:
   - **Title**: the heading of the page, "Share your location" by default (up to 120 characters).
   - **Description** (optional): tell visitors why you ask, for example to show the nearest store (up to 500 characters). This is where you earn the "yes".
   - **Button label**: the button that asks the browser, "Share my location" by default.
   - **Show a skip button**: adds a second button that takes the **Not shared** branch without asking the browser. Set its text in **Skip label** ("Skip" by default).
   - **Ask only once per device**: see below.
5. Click **Create Location Request**. When you insert it on an existing connector, both branches lead to the step that came next, so the visit carries on as before whatever the visitor chooses.
6. To send the two outcomes to different places, connect the **Location shared** branch and the **Not shared** branch to the steps you want.
7. Scan the code with your phone to check both paths: once sharing, once refusing or skipping.

The page uses your [page theme](https://linkbreakers.com/help/article/whats-a-page-theme) and has a back button like other pages.

## How each branch behaves

### Location shared

The visitor tapped the button and agreed in the browser prompt. The step asks the browser for its most precise reading, waits up to 15 seconds for it, and accepts a position the phone found in the last minute so a returning visitor is not kept waiting. It records the latitude, longitude and accuracy (in meters), then the workflow continues on the **Location shared** branch.

### Not shared

This is the step's else branch. The workflow continues on it when:

- the visitor refuses in the browser prompt,
- the device cannot give a position within 15 seconds, for example no GPS fix, a browser that does not support it, or a page that is not secure,
- the visitor presses the skip button.

### Unconnected branches

A branch that is not connected to anything sends the visitor to the link's [fallback destination](https://linkbreakers.com/help/article/what-is-a-fallback-destination-in-linkbreakers), the page a visit lands on when no step says where to go next.

### When the browser already allows location

If the visitor's browser already allows location for the link's site, the position is read without showing the page. This happens on every visit, so a returning visitor who allowed it before goes straight on along **Location shared**, with a fresh position.

## Ask only once per device

With **Ask only once per device** turned on, a device that has shared its location on that step is not asked again. Later visits from the same device go on along **Location shared** without being asked, and the location is not captured again. Turn it off if you want a fresh position on every visit.

## What is saved, and where you see it

Every Location request records an outcome on the visit: "Location Shared", "Location Refused", "Location Skipped", "Location Unavailable" or "Location Already Shared". A shared position adds the latitude, the longitude and the accuracy.

- **Activity timeline**: each visit shows the outcome, with the coordinates, the accuracy and a Google Maps link to the exact spot. This is the same timeline as the [QR code scan history](https://linkbreakers.com/help/article/is-there-a-qr-scan-history) and [who scanned your QR code](https://linkbreakers.com/help/article/how-do-i-track-who-scanned-my-qr-code).
- **[Slack notifications](https://linkbreakers.com/help/article/linkbreakers-slack-integration-qr-scan-notifications-for-your-team)**: the same details appear in the scan notification, so your team sees where someone scanned as it happens.
- **[Webhooks](https://linkbreakers.com/help/article/how-do-webhooks-work-in-linkbreakers)**: the outcome and coordinates are part of the visit journey your server receives.
- **Analytics dashboards**: the **Shared locations** map widget plots the positions (see below).
- **Google Analytics 4**: if you [connected GA4](https://linkbreakers.com/help/article/google-analytics-4-integration-for-qr-codes-and-links), a shared position also sends a `location_shared` event.
- **Visitor profile**: switch on [save to visitor profile](https://linkbreakers.com/help/article/how-to-save-visitor-data-from-any-workflow-step) on the step. It starts with the latitude and longitude saved as numbers (`{{location.latitude}}`, `{{location.longitude}}`), and you can add `{{location.accuracy}}`. Saved values stay on the [visitor](https://linkbreakers.com/help/article/what-is-a-visitor-in-qr-analytics-and-why-it-matters) across visits, appear in CSV exports of visitors, and can be used in [visitor data conditions](https://linkbreakers.com/help/article/how-to-use-visitor-data-conditions), which compare numbers (greater than, less than), for example to treat a returning visitor differently when their saved latitude falls inside your area.

The country, region and city in the rest of your analytics still come from the IP address, for every scan, including the ones where nobody shared a position. To route by country without asking anything, use [country conditions](https://linkbreakers.com/help/article/how-to-use-country-conditions).

## See shared positions on a map

Once at least one visitor has shared their position, your analytics dashboards offer a **Shared locations** widget: a map with a marker for every position shared through a Location request step.

- **Adding it**: a dashboard you can edit shows an **Add map** banner as soon as someone has shared a position, on the workspace dashboard and on the dashboard of a link with this step. You can also ask the Assistant on the dashboard ("add a map of the locations visitors shared"). The widget is never part of a new dashboard's starter set, and neither the banner nor the Assistant suggests it while nobody has shared.
- **Reading it**: the map opens zoomed on the positions. Nearby positions are grouped into one marker showing how many it holds, and they split apart as you zoom in. Hover a single marker to see its coordinates, the accuracy the device reported and when it was shared.
- **Filters**: the widget follows the dashboard's date range and its link, directory, tag and country filters. On a link's dashboard it only shows that link.
- **Empty periods**: when no visitor shared a position in the selected period, the widget says so instead of drawing an empty map.
- **How many**: the map draws the 2,000 most recent positions in the period.

## What you can do with it

- **Send people to the nearest store.** Ask on a poster or a flyer, then send those who share to your store finder and everyone else to your main site, and see on the map where the people who wanted a store were standing.
- **Know which placement works, to the street.** A QR code on a delivery van, a bus shelter or a set of shop windows: the IP city says "Lyon"; shared positions show which street corner and which side of town the scans actually come from, so the next print run goes where people scan.
- **Check where products are scanned.** On packaging, shared positions show where your product is actually being scanned, beyond the country the IP address gives. For scans by product and country without asking, see [how to track QR code scans by product and country](https://linkbreakers.com/help/article/how-to-track-qr-code-scans-by-product-and-country).

In each case you get a position only from the visitors who agree, and the rest still give you the IP-based city.

## With the API, MCP and the Assistant

The step can be created like any other workflow step through the [Linkbreakers API](https://linkbreakers.com/help/article/how-to-use-the-linkbreakers-api), the [MCP server](https://linkbreakers.com/help/article/mcp-server-setup) or the Assistant.

- Event action: `EVENT_ACTION_LOCATION_REQUEST`
- Payload: `location_request` with `title`, `description`, `button_label`, `skip_enabled`, `skip_label` and `ask_once`
- Branches: `location` (Location shared) and `else` (Not shared), connected with the `workflow_steps_connect` MCP tool or the connect endpoint
- Shared positions: `GET /v1/analytics/shared-locations` (MCP and Assistant tool `analytics_shared_locations`) returns them newest first, with latitude, longitude, accuracy in meters, time and link, plus the total count. It takes the same date range and link, directory, tag and country filters as the other analytics endpoints, and up to 2,000 positions per call. Without dates it covers all time, so `limit=1` tells you whether anyone has shared a position.

## Privacy and consent

- Precise location is only ever collected when the visitor agrees in their browser. Linkbreakers never reads it any other way, and never on links without this step.
- Visitors can refuse the prompt, use the skip button if you show one, or later withdraw the permission in their browser settings.
- You, the business that owns the link, decide to ask. Say why in the description, and cover precise location in your own privacy notice. See [what GDPR means for your links](https://linkbreakers.com/help/article/what-is-gdpr-and-how-does-linkbreakers-handle-it) and [is Linkbreakers GDPR compliant](https://linkbreakers.com/help/article/is-linkbreakers-gdpr-compliant).
- The Linkbreakers [Privacy Statement](https://linkbreakers.com/privacy) describes precise location shared with permission.

## Limits and caveats

- Browsers only offer location on secure (https) pages. All Linkbreakers links are https.
- The accuracy depends on the device and where it is. The step records the accuracy the device reports, so you can tell a precise fix from a rough one.
- Some visitors will refuse or skip. Make sure the **Not shared** branch leads somewhere useful, and expect your map to show part of your scans, not all of them.
- The step adds a page, so it adds a tap before the destination. Ask only where the position is worth that tap.
- With **Ask only once per device**, later visits from that device do not update the position.
- The **Shared locations** map draws the 2,000 most recent positions in the selected period. There is no heat map.

## Frequently asked questions

### Can a QR code get the GPS location of the person who scans it?

Only if they agree. A QR code is just a link; the page it opens can ask the browser for the phone's position, and the browser asks the person. With a Location request step, Linkbreakers records the latitude, longitude and accuracy for those who agree.

### Does Linkbreakers now collect GPS on every scan?

No. Scan location is still approximate and IP-based by default. Precise location is only recorded on links with a Location request step, and only when the visitor agrees in their browser.

### What happens if the visitor says no?

The workflow continues on the **Not shared** branch. If you leave it unconnected, the visitor goes to the link's fallback destination.

### Can visitors skip without seeing the browser prompt?

Yes, if you turn on **Show a skip button**. Skipping takes the **Not shared** branch and never triggers the browser prompt.

### How precise is the location?

As precise as the phone can tell at that moment. The browser reports an accuracy radius in meters with every position, and Linkbreakers records it: small outdoors with GPS, wider indoors or on Wi-Fi only.

### Is the Location request step on every plan?

Yes. It is available on every plan.

### Can I see the shared positions on a map?

Yes. Add the **Shared locations** widget to an analytics dashboard, from the **Add map** banner or by asking the Assistant. It is offered once at least one visitor has shared a position.

### Can I route visitors by their coordinates?

Inside the step, the routing is by the answer: **Location shared** or **Not shared**. To use the coordinates themselves, save them on the visitor's profile with the step's save to visitor profile option, then compare them in [visitor data conditions](/workflow-steps/visitor-data-condition).

## Next steps

- [Save visitor data from any workflow step](https://linkbreakers.com/help/article/how-to-save-visitor-data-from-any-workflow-step), to keep the coordinates on the visitor.
- [Use visitor data conditions](https://linkbreakers.com/help/article/how-to-use-visitor-data-conditions), to act on what you saved.
- [How to track location from QR code scans](https://linkbreakers.com/help/article/how-to-track-location-from-qr-code-scans), for everything you learn about location without asking.

## Sources

- Linkbreakers Location request step, editor, visitor page and API, checked in the product and its code on 2026-11-09.
- Linkbreakers Shared locations dashboard widget, added on 2026-11-03.
- W3C, Geolocation specification (sources of location, accuracy in meters): https://www.w3.org/TR/geolocation/
- MDN Web Docs, Geolocation API: https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API
- MDN Web Docs, secure contexts: https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts

## Last reviewed

2026-11-09 by Laurent Schaffner.
