Aggregations.io (Actions) Destination

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.

Build your own Mappings. Combine supported triggers with the following Aggregations.io-supported actions:

• Send Events

Send events to Aggregations.io.

Send Events is a Cloud action.

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.

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