The Aggregation consolidates related UDRs that originate from either a single source , or from several sources, into a single UDR. Related UDRs , are grouped into "sessions" according to the value of their respective fields, and a set of configurable conditions.
The first UDR to match a set of conditions triggers the generation of a new session. Consecutive UDRs that match the same conditions can then be handled in the context of the same session.
The agent stores the session data in a file system, Couchbase, Redis, or Elasticsearch. It is also possible to use the settings for file storage to keep the session data in - memory only.
When selecting which storage type you require, note that File Storage can be used in batch and real-time workflows; Couchbaseand Redis can only be used in real-time workflows; Elasticsearch can only be used in batch workflows.
...
When several matching sessions are found, the first one is updated. If this occurs, redesign the workflow. There must always be zero or one matching session for each UDR.
High-level steps for configuration of Aggregation
Follow the steps below to configure Aggregation:
Create a session UDR in Ultra format.
- Create a storage profile, i.e. Couchbase or Redis profile (not required for file storage).
Create an Aggregation profile.
Create a workflow containing an Aggregation agent.
...