👍

Estimated setup time

15 minutes

There are 2 ways to setup Aampe as a segment destination

  1. Configure Aampe Destination
  2. Google Cloud Storage Destination

Configure Aampe Destination

This guide assumes you have an Aampe account. If not, sign up here

  1. Login to your Segment account at https://app.segment.com/

  2. Select Destinations under Connections on the left side panel

  3. Click on "Add Destination"

1482
  1. Enter Aampe in the Filter Destinations searchbox.

  2. Click on the Configure Aampe button, select the data source for your app events, then click on Next.

  3. Enter a destination name of your choice and click on Save. We recommend naming it Aampe App Events

  4. Login to Aampe Composer in another browser tab, then go to Configure -> App Events

744
  1. Click on Add Integrations, select Segment, and then copy the Segment API key from the resulting page
1018
  1. Paste this key into the API Key field under Connection Settings on the Segment website (this is where we left off at Step 6.)
1690

Configure Google Cloud Storage Destination

Requirements:

  • A Google Cloud bucket name. For example: aampe-staging-data-xxx
  • A credentials file. For example: xxxxxxxx-4e120-14a6f2ac3c25.json

Aampe will provide both of these to you for setup

  1. Go to Segment’s Connection > Destinations section
200
  1. Click on Add Destination
  2. Search for Google Cloud Storage in the catalog that appears
1600
  1. Click on the Google Cloud Storage destination
  2. Click on Configure Google Cloud Storage.
1600
  1. Select the source you wish to share with Aampe and then click on Confirm Source. Source will be your data source housing the event data
1600
  1. You will then be redirected to a screen where you will provide the destination bucket details (provided by Aampe):
    Bucket: the name of the bucket where the data will flow
    GCS Private Key File: the content of the JSON with the access credentials to that bucket
1600
  1. After having input both details, you need to click on the toggle that enables this destination and the integration is completed
1600