> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reelevant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Geolocation

> Resolve the user geographic location based on their IP address

<img src="https://mintcdn.com/reelevant/amH2YHA9709Bju3v/images/workflows/node-geolocation.png?fit=max&auto=format&n=amH2YHA9709Bju3v&q=85&s=8abd32d561efee50a52c89f8ebc79930" alt="Geolocation node configuration panel showing address and location options" width="1024" height="768" data-path="images/workflows/node-geolocation.png" />

## Overview

The Geolocation node resolves the user's geographic location (city, country, coordinates) based on their IP address or other signals.

This node doesn't require manual configuration — it automatically provides location data that can be used by downstream nodes.

## Output Data

The Geolocation node provides:

* **City** — The user's city name.
* **Country** — The user's country.
* **Coordinates** — Latitude and longitude for precise location-based logic.

## Common Use Cases

* **Store locator** — Combine with a [Location Datasource](/product-guide/workflows/data-nodes/datasources) to find stores near the user.
* **Weather-based personalization** — Pair with a [Weather](/product-guide/workflows/data-nodes/weather) node to show weather-appropriate content.
* **Regional content** — Use conditions to show different content based on the user's country or city.

## Best Practices

* Geolocation accuracy depends on the user's network. IP-based geolocation is typically accurate to the city level.
* For email channels, the location reflects where the email is opened, not where the user lives.
* Consider adding fallback branches for cases where geolocation data is unavailable.