---
title: "Ask visitors for their precise location"
description: "A new Location request workflow step asks visitors to share their precise location. If they agree in their browser, the latitude, longitude and accuracy are recorded and the workflow goes on along a Location shared branch; otherwise it takes Not shared. On every plan."
canonical: "https://linkbreakers.com/help/article/ask-visitors-for-their-precise-location"
last-updated: 2026-10-28
---

# Ask visitors for their precise location

> A new Location request workflow step asks visitors to share their precise location. If they agree in their browser, the latitude, longitude and accuracy are recorded and the workflow goes on along a Location shared branch; otherwise it takes Not shared. On every plan.

## Short answer

Workflows have a new step: **Location request**. It shows the visitor a page asking them to share their precise location, and only when they tap the button does the browser ask for permission. If they agree, the latitude, longitude and accuracy their device reports are recorded and the workflow continues on **Location shared**. If they refuse, skip, or the device cannot give a position, it continues on **Not shared**. It is available on every plan. See [how to ask for a visitor's precise location](/help/article/how-to-ask-for-a-visitors-precise-location).

## What we shipped

Until now, the location of a scan came only from the IP address: a country, a region and usually a city. That is still how every scan is located by default. The Location request step adds precise location for the links where you ask for it, and only for visitors who agree.

### A page that asks first

In the workflow editor's interaction steps, choose **Location request**. You set a title, a description and a button label ("Share my location" by default). The page uses your page theme and has a back button like other pages. The browser's permission prompt only appears after the visitor taps your button, so you get to explain why you ask before they are asked. The description is the place for it.

### Two branches

- **Location shared**: the visitor agreed. The step records the latitude, longitude and accuracy (in meters).
- **Not shared**: the visitor refused in the browser, the device could not give a position (no GPS, timeout, unsupported, page not secure), or they pressed the optional skip button. The skip button never triggers the browser prompt.

Both branches can lead to the same next step or to different ones. A branch left unconnected falls back to the link's fallback destination, like other steps.

When a visitor's browser already allows location for the link's site, the position is read without showing the page, on every visit. Turn on **Ask only once per device** and a device that has shared on that step goes on along **Location shared** on later visits without being asked or captured again.

### Where it shows

- Each visit's activity timeline shows "Location Shared" (or "Location Refused", "Location Skipped", "Location Unavailable", "Location Already Shared") with the coordinates, the accuracy and a Google Maps link.
- Slack notifications show the same.
- Webhooks carry it in the visit journey.
- With the step's save to visitor profile option, `{{location.latitude}}`, `{{location.longitude}}` and `{{location.accuracy}}` can be saved on the visitor's profile, then used in visitor data conditions and CSV exports of visitors.

### In the API, MCP and the Assistant

Create the step with the event action `EVENT_ACTION_LOCATION_REQUEST` and a `location_request` payload (`title`, `description`, `button_label`, `skip_enabled`, `skip_label`, `ask_once`). Connect its `location` and `else` branches with `workflow_steps_connect` or the connect endpoint. The Assistant can add it for you too.

## Frequently asked questions

### Does every scan now record GPS?

No. Without the step, scan location is approximate and comes from the IP address, as before. Precise location is only recorded on links with a Location request step, and only when the visitor agrees in their browser.

### Can visitors say no?

Yes. They can refuse the browser prompt, press the skip button if you show one, or later withdraw the permission in their browser settings. The workflow then continues on **Not shared**.

### Which plans include it?

Every plan.

### Is there a map of scans?

No. Coordinates appear in the activity timeline with a Google Maps link, in Slack notifications, in webhooks and, if you save them, on visitor profiles and in visitor exports. There is no map, heat map or analytics widget for coordinates.

### Does it work on every link?

Browsers only offer location on secure (https) pages, and all Linkbreakers links are https.