The Sitecore IP Geolocation service provides information about the location and owner of an IP address beyond that provided by a reverse DNS lookup. IP Geolocation information includes the country, state, city, and the registered company name of every visitor.
You can use IP Geolocation lookups to create conditional renderings or personalization rules that show different content based on the visitor's location.
System requirements for Sitecore
Sitecore IP Geolocation is included in the initial version of Sitecore Experience Platform 8.1 (Sitecore XP) and all later versions by default, and is tested with all subsequent updates. This means you only need to subscribe to the Sitecore IP Geolocation service.
The Sitecore IP Geolocation module is fully compatible with Sitecore Experience Management (CMS-only mode).
Activate the Sitecore IP Geolocation service for Sitecore
To activate the Sitecore IP Geolocation Service on Sitecore XP 8.2, you must subscribe to the Sitecore IP Geolocation service in the App Center.
Subscribe to the Sitecore IP Geolocation Service
- Go to the Sitecore Launchpad, App Center.
- Click Sitecore IP Geolocation Service.
- Select your commitment period and number of lookups per month.
- Select I accept the terms and conditions and confirm your subscription.
After you have activated your subscription, it may take some time for the system to update the license information. When the system has updated, the Sitecore IP Geolocation service will automatically conduct geolocation lookups.
Configure a firewall
It is common to have a firewall set up between your content management and content delivery servers. To ensure that the Sitecore IP Geolocation service works correctly in all scenarios, you must configure your firewall settings to allow requests to the service.
Add a firewall rule to allow HTTPS protocol for:
Using a proxy server
When requests that come from a reverse proxy server to your Sitecore instance should be tracked as the valid IP addresses of a client, and not as the IP addresses of a proxy, use the following setting.
Analytics.ForwardedRequestHttpHeadersetting to the value: X-Forwarded-For