Amplitude

👍

Estimated setup time

30 minutes

Aampe will fetch events and properties data from your Amplitude instance directly. The methods available are

1. Recurring data export to Aampe GCS bucket
2. Recurring data export to Aampe BigQuery [Preferred]
3. Using the Ampltiude API

Aampe is also able to collect certain data in real-time via a custom webhook which listens for events.

Real-time data push

Recurring data export

Setting up recurring data export - Google Cloud Bucket

1. In Amplitude Data, click Catalog and select the Destinations tab.
2. In the Warehouse Destination section, click Google Cloud Storage.
3. On the Getting Started tab, select the data you'd like to export. You can Export events ingested today and moving forward, Export all merged Amplitude IDs, or both. For events, you can also specify filtering conditions to only export events that meet certain criteria.
4. Review the Event table and Merge IDs table schemas and click Next.
5. In the Google Cloud Credentials For Amplitude section, upload the Service Account Key file. This file must be in JSON format and will be provided by Aampe. After the account service key is uploaded, fill out the Google Cloud bucket details in the Google Cloud Bucket Details section as provided by Aampe team
6. Click Next. Amplitude attempts a test upload to check that the entered credentials work. If the upload is successful, click Finish to complete the GCS destination configuration and activation.

Setting up recurring data export - Google Bigquery

1. Amplitude will directly write data to the Aampe BigQuery instance
2. In the Warehouse Destination section, click Big Query.
3. On the Getting Started tab, select the data you'd like to export and the export's cadence. You can Export events ingested today and moving forward, Export all merged Amplitude IDs, or both. For events, you can also specify filtering conditions to only export events that meet certain criteria.
4. Review the schemas for the Event table and the Merge IDs table and click Next.
5. Specify the BigQuery dataset to receive your Amplitude data, and upload the service account key file. This file must be in JSON format and will be provided by Aampe
6. Click Next. Amplitude attempts a test upload to test the credentials. If the upload is successful, click Finish to complete the BigQuery destination configuration and activation.

Amplitude export API

Aampe will pull data from the amplitude Export API

📘

This is only useful when data size is small. If data is larger you should go to Recurring data export

Requirements

• Your Amplitude API Key and Secret Key

Getting your API keys:

1. In your Amplitude workspace, click on Settings at the bottom left of your screen

2. Select Projects from the navigation bar that opens.
3. Select the project with the events you would like Aampe to ingest.

4. Copy your API Key and Secret Key

5. We will reach out to you to share your API key and secret key in a secured and encrypted manner

Real-time data push

To configure streaming from Amplitude to your webhook, you need the following information.

1. Webhook URL: Aampe will provide the webhook link
2. Header Information You can set up to five extra headers for the webhook request.

Reference: https://amplitude.com/docs/data/destination-catalog/webhooks

Steps:

1. Create a new sync
2. In Amplitude Data, click Catalog and select the Destinations tab.
3. In the Event Streaming section, click Webhook.
4. Enter a sync name, then click Create Sync.
5. Enter webhook URL: Enter the URL endpoint for the webhook. For example, https://mycompany.com/webhook.
6. Select headers:There are two preset headers for every webhook sync:
   1. Content-Type: application/json
   2. User-Agent: Amplitude/Webhook/1.0
      After these preset headers, you can define five more headers. To create a new header: Enter the header name on the left side text boxEnter the header value on the right side text boxA new header row appears if limit isn't reached
7. Configure event forwarding
8. Under Send Events, make sure the toggle is enabled ("Events are sent to Webhook") if you want to stream events to the webhook. When enabled, events are automatically forwarded to the webhook when they're ingested in Amplitude. Events aren't sent on a schedule or on-demand using this integration.
9. Define the event payload you want to receive in the webhook. You can choose to:
   1. Send the default Amplitude payload which follows the Amplitude event format.
   2. Customize the payload using an Apache FreeMarker template. See more details below.
      In Select and filter events choose which events you want to send. Choose only the events you need in the webhook. Transformed events aren't supported.
10. Configure user forwarding
    Under Send Users, make sure the toggle is enabled ("Users are sent to Webhook") if you want to stream users and their properties to the webhook. When enabled, users are sent to the webhook when an event is sent to Amplitude. Amplitude Identify API calls are also forwarded to the webhook. Users aren't sent on a schedule or on-demand using this integration.
11. Define the user payload you want to receive in the webhook. You can choose to:
    1. Send the default Amplitude payload which follows the Amplitude user format.
    2. Customize the payload using an Apache FreeMarker template. See more details below.
12. Enable sync
13. When satisfied with your configuration, at the top of the page toggle the Status to "Enabled" and click Save.

Events should now be streaming to Aampe.