Amplitude

Amplitude is a product analytics platform that helps businesses understand user behavior through event tracking and analytics. The Amplitude connector enables you to extract raw event data and analytics from Amplitude using the Export API, allowing you to analyze user behavior, track events, and export data for further processing.

Power end-to-end data operations for your Amplitude API with Nexla. Our bi-directional Amplitude connector is purpose-built for Amplitude, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Amplitude or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Amplitude workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Amplitude credential, you'll need to obtain API credentials from your Amplitude project settings. The Amplitude Export API uses Basic Authentication with an API Key and Secret Key.

Amplitude Account Setup

To obtain the required API credentials for Amplitude:

1. Sign in to Amplitude: Navigate to https://amplitude.com/ and sign in to your Amplitude account. If you don't have an account, you can create one by clicking Sign up and following the registration process.

2. Access Project Settings: Once signed in, navigate to your Amplitude project. Click on your profile icon in the top right corner, then select Settings from the menu, or navigate directly to your project settings.

3. Navigate to API Keys: In the project settings, look for the API Keys or Project Settings section. This section contains your API credentials for accessing the Amplitude Export API.

4. Obtain API Key and Secret Key: In the API Keys section, you'll find:

   • API Key: Your project's API key (also known as the API Key ID)
   • Secret Key: Your project's secret key (also known as the API Secret)

5. Copy Credentials: Copy both the API Key and Secret Key immediately. Store these credentials securely, as you'll need them when creating the credential in Nexla.

Amplitude API credentials are project-specific. Each Amplitude project has its own API Key and Secret Key. Ensure you're using the credentials from the correct project. The API Key and Secret Key are used together for Basic Authentication in API requests. For complete information about Amplitude API authentication, see the Amplitude API Authentication Documentation.

Data Residency Region

Amplitude supports different data residency regions, which affect the base URL for API requests:

• Standard: Uses https://amplitude.com as the base URL (default)
• EU: Uses https://analytics.eu.amplitude.com as the base URL for EU data residency

Select the appropriate region based on where your Amplitude project data is stored. This information is typically available in your Amplitude project settings.

API Access Requirements

Amplitude Export API access requires:

• Valid Amplitude Account: You must have an active Amplitude account
• Project Access: You must have access to the Amplitude project
• API Key: Your project's API key from project settings
• Secret Key: Your project's secret key from project settings

The Amplitude Export API uses Basic Authentication, where the API Key is used as the username and the Secret Key is used as the password. All API requests must use HTTPS.

For complete information about Amplitude Export API authentication and getting started, see the Amplitude Export API Documentation.

Authenticate

Credentials required

Authenticate using your Amplitude API Key and Secret Key.

