As long as enough product data with the criteria is there you should not see any issues. If your collection is just formed with 2 or 3 products in it , then there is a chance of this issue.

you mean moving between profile (workspaces) with in Target ? For target. , always maintain 1 to 1 mapping from AEM to Target , else it will create an issue.

Adobe Analytics:1) Can have a segment based on user historic behaviour2) Not a near real time3) When you create the audience for the first time , it gonna take atleast 12 hrs sometime more to reach target4) I think there is a limit on number of audiences i.e. pushed to AT via People service.5) If something breaks in AA and not capturing the analytics events , it gonna impact Target Activity. AT:1) cannot create a segment with historic behaviour , may be possible with some profile scripting but l...

It doesnt make sense to expose http://localhost:4502/content/experience-fragments/my-project/us/en/site/globalnav/master/jcr:content/root/globalnav.model.json this link as a content server as it has jcr:content in it , also you are replying on the node formed by component. If someone removes the global nav component from the XF and readd and author it , then your content service will fail Suggestion - to use Content service as http://localhost:4502/content/experience-fragments/my-project/us/en/s...