# Aampe Event Stream Sync

Stream events and user properties from Amplitude to Aampe for personalized messaging and engagement.

Source: https://amplitude.com/docs/data/destination-catalog/aampe-event-stream

---

On this page

- [Prerequisites](#prerequisites)
- [Aampe setup](#aampe-setup)
- [Amplitude setup](#amplitude-setup)
- [Data Security](#data-security)

# Aampe Event Stream Sync

Aampe's event stream integration enables you to send user events and properties from Amplitude to Aampe in real-time. This data powers Aampe's AI agents to deliver personalized messaging across multiple channels.

[Aampe](https://aampe.com/) deploys individual AI agents, one for each user, that analyze behavior and preferences to deliver hyper-personalized messages across SMS, email, push notifications, and in-app banners.

## Prerequisites

This Amplitude to Aampe event streaming integration requires an Aampe account.

## Aampe setup

Retrieve your Aampe API key:

2. Go to <https://compose.aampe.com/system-setup/integrations/events>
3. Log in with your organization credentials
4. Navigate to *System Setup > Integrations > Event data import*
5. Click **Connect** next to "Aampe endpoint"
6. Copy the API key

### Amplitude setup

1. Navigate to **Data > Destinations** in your Amplitude dashboard

2. Search for "Aampe" and select **Aampe** with subtitle Events and User Properties

3. Enter a sync name click **Create Sync**.

4. Configure the destination with:

   - **REST API Key**: Paste the Aampe API key you copied in [Aampe setup](#aampe-setup)
   - **Mappings**: Select the Amplitude property that maps to the Aampe User ID. The property you choose should match the `user_id` in Aampe.
   - **Send Events**: By default, Amplitude sends all events to Aampe. Optionally define filter criteria to limit the events that Amplitude sends. Optionally select any additional user properties to send with event information to Aampe.
   - **Send users**: Enable the toggle to send users and associated user properties to Aampe. Optionally select additional user properties to send with users to Aampe.

5. Enable the destination when you're ready and click **Save**.

## Data Security

- All API communications use bearer token authentication
- Data is transmitted securely over HTTPS
- User identifiers should be non-PII where possible

Was this helpful?

<!--$-->

<!--/$-->