[Content]: Document which conditions force batch instead of real-time processing for audiences

What article on segment.com/docs is affected?

https://segment.com/docs/engage/audiences/#real-time-compute-compared-to-batch

What part(s) of the article would you like to see updated?

Give as much detail as you can to help us understand the change you want to see.

Segment should specify the kinds of conditions in an audience or computed trait that will switch it from real-time to batch computation. I discovered that certain time-based conditions, such "in the past X days" affect this, but your docs don't set any expectations.

Why should the docs be changed? What use cases does it support?

It would help users understand the capability Segment Engage provides before they plan on using an audience to address a business requirement, just to find out that they cannot filter users in real-time. Honestly, the lightning bolt looks pretty subtle and a user might not immediately notice it or recognize its significance.

What is the expected outcome?

Users evaluating Segment Engage for their use cases can read the audiences documentation and quickly understand whether they can use its features to filter users in real-time or not.

Additional information

No response

segmentio / segment-docs