Personalization using geolocation doesn't work in publish instance | Community
Skip to main content
subrato_kha
subrato_kha
September 10, 2018

Personalization using geolocation doesn't work in publish instance

  • September 10, 2018
  • 6 replies
  • 9268 views

Hi All,

I am trying to setup personalization using geolocation, but it is not working in publish instance.

The behaviour works fine in author instance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

6 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
September 11, 2018

Any particular article that you are following?

Reference article:- Using the ContextHub to setup GeoLocation data in the Experience Manager Toy Store site

Note: ContextHub is not by default aware of the currently logged in user on publish servers and such users are regarded by ContextHub as “Anonymous.” You can make ContextHub aware of logged in users by loading the profile store as implemented in the We.Retail reference site.Refer to the relevant code on GitHub here.

Kautuk Sahni
subrato_kha
subrato_khaAuthor
September 11, 2018

Hi kautuksahni​,

Thanks for the reply.

I don't want ContextHub to be aware of the user. It can be anonymous. I just want it to show the location of the visitor. Depending on which my created segment will resolve. In my segment I am simply comparing the country code which I expect it to be available OOB as part of personalization.

Above example doesn't matches my use case

R
ravik80714278
April 1, 2019

Hi AEM Experts,

I am also facing the same issue in AEM 6.4

Any solution or fix to the issue? Thanks!

F
felipeabellan
September 24, 2019

Solution for me so far is to build a custom store based on the geolocalization one. There is a constraint in the reverse geolocation to the context hub ui. Not sure why. but its there. not configurable as far as I could read in the code.

The summit toy store keeps coming as a reference, but that is conviniently only tested in author environment or using lat/long params which are the only properties available in the contexthub persistance store when viewed in publish. All segments created using any address detail will not be resolved.

P
papenaarun
October 28, 2019

Any update on this ?

Am facing the same issue.

Just created a simple segment's for geolocation/address/postalCode.

Working in Author but not in Publish.

I have tried in AEM 6.3, 6.4 & 6.5 instances.

F
felipeabellan
November 15, 2019

Not that I'm aware. Code in geolocation store do not allow reverse geolocation if ContextHub UI is not available. So publish server will not do reverse geolocation. Any segment done with this properties are not going to work on publish unless you extend this store or create your own.

P
pvo008
April 11, 2021

This is because of lack of access to 

/libs/settings/cloudsettings/legacy/contexthub/geolocation

Proper fix would be to correct

com.adobe.granite.contexthub.impl.GoogleMapsSignatureServlet

Here, proper service user needs to be used and access need to be granted accordingly.

 

Quick Fix: Provide anonymous user access to

/libs/settings/cloudsettings/legacy/contexthub/geolocation
Terms & ConditionsAccessibility statement

Loading footer...