24

Firstly; Using the Service based Geo IP service is not recommended practice for personalization scenarios. The guaranteed response time for the service simply isn't fast enough - and it will slow down your site immensely if you put it in production. Secondly; and potentially exactly because of this; you could be experiencing the known issue referred to here....


19

This looks like it's part of the Device Detection feature within the Sitecore.CES configuration. It's fair that you would want device detection yet not have the GeoIP feature of it enabled. Have you tried renaming the following two configuration files to disable them and see if that works? App_Config/Include/CES/Sitecore.CES.GeoIp.config App_Config/...


16

Ensure that the following setting in the Sitecore.Analytics.config file is set to false <setting name="Analytics.PerformLookup" value="false" />


8

I can suggest the following solution: You need to implement a custom field reader with a custom field converter: using Sitecore.DataExchange.DataAccess; namespace Example { public interface IBaseValueReader: IValueReader { string AttributeName { get; set; } } } AddressFieldReader: using System; using Sitecore.DataExchange.DataAccess;...


8

Where the Business Name Compares to Specific Value Rule In some cases, a business or institution may be available for an IP address. This rule compares against that name. The incidences of these are rather low, however, and when they are not available, the name of the user's ISP is exposed to be tested against. Please look here http://www.berndtgroup.net/...


8

The geo lookup isn't fast enough to work for a first page. It's not even really worth trying. If you must have it, you can hook into the GeoIP lookup service directly, or you can ajax in your content, to give the service a change to lookup the IP without destroying the user experience. Some CDNs (like Akamai) can add headers to requests that will identify ...


7

You need to check in your GeoIP collection data to see if your IP is already included with null information. Most of the time this is the case. Please note that, when you test this using TestIp.aspx page, it directly sends your request to GeoIP Service directly without looking at your cache or data. That is the reason it works with TestIp.aspx page. ...


6

Answer It is possible to set this data on your own. It can be done as Gatogordo suggests, using the following code snippet. Tracker.Current.Session.Interaction.SetGeoData(new WhoIsInformation { City = "Boston", Country= "US", Region = "North America" }); However, it's important to know how this data is initially collected in an out-of-the-box scenario. ...


6

I'm sure Pete will elaborate further on this, but to get you going already: the property on the Interaction is indeed only a getter, but there is a function called SetGeoData. This would end up in this: Tracker.Current.Interaction.SetGeoData(new WhoIsInformation { City = "", Country= "", Region = "" }); Found some code here that fills the geo data (amongst ...


6

Sitecore Personalization using GEO IP is not executed: It works after i added new rule under (/sitecore/system/Settings/Rules/Definitions/Elements/GeoIP/)to check country with country code not country name as already exists in sitecore. The existing rule: where the country compares to specific country did not work properly because the returned value for "...


6

Azure Search has no built in replication at this time. The Sitecore Azure Search Provider can be pointed to multiple Azure Search instance at once and it will mirror all Create, Update, Delete, requests to those additional instances.


6

The quick answer is that you should always use option #1 over option #2. When you make a request to LookupManager.GetInformationByIp(), this makes a direct service call to map the ip to a location. That might seem to be what you are trying to achieve, but there are several issues with that. Including some of the following: No caching to return previously ...


5

You installed a module for Sitecore 8 on a Sitecore 9 site. From Sitecore 8.1 and higher, you don't need that module - it's already included. Check the documentation on https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/ip_geolocation/ip_geolocation/setting_up_sitecore_ip_geolocation but be sure to read it for your Sitecore ...


5

We are usually faking local IP address in this case. We use querystring such as "?ipaddress={Fake_Ip_goes_here}" to inject faked ip address. In your code, in place where you determine IP address, just add another condition if this query string is present, use value provided instead. There are sites like this one https://www.nirsoft.net/countryip/ which ...


5

Sitecore has a fix for this, but it has the drawback of possibly slowing your site down. With this KB you can specify the time in seconds you are willing to wait for the GeoIP lookup to get in sync with the fist page load. https://kb.sitecore.net/articles/320734


5

