Aggregations.io (Actions) Destination
Aggregations.io 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.
Getting started
- From the Segment web app, click Catalog, then click Destinations.
- Find the Destinations Actions item in the left navigation, and click it.
- Click Configure Aggregations.io (Actions).
- Select an existing Source to connect to Aggregations.io (Actions).
- 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 Objectsand the API Key requiresWritepermission. For more information, see the Aggregation.io docs.
Destination Settings
| Setting | Description |
|---|---|
| API Key | Required. Your Aggregations.io API Key. This key requires Write permissions. |
| Ingest Id | Required. 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. |
Available Actions
Build your own Mappings. Combine supported triggers with the following Aggregations.io-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Send Events
Send events to Aggregations.io.
Send Events is a Cloud action.
| Field | Description |
|---|---|
| Data | Type: OBJECTPayload to deliver (JSON-encoded). |
| Enable Batching* | Type: BOOLEANEnabling sending batches of events to Aggregations.io. |
| Batch Size | Type: NUMBERMaximum number of events to include in each batch. Actual batch sizes may be lower. If you know your events are large, you may want to tune your batch size down to meet API requirements. |
Engage
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an 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.
Real-time to batch destination sync frequency
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.
| Setting | Description |
|---|---|
| API Key (required) |
password. Your Aggregations.io API Key. This key requires Write permissions. |
| Ingest Id (required) |
string. 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. |
This page was last modified: 17 Jan 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!