Geolocation Detection 🧪
Route Visitors and Display Conditional Elements Based on Country or City.
UNDER DEVELOPMENT Watch this space.
Use Cases
Route visitors to a Country-specific home page
Route visitors to a City-specific contact-us page
Feature Roadmap
Route user by Country
Routing table support
Supports routing any defined path, e.g. /about to any Geo-specific variants you have, e.g.
/about/gb,/about/au,/jp/about.Routed sources and destinations are unlimited, no enforced path rules.
Standardized GeoInfo object, to consistently describe the detection regardless of the GeoIP handler source
Cached responses, for minimal GeoIP service traffic
One request per unique user
GeoIP handlers;
IPInfo support. 50,000 requests/mo free.
Route user by Continent
Route user by City
Cache duration as a setting
Named route efficiency
Modify page paths on e.g. Home / to the routed page variant, to avoid unnecessary redirects.
Override support;
The ability to apply the current setting to a Dropdown, and automatically indicate the current Country, City, etc.
The ability to change country, city, etc and have that override the detected settings.
GeoIP handlers;
Support for multiple Geoip handlers
Ability to select in config
Developer support;
Expose and document the Detect objects for use in code, e.g.;
Data-binding support, populate a form's Zip code field, select a country, etc.
Auto-center maps
Automatic Filter-binding support for FS-Filter
GeoZone definitions;
Collection of countries, cities, zips, etc into a Zone, like "Europe"
GeoIP handlers;
Ability to select the GeoIP handler dynamically in config
Fallback handlers
GeoZone definitions;
Point-and-radius
Sort list by nearest ( branch locators, etc. )
Zip to data chaining
GeoIP handlers;
Possibly a Sygnal-specific Geoip handler
Usage Notes
Routing Rules
Routing rules are configured just before the library is loaded in the script section indicated with // Routing rules ( see quick start ).
You may have multiple rule configurations in this section, though this is mostly a future design facilitation. Most likely, the first rule matched will be applied.
Route by Country
Specify the rule type as geo-country.
Supply your routes, from country code to path, exactly as in the structure below. You may have as few or as many routes as you like.
If the visitor's country is not in the list, they will not be routed. They will simply match the default page.
<script>
// Routing rules
window['sa5_route'] = [{
type: 'geo-country',
path: '/',
route: [
["NZ", "/nz"],
["AU", "/au"],
["US", "/us"],
["GB", "/gb"],
]
}];
</script>IPinfo Lite
IPinfo Lite gives you essential IP data completely free, with no restrictions. Here’s what you have to look forward to:
Industry-leading, enterprise-grade accuracy
Country, continent, and ASN data
Use it commercially with no caps or usage limits
Data updated daily
Unlimited usage via API or download
Here's an example of the Lite API, showing the ASN and county level geolocation fields that are included:
Prefer working with files? The data is also available as a download, in JSON, CSV, MMDB and Parquet formats – ready to integrate into your tools, dashboards, or workflows.
IPinfo Lite is your new go-to – and built to support everything from side projects to production systems. While IPinfo Lite only includes a subset of all of the data we offer, there's no compromise to the data quality, or the refresh rate.
Last updated
Was this helpful?