I am using CQ5.4 and wanted to find out if there is any limitation to the number of attributes or rules i can set in a segment.
I want to use around 30000 to 50000 attributes in one segment, like a different set of zipcode etc...
can anyone let me know if there is any limitaion on 5.4 or 5.5, since i am planning to upgrade as well.
This seems like something you should do on the server side. How would an author even create a segment with 30000 to 50000 attributes? And it seems like a waste of bandwith to transfer this many values to the client side for evaluation.
Without customization, the segmentation is cookie-based, so I can pretty much guarantee you will have issues with browser limits on cookie size. I agree with Justin though...that many attributes isn't really manageable without building some kind of automation into it.
May be i stated my question wrong, its not really 50k traits, it probably in 20's, or 30's in number, but use those traits in abundance, for ex
if zipcode is a traits, i would like to create a OR segment rule with all possible combination of zipcodes, which might be a huge number in the segmentation rule. So is there a limitation for a segmentation rule was my question.
Raj, are we only talking about ZIP codes here? If this is the case, it may be possible to implement a compression algorithm that will not only allow for a smaller representation on the wire, but also for faster execution.
Sure definitely will be doing something around automating on serverside and may be an algorithm, to combine few zips to one.
But i was trying to only get the numbers meaning is there limitation CQ has set on the segments and how much of an impact will be on the performance to evaluate the segment.
Europe, Middle East and Africa