Lifecycle and Management
Q: Can I edit or delete an existing Aggregate?
A: No. To ensure data consistency across Segmentation and Personalization, Aggregates are immutable. If logic requirements change, you must create a new Aggregate with the desired configuration.
Q: Is there a limit on the number of Aggregates I can create?
A: There is currently no fixed numerical limit. However, Aggregates are subject to system guardrails to maintain platform performance. Highly complex or inefficient definitions may be restricted.
Q: Do Aggregates count toward my attribute limit?
A: No. Since Aggregates are calculated metrics processed at runtime, they do not consume Attribute limits.
Logic and Calculation Constraints
Q: Are Aggregates calculated per user or globally?
A: Aggregates are always user-scoped. Each value is calculated based on the individual event history of a specific user.
Q: Can I use multiple event types in a single Aggregate?
A: No. Each Aggregate is scoped to a single event type. While you can apply filters based on parameters within that event, cross-event logic is not supported.
Q: Can filter conditions reference external attributes?
A: No. Filters can only reference parameters belonging to the selected event. They are used exclusively to include or exclude specific instances of that event from the calculation.
Q: What happens if an event parameter is missing or null?
A: If a required parameter is missing from an event instance, that specific instance is excluded from the calculation. The Aggregate will continue processing using the remaining valid event data.
Q: What happens if I change the event or event parameter?
A: Aggregates depend on the schema defined at the time of creation. If an event or parameter structure changes, the Aggregate may stop producing valid results. In this scenario, creating a new Aggregate is recommended.
Data Accuracy and Discrepancies
Q: Why does an Aggregate value change or decrease over time?
A: Values fluctuate based on the Time Window and Data Retention (TTL) settings. Events fall out of the calculation when they exit the selected lookback window or are deleted due to TTL, even if no new events are received.
Q: Why doesn’t my Aggregate value match my external system?
A: Discrepancies are typically caused by differences in Time Windows, TTL limits, parameter-level filters, or specific Identity Resolution (unification) logic. Ensure both systems are aligned on these configurations.
Q: What happens if my event data is inconsistent?
A: Because Aggregates rely on raw event data, any inconsistencies in payloads or identifiers will lead to inaccurate calculation results.
Integration and Performance
Q: Are Aggregates updated in real-time?
A: Aggregates update as new events are processed. Note that a marginal delay may occur depending on Ingestion and processing cycles.
Q: Why doesn’t an aggregate trigger an action when the value changes?
A: Aggregates update based on event data and time windows. Changes caused purely by time passing (without a new event) do not automatically trigger actions.
Q: Where can I use Aggregates within the platform?
A: Aggregates are primarily used in Dynamic Segments and Dynamic Content. A single definition can be shared across both modules.