Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
In most cases when working with batched data we also need to be more close to real time. Both the bach and streaming audiences has a threshold when it comes to number of active and live audiences. Rules can in many cases replace the way we use audiences, and with not the some threshold rules. But today we are not able to use event data in this rules. If we f ex in a computed attribute could use event data and not just Attributes we could create rules instead of using streaming segments - that has limitations in the systems.
Hey @Selliers, you absolutely can use experience events using Computed Attributes! We're using these for a number of functions such as 'Most Recent Purchase' that looks at purchase data we batch in.
I was thinking more in the direction of using rules instead of audiences, when creating activities. But here is some limitations on how and what you can do with a rule compared to a audience. F. ex that you cant combine event data with attributes. Is there a reason for that the "rule builder" has less possibilities than the audience builder?
Thanks for the follow-up! That’s a great question and definitely something that deserves deeper insight. I’m not the best person to answer this in full detail, so I’m tagging @Ivan_Mironchuk here, he might be able to shed more light on why there are certain limitations in the rule builder compared to the audience builder.