# Aggregations.io (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Aggregations.io (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[Aggregations.io](https://aggregations.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) enables you to use your existing analytics events and pipeline for real-time monitoring and alerting.

This destination is maintained by Aggregations.io. For any issues with the destination, [contact their Support team](mailto:help@aggregations.io).

## Getting started

1. From the Segment web app, click **Catalog**, then click **Destinations**.
2. Find the Destinations Actions item in the left navigation, and click it.
3. Click **Configure Aggregations.io (Actions)**.
4. Select an existing Source to connect to Aggregations.io (Actions).
5. In the destination settings, enter your Aggregations.io API Key and Ingest ID. Your ingestion on the Aggregations.io dashboard should be set up using `Array of JSON Objects` and the API Key requires `Write` permission. For more information, see the [Aggregation.io docs](https://aggregations.io/docs/ingesting-data/create-an-ingest).

## Destination Settings

| Field     | Description                                                                                                                                                    | Required | Type     |
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- |
| API Key   | Your Aggregations.io API Key. This key requires Write permissions.                                                                                             | Yes      | password |
| Ingest Id | The ID of the ingest you want to send data to. This ingest should be set up as "Array of JSON Objects". Find your ID on the Aggregations.io Organization page. | Yes      | string   |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Aggregations.io-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Send Events](#send-events-1)

### Send Events

Send events to Aggregations.io.

Send Events is a **Cloud** action.

| Field           | Description                                            | Required | Type    |
| --------------- | ------------------------------------------------------ | -------- | ------- |
| Data            | Payload to deliver (JSON-encoded).                     | No       | OBJECT  |
| Enable Batching | Enabling sending batches of events to Aggregations.io. | Yes      | BOOLEAN |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Aggregations.io (Actions)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field     | Description                                                                                                                                                    | Required | Type     |
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- |
| API Key   | Your Aggregations.io API Key. This key requires Write permissions.                                                                                             | Yes      | password |
| Ingest Id | The ID of the ingest you want to send data to. This ingest should be set up as "Array of JSON Objects". Find your ID on the Aggregations.io Organization page. | Yes      | string   |