> For the complete documentation index, see [llms.txt](https://docs.highcohesion.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.highcohesion.com/creating-streams/destinations/aggregated-events.md).

# Aggregated Events

When opting to aggregate the events, the core will combine multiple events together rather than sending them to the destination individually. This is useful for systems such as file based ones as it allows you to combine multiple events into a single file. Additionally, you can choose a page size for the aggregated events. This allows control over how many events will be combined into one. For example if you set a page size of 10, and a job creates 50 events, then the aggregation will combine this into 5 events containing 10 of the original events each.

{% hint style="info" %}
Please be aware that when using aggregation, additional events are created that act as the "parent" event that combine all of the events that are to be aggregated. These additional events are charged for as normal.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.highcohesion.com/creating-streams/destinations/aggregated-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.