We have an architectural requirement for CQ5.5 to be situated behind an application in which it acts as a "content provider" rather than the application interfacing directly with the client. We also have a requirement to leverage client contexts and segmentation. Reading further into segmentation, it seems what CQ uses is based primarily on the profile of the user in CQ5. There are other factors such as IP, geo location and device type that can also be used to resolve segments, but given that we won't have users interfacing directly with CQ, is there a way to have CQ resolve segments based on request attributes passed into CQ?
Thanks in advance