Hi, we are trying to use ContextHub to implement personalisation (segmentation) on our website.
We were able to implement it correctly. Everything is OK, but in some computers, we don't know why, the screen flickers before displaying the final content.
In some computers:
a) First, it displays the Default content (without segmentation applied).
b) Then, after 1 second, the screen changes completely to match the segmentation.
Anyones knows why this is happening? We want to see the final content with segmentation applied without the page flickering.
Solved! Go to Solution.
Views
Replies
Total Likes
Not sure but that could be because of network/machine related issues that the libraries take time to load & process. For the m/c where you notice the error, do they have local AEM or they use the same remote/cloud AEM server?
Couple of pointers to debug:
Views
Replies
Total Likes
Not sure but that could be because of network/machine related issues that the libraries take time to load & process. For the m/c where you notice the error, do they have local AEM or they use the same remote/cloud AEM server?
Couple of pointers to debug:
Views
Replies
Total Likes
I am really working in a very restricted network environment, where we have a strong proxy with lots of blocked websites and strict monitoring of information.
It may be that our proxy is slowing down the loading of some scripts. But I am not sure yet what is the root of the problem.
Views
Replies
Total Likes
very likely but proxy would have same impact on all m/c, its sort of a combination of multiple reasons..
Views
Replies
Total Likes
Views
Likes
Replies