Aampe Destination
Destination Info
- Accepts Track calls.
- Refer to it as Aampe in the Integrations object
- This integration is partner owned. Please reach out to the partner's support for any issues.
Aampe uses automated, rapid learning to personalize notifications, and continuously learns what messages bring value to your customer.
This destination is maintained by Aampe. For any issues with the destination, contact the Aampe Support team.
- From the Destinations catalog page in the Segment App, click Add Destination.
- Search for "Aampe" in the Destinations Catalog, and select the "Aampe" destination.
- Choose which Source should send data to the "Aampe" destination.
- Go to the Data Integrations page on Aampe Composer, click on "Add Integration", select "Segment" and click "Next".
- Copy the Segment API Key from the resulting page.
- Enter this key in "API Key" in the "Aampe" destination settings in Segment.
Aampe supports the following methods, as specified in the Segment Spec.
Segment sends Track calls to Aampe as a track event. These are used by Aampe to display engagement activity and reports in the Aampe Composer. You can use these to configure goals that are used for monitoring and creating campaigns. It may take up to 24 hours for events to show up in the Aampe Composer.
analytics.track("Login Button Clicked");
Segment sends Track calls to Aampe as a track event.
Other methods like Page, Screen, and Identify are accepted by the Aampe destination but are not stored or used in any way.
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 Aampe may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
After logging into the Composer, go to Configure -> Data Integrations, click on "Add Integration" and select Segment
Optional
If your users all belong to the same timezone, enter a fixed value here. If we are unable to find a value in "context.timezone", this value will be used. Defaults to UTC
Optional
Path to the field that contains the timezone string for the user to which the event belongs. By default we will use "context.timezone".