Aggregated Events
How event aggregation combines multiple events into one at the destination, and how page size controls the batching.
The short answer
When you opt to aggregate events, HC combines multiple events together rather than sending them to the destination individually. This is useful for file-based systems, because it lets you combine multiple events into a single file.
How it works
Events are combined
Instead of each event going to the destination on its own, aggregation groups the events from a job into a smaller number of combined events.
Page size sets the batch
You can choose a page size for the aggregated events, which controls how many events are combined into one. For example, if you set a page size of 10 and a job creates 50 events, aggregation combines them into 5 events containing 10 of the original events each.
Parent events are created
When using aggregation, additional events are created that act as the "parent" event combining all of the events to be aggregated. These additional events are charged for as normal.
What this means for you
A file-based destination receives one file containing many events rather than one file per event.
The page size you choose determines how many events go into each aggregated event.
Each parent event is a chargeable event, so aggregation adds to the number of events you are charged for.
Related
Glossary of key terms (see Aggregation / parent event)
Was this helpful?
Still need help? Ask the team