Respondent Location (Geo Tagging)
Respondent Location captures a respondent’s browser-reported device location once, at the start of a survey response—before they see the first question.
Use it when you need place context on the response itself (catchment checks, regional fieldwork, in-person or on-site studies), not when you need someone to answer a map question. For pin-drop or draw-on-map answers, use Interactive Map instead.
Location is treated as personal information (PII). Coordinates and reverse-geocoded place fields follow the same view / export / clear controls as other respondent identity metadata.
Note
Browser location is reported by the device and browser. It is useful evidence of approximate place—not cryptographically verified proof that someone is physically standing at those coordinates.
Open Respondent Location settings
Open your survey in the Survey Builder.
Click Tools in the top bar, then Respondent Location.
Choose a Tracking mode, adjust consent and capture settings, then click Save.
New surveys default to Off—respondents are never prompted until you turn capture on.
Tracking modes
| Mode | What happens |
|---|---|
| Off | No consent screen, no browser permission prompt, no location stored. |
| Optional | Respondents see a consent step. They can allow location, or continue without it. Declines, denials, and capture failures still let them proceed into the survey. |
| Required | Respondents may continue only after a passing capture (accuracy—and any configured area rules—must pass). Declining, denying permission, or exhausting retries ends the response through the normal Screened Out termination flow. |
In required mode, the decline button reads Decline and exit. In optional mode it reads Continue without location.
Consent message
Before Quali-Fi asks the browser for location, respondents see your Consent message and must choose Allow location (or decline / continue without).
- Edit the message in Tools → Respondent Location.
- The modal shows a Respondent preview of the live copy.
- Default message explains that location may be stored with the response and treated as personal information.
Quali-Fi does not call the browser’s native location permission prompt until the respondent clicks Allow location.
Accuracy and failure handling
Minimum accuracy
Minimum accuracy (meters) sets how precise the browser-reported accuracy radius must be for a capture to count as meeting the requirement (default 100 meters).
If the device reports a larger (less precise) radius than your threshold, the capture is treated as poor accuracy and follows the Poor accuracy failure path you configure.
Failure paths
For each failure type you choose how Quali-Fi resolves the attempt:
| Failure | Typical cause | Path options |
|---|---|---|
| Permission denied | Browser or OS blocked location | Immediate resolution, or show help (no automatic re-prompt) |
| Unavailable | Geolocation not available | Immediate, show help, retry, or help then retry |
| Timeout | Location request timed out | Same as Unavailable |
| Poor accuracy | Accuracy radius worse than your minimum | Same as Unavailable |
| Outside allowed area | Coordinates fall outside a configured allowed area (when one is in effect) | Same as Unavailable |
Retry paths are capped (typically 2 or 3 attempts). Permission denied never auto-opens the native prompt again—browsers control that. Help copy tells the respondent to change site settings, then use Try again only after they have updated permissions.
Final outcome is always mode-driven:
- Optional → continue into the survey after the configured path finishes
- Required → terminate (Screened Out) unless a capture eventually passes
What gets stored
Capture and place enrichment are separate.
Browser capture (immediate)
When a capture succeeds, Quali-Fi can retain:
- Latitude / longitude (if Retain coordinates is on)
- Reported accuracy in meters
- Operational status fields (consent, permission, capture result, timestamps)
Turn Retain coordinates off when you only need derived place labels and do not want exact lat/lng kept on the response. Exact coordinates are highly identifying PII.
Reverse geocoding (background)
When Enable reverse geocoding is on, Quali-Fi enriches a successful capture in the background with best-effort:
- Country
- Region / province / state
- Locality (city / municipality)
- Postal / ZIP code
Enrich & retain formatted address is off by default. When on, Quali-Fi also stores the provider’s address label (street / locality line). That label can be as identifying as coordinates—turn it on only when you need it.
Enrichment never blocks the respondent. A slow or failed reverse-geocode does not undo a successful browser capture or change whether they continue.
Respondent experience
After any access / kiosk / member gates, and after the response session starts, respondents with Optional or Required mode see a Location step:
- Your consent message
- A short note that device location is browser-reported
- Allow location and the decline / continue control for your mode
If they allow location, the browser shows its own permission dialog. While Quali-Fi waits, they see Getting your location….
On resume, if location was already finalized for that response, they are not prompted again.
Viewing location in analytics and exports
Location appears as response metadata columns—the same family as IP / OS / browser—not as survey answer columns.
Raw Data
Go to Analytics → Raw Data. When location capture is enabled (or historical location rows exist), you will see operational columns such as:
- Location Capture Status
- Location Capture Resolution
- Location Permission Status
- Location Consent Status
- Location Accuracy (m)
- Location Accuracy Met
- Location Allowed Area Status
- Location Enrichment Status / Error
- Location Retained Resolution
- Location Captured At
Coordinate and place fields (latitude, longitude, country, region, locality, postal code, formatted address) appear with other respondent PII. Without respondent PII view permission (and package access), those values are masked; operational status columns stay readable so you can still see capture outcomes.
CSV and SPSS exports
The same metadata fields can appear in CSV and SPSS exports when location was captured for responses. Exporting coordinate and address PII requires respondent PII export permission (and package access), same as other identity fields.
There is no dedicated geography map report in analytics for this feature yet—use Raw Data and exports for analysis.
Privacy and permissions
| Concern | Behavior |
|---|---|
| Consent | Custom message + explicit Allow before the browser prompt |
| Storage | Coordinates and address fields are PII; operational status is not |
| Access | View / export / clear follow existing respondent PII permissions and package gates |
| Logging | Coordinates and address values are not written to ordinary application logs |
Include location in your privacy notice and fieldwork brief when you enable Optional or Required capture.
Tips
- Start with Optional while you validate device behavior; switch to Required only when location is a hard screen-in.
- Keep the consent message short and specific about why you need location.
- Prefer reverse-geocoded country / region / locality over formatted address when approximate place is enough.
- Test on the devices and browsers your sample will use—especially mobile Safari and Chrome, where permission UX differs.
- Do not confuse this with Interactive Map’s optional Geolocation control, which only helps a respondent place pins on a map question.
Troubleshooting
Respondents never see a location step
- Confirm Tools → Respondent Location is set to Optional or Required and saved.
- Confirm they are starting a real response session (preview / live), not a flow that never creates a response ID.
“Allow location” does nothing / permission keeps failing
- The browser or OS may have blocked the site previously. Respondents need to open site settings, allow location, then use Try again.
- HTTPS (or localhost) is required for browser geolocation in most environments.
- Some corporate or in-app browsers disable geolocation entirely—use Optional or a different channel for those samples.
Capture succeeds but country / city columns are blank
- Enrichment runs in the background. Refresh Raw Data after a short wait.
- Check Location Enrichment Status / Location Enrichment Error on the row.
- Confirm Enable reverse geocoding is on in Respondent Location settings.
Required mode screens people out unexpectedly
- Review Minimum accuracy—indoor Wi‑Fi often reports larger accuracy radii than outdoor GPS.
- Review failure paths and attempt counts for timeout and poor accuracy.
- Confirm respondents understand that declining ends the survey in Required mode.