Batch vs. Real-Time Calculated Attributes - Zeotap docs

This following table provides the differences between Batch Calculated Attributes versus Real-Time Calculated Attributes:

Feature	Batch Calculated Attributes	Real Time Calculated Attributes
Trigger Timing	Based on scheduled refresh (for example, every 24 hours)	Immediate response when conditions are met.
Example Use Case	A customer crossing a $25,000 purchase threshold is reflected in the next day’s refresh, triggering a welcome email the following evening.	A customer crossing a spending threshold triggers an immediate action, such as unlocking a loyalty reward instantly.
Best for	Non-urgent engagement, such as next-day campaign updates.	Real-time personalisation and immediate actions
Refresh Rate	Updates once every 24 hours.	Immediate — updates as soon as the event enters the system
Operator Limitations	Supports a full range of operators.	Some operators may not be available.

Note:For the full list of supported operators and their data type constraints, refer to Calculated Attributes: Guardrails & Limits.Segment Membership is a batch calculated attribute. It follows the scheduled refresh cycle and does not support real-time computation. For more information, refer to Segment Membership Calculated Attribute.

Components of the Calculated Attributes Screen

Create a Batch Calculated Attribute

Create a Real Time Calculated Attribute

Segment Membership Calculated Attribute

FAQs about Calculated Attributes

Last modified on August 12, 2026

⌘I