Skip to content

Commit 1e3f641

Browse files
Merge pull request #7762 from saiyamaampe/add-aampe-destination
Add Aampe (Actions) destination documentation
2 parents 4bb1395 + 1af1c9a commit 1e3f641

File tree

1 file changed

+29
-0
lines changed
  • src/connections/destinations/catalog/actions-aampe

1 file changed

+29
-0
lines changed
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Aampe (Actions) Destination
3+
id: 6874c64e5eda096bf3850ee0
4+
private: true
5+
beta: true
6+
---
7+
8+
[Aampe](https://aampe.com/){:target="_blank”}'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.
9+
10+
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.
11+
12+
This destination is maintained by Aampe. For any issues with the destination, [contact the Aampe Support team](mailto:[email protected]).
13+
14+
## Getting Started
15+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
16+
2. Search for "Aampe (Actions)" in the Destinations Catalog, and select the **Aampe (Actions)** destination.
17+
3. Choose which Source should send data to the Aampe destination.
18+
4. Open Aampe Composer and navigate to the [Data Integrations page](https://compose.aampe.com/configure/integrations){:target="_blank”}, click **Add Integration**, select Segment and click **Next**.
19+
5. Copy the Segment API Key from Aampe Composer, then return to the Segment app.
20+
6. On your Aampe destination's settings page, enter the API key that you copied from Aampe Composer.
21+
7. Select the appropriate data region as per the privacy policy and click **Save**.
22+
23+
## Supported methods
24+
25+
Aampe supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
26+
27+
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.
28+
29+
Aampe also receives Identify calls and user property update calls from Segment which helps with high-level segmentation for eligible Aampe audiences.

0 commit comments

Comments
 (0)