You should be able to setup a test file to test if the GeoIp service is working correctly. I'd recommend following Solution 3 in the Sitecore support issue below: https://kb.sitecore.net/articles/798498 Basically you need to drop code like the following on your server. Ideally in a location under the /sitecore path to protect just anyone from accessing ...


5

Yes it will. Personalisation is based on the current session - it happens real-time. Any personalisation rules you normally use, will continue to work regardless of this setting. The hashing or blanking of IP addresses affects what gets stored in xDB. This happens after any personalisation has taken place to render your page. In short; these configuration ...


4

There are a few things to note: some web servers have outbound firewalls, now it might be that the CD servers cannot access the GeoIP service make sure the X-Forwarded-For header is not appending the port number to the client IP - ARR and nginx do that under some configurations IP/geo mapping data is recorded in the xDB MongoDB - check the GeoIps collection ...


4

No, not out of the box. According to Sitecore, there is no way to upgrade the precision on the Geo IP services provided. Out of the box, they state: Inaccuracy in country, state, and city resolving. Sitecore IP Geolocation service may provide limited precision on a country, state, and city level. For Australia, the precision of the service is around 66%....


4

If you haven't done it already, you have to go through your account manager to get special permissions to login through the app center. I had to do this for SC9 as well. I had to fill out this form & have app center access permissions associated with my Sitecore Portal login.


3

Right, so turns out this is a case of a very unhelpful exception message, for something that really is rather simple. The client had not activated the GeoIP Location service correctly, which led to the above exception being thrown - even from my TestIP code. Once this was sorted out, the error went away.


3

The GeoIP service can be made to resolve at zipcode level. That said; you cannot rely on it to personalize your content for your visitor - real time. For that you need to look at other options - like creating your own MaxMind integration or looking at other alternatives. See also: Sitecore IP Geo location Service-Personalization with Geo-based conditions ...


3

I just had this issue yesterday. The problem is that if you have tracking disabled on your CM instance, there is a visibility rule that prevents the whole section from showing up. This means that even if you have tracking enable on your CD instance, it won't show up on your CM instance. The visibility rule is configured at /sitecore/system/Settings/Rules/...


2

although Dylan's answer is correct but I would like to add few more points here - if you still receiving incorrect information? Check whether the correct IP information is stored in the Analytics database Sitecore 7.5 – Sitecore 8.x: the “GeoIps” collection, Collection database (MongoDB) Sitecore 6.4.1 – Sitecore 7.2: the “GeoIps” table, Analytics ...


2

As far as I can tell from my own installation (we ran without GeoIP for a week or so) the answer is no, it does not go back in time. However, if a visitor returns to the site, their Geo will be captured as part of their profile. I have a few visitors that are anonymous, but hit my site regularly, and they have been classified by GeoIP after the service was ...


2

You can find location based on visitor IP and can implement redirect condition for a particular url. e.g: System.Net.IPAddress ipAddress = null; string country = string.Empty; if (System.Net.IPAddress.TryParse(Request.ServerVariables["REMOTE_ADDR"], out ipAddress)) { Sitecore.Analytics.Lookups.GeoIpOptions geoIpOptions = new Sitecore.Analytics....


2

Sitecore supports a Search service with geo-replicated scenarios. To use this type of scenario: Create two or more Search service instances. Add connection strings with a pipe separator (|). If you have two search services, for example, searchservice1 and searchservice2, and you want to use them in a geo-replicated scenario, you must use the following ...


2

If you wish to personalize by Australian State,'Region' is usually the 'State' (or 'Province', depending on country). Mark is right about data accuracy, but if you are just looking to pull what it THINKS the State is, you would usually personalize to Region.


2

You should set X-Forwarded-For header in config settings: <setting name="Analytics.ForwardedRequestHttpHeader" value="X-Forwarded-For" /> If you use reverse proxy server you should also disable "Include TCP port from client IP" in Application Request Routing


2

You can add a processor to change request IP address locally in the analytics "createVisit" pipeline. <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <pipelines> <createVisit> <processor type="Sitecore.Foundation.Geolocation.Pipelines.Testing.ChangeIP, Sitecore.Foundation.Geolocation"...


Only top voted, non community-wiki answers of a minimum length are eligible