Aampe (Actions) Destination

Aampe’s Agentic AI learns what works for each customer. Then it instantly adapts your messaging and delivers at optimal times to drive better engagement, growth and unlock valuable insights.

By assigning a dedicated agent for each user, Aampe conducts controlled, parallelized experiments to learn user preferences and optimizes engagement for them. It’s a dynamic, self-improving system that fine-tunes every interaction, ensuring your messaging evolves as fast as your audience does.

This destination is maintained by Aampe. For any issues with the destination, contact the Aampe Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Aampe (Actions)” in the Destinations Catalog, and select the Aampe (Actions) destination.
3. Choose which Source should send data to the Aampe destination.
4. Open Aampe Composer and navigate to the Data Integrations page, click Add Integration, select Segment and click Next.
5. Copy the Segment API Key from Aampe Composer, then return to the Segment app.
6. On your Aampe destination’s settings page, enter the API key that you copied from Aampe Composer.
7. Select the appropriate data region as per the privacy policy and click Save.

Supported methods

Aampe supports the following methods, as specified in the Segment Spec.

Segment sends Track, Page, Screen calls to Aampe as an event. These are used by Aampe agents to learn preferences for your users and take action accordingly.

Aampe also receives Identify calls and user property update calls from Segment which helps with high-level segmentation for eligible Aampe audiences.

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.

Settings

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