Field	Required	Secret	Description
Data Residency Region	Yes	No	Select your Amplitude data residency region. This will affect the base URL for the API. Allowed values: Standard (Standard data residency region, accessible through API base URL https://amplitude.com); EU (EU data residency region, accessible through API base URL https://analytics.eu.amplitude.com)
API Key	Yes	No	Your Amplitude API Key from the project settings
Secret Key	Yes	Yes	Your Amplitude Secret Key from the project settings
Project Name	Yes	No	Your Amplitude project name. This can be found in the Amplitude project settings.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Amplitude

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Data Residency Region: Select your Amplitude data residency region from the Data Residency Region pulldown menu. Available options are:

   • Standard: For standard data residency (base URL: https://amplitude.com)
   • EU: For EU data residency (base URL: https://analytics.eu.amplitude.com)

   This selection determines the base URL that will be used for API requests.

4. API Key: Enter your Amplitude API Key in the API Key field. This is your project's API key from the Amplitude project settings. The API Key is used as the username in Basic Authentication.

5. Secret Key: Enter your Amplitude Secret Key in the Secret Key field. This is your project's secret key from the Amplitude project settings. The Secret Key is used as the password in Basic Authentication.

   The API Key and Secret Key are sensitive credentials that provide access to your Amplitude project data. Keep these credentials secure and never share them publicly or commit them to version control systems. The credentials are used together for Basic Authentication in all Amplitude API requests.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Amplitude connector tile, then select the credential that will be used to connect to the Amplitude instance, and click Next; or, create a new Amplitude credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Amplitude endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Export Events

This endpoint exports raw event data from Amplitude as compressed JSON archives. Use this endpoint when you need to extract large volumes of event data, perform custom analysis, or sync event data to other systems.

• Enter the start date in the Start Date field in the format YYYYMMDDTHH (e.g., 20251001T00). This defines the beginning of the export time range. The default is {now-1} (one day ago).
• Enter the end date in the End Date field in the format YYYYMMDDTHH (e.g., 20251002T00). This defines the end of the export time range. The default is {now} (current time).
• Enter a schedule in the Schedule field to specify when this data source should run. The schedule uses cron expression format.
• The endpoint returns compressed ZIP archives containing JSON files with event data. Nexla automatically extracts and processes the JSON files from the ZIP archive.

The export endpoint is designed for bulk data extraction and returns data in compressed ZIP format. The date format uses YYYYMMDDTHH (e.g., 20251001T00 for October 1, 2025 at midnight). For complete information about exporting events, see the Amplitude Export API Documentation.

Get Event Types

This endpoint retrieves metadata about event types in your Amplitude project. Use this endpoint when you need to discover available event types, analyze event schemas, or build dynamic workflows that operate on different event types.

• Enter a schedule in the Schedule field to specify when this data source should run. The schedule uses cron expression format.
• The endpoint returns event type metadata including event names, descriptions, and properties.

This endpoint is useful for discovering available event types before configuring more specific endpoints. The returned data includes event type information that can be used to understand your Amplitude project structure. For complete information about retrieving event types, see the Amplitude Dashboard REST API Documentation.

Get User Activity

This endpoint retrieves user activity data for a specific user. Use this endpoint when you need to analyze individual user behavior, track user journeys, or extract activity data for specific users.

• Enter the Amplitude User ID in the Amplitude User ID field. This should be the Amplitude User ID or Device ID for the user whose activity you want to retrieve.
• Enter a schedule in the Schedule field to specify when this data source should run. The schedule uses cron expression format.
• The endpoint uses pagination to handle large volumes of user activity data efficiently, automatically fetching additional pages as needed.
• Each activity record includes event information, timestamps, and user properties.

User activity data includes all events associated with a specific user. The endpoint supports pagination to handle users with extensive activity history. You can find user IDs by using the "User Search" endpoint first. For complete information about retrieving user activity, see the Amplitude User Activity API Documentation.

User Search

This endpoint searches for users and retrieves their Amplitude IDs. Use this endpoint when you need to find users by their user ID, discover Amplitude user identifiers, or build workflows that require user ID lookups.

• Enter the User ID to search for in the User ID to Search field. This should be the user_id (string) that you want to search for in Amplitude.
• Enter a schedule in the Schedule field to specify when this data source should run. The schedule uses cron expression format.
• The endpoint returns matching user records including their Amplitude IDs and user properties.

User search is useful for finding Amplitude user identifiers when you have external user IDs. The search returns matches including the Amplitude ID that can be used with other endpoints like "Get User Activity". For complete information about user search, see the Amplitude User Search API Documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Amplitude data sources can also be manually configured to ingest data from any valid Amplitude API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request headers and parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Amplitude API URLs typically follow the format: https://amplitude.com/api/2/export for event exports, or https://amplitude.com/api/2/events/list for event types. Replace the base URL with your data residency region if using EU (e.g., https://analytics.eu.amplitude.com).

You do not need to include authentication headers (Basic Authentication with API Key and Secret Key) as these are automatically included from your credentials; however, you may need to include additional headers for specific Amplitude API features, and the Content-Type header should be set to application/json for most Amplitude API requests. For Amplitude API responses, the data path varies by endpoint: use $.data[*] to extract individual event type objects from event list responses, $.events[*] to extract individual event objects from user activity responses, and $.matches[*] to extract matching user records from user search responses. For complete information about Amplitude API endpoints and response formats, see the Amplitude Export API Documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Amplitude data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.