Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Personalization using geolocation doesn't work in publish instance

Avatar

Avatar
Springboard
Level 3
subrato_kha
Level 3

Likes

10 likes

Total Posts

49 posts

Correct Reply

2 solutions
Top badges earned
Springboard
Establish
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Springboard
Level 3
subrato_kha
Level 3

Likes

10 likes

Total Posts

49 posts

Correct Reply

2 solutions
Top badges earned
Springboard
Establish
Validate 1
Ignite 5
Ignite 3
View profile
subrato_kha
Level 3

10-09-2018

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.

Replies

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,167 likes

Total Posts

6,281 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,167 likes

Total Posts

6,281 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

11-09-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.

Avatar

Avatar
Springboard
Level 3
subrato_kha
Level 3

Likes

10 likes

Total Posts

49 posts

Correct Reply

2 solutions
Top badges earned
Springboard
Establish
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Springboard
Level 3
subrato_kha
Level 3

Likes

10 likes

Total Posts

49 posts

Correct Reply

2 solutions
Top badges earned
Springboard
Establish
Validate 1
Ignite 5
Ignite 3
View profile
subrato_kha
Level 3

11-09-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

Avatar

Avatar
Level 1
ravik80714278
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
ravik80714278
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
ravik80714278
Level 1

01-04-2019

Hi AEM Experts,

I am also facing the same issue in AEM 6.4

Any solution or fix to the issue? Thanks!

Avatar

Avatar
Ignite 1
Level 2
notyourcat
Level 2

Likes

7 likes

Total Posts

15 posts

Correct Reply

1 solution
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Ignite 1
Level 2
notyourcat
Level 2

Likes

7 likes

Total Posts

15 posts

Correct Reply

1 solution
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
notyourcat
Level 2

24-09-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.

Avatar

Avatar
Validate 1
Level 2
papenaarun
Level 2

Likes

8 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Validate 1
Level 2
papenaarun
Level 2

Likes

8 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
papenaarun
Level 2

28-10-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.

Avatar

Avatar
Ignite 1
Level 2
notyourcat
Level 2

Likes

7 likes

Total Posts

15 posts

Correct Reply

1 solution
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Ignite 1
Level 2
notyourcat
Level 2

Likes

7 likes

Total Posts

15 posts

Correct Reply

1 solution
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
notyourcat
Level 2

14-11-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.

Avatar

Avatar
Validate 1
Level 1
pvo008
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Give Back
Affirm 1
View profile

Avatar
Validate 1
Level 1
pvo008
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Give Back
Affirm 1
View profile
pvo008
Level 1

11-04-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