Skip to main content

Amplitude Feeds

Amplitude is a digital analytics platform that helps teams track user behavior, analyze product usage, and measure how features and experiments perform across web and mobile applications. The Amplitude Feeds connector is a source-only ELT connector that ingests Amplitude project data as feeds: raw event data retrieved through the Amplitude Export API using an incremental strategy, and the project's event types retrieved with a full-refresh strategy. Selected feeds are ingested in parallel on a configurable schedule.

Amplitude Feeds icon

Power end-to-end data operations for your Amplitude Feeds API with Nexla. Our bi-directional Amplitude Feeds connector is purpose-built for Amplitude Feeds, 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 Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Amplitude Feeds 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​

The Amplitude Feeds connector authenticates with HTTP Basic Authentication using an Amplitude project's API Key as the username and Secret Key as the password, as required by the Amplitude Export API. Both keys are scoped to a single Amplitude project, so create one Nexla credential per project you want to ingest.

To obtain your Amplitude credentials:

  1. Sign in to the Amplitude web app with a user that has a Manager or Admin role on the project. Amplitude notes that only Managers and Admins can generate, copy, and revoke API keys and generate secret keys.

  2. Click Settings in the lower-left navigation, then select Projects in the side navigation.

  3. Select the project whose data you want to ingest.

  4. On the General tab, locate the API Key and Secret Key sections, and use the Manage option to view and copy each key.

  5. Note the project name exactly as it appears in the project settings — you will enter it when creating the Nexla credential.

  6. Confirm your organization's data residency region. Standard (US) projects use the API base URL https://amplitude.com, and EU data residency projects use https://analytics.eu.amplitude.com.

The API Key identifies the project, but the Secret Key authenticates server-side APIs that read project data and must be kept private. If a Secret Key is compromised, delete it in the Amplitude project settings and generate a replacement.

The Amplitude Export API returns event data with a delay of about two hours after ingestion, supports a maximum query window of 365 days per request, and caps responses at 4GB. For details, see the Amplitude Export API documentation and the Amplitude keys and tokens guide.

Authenticate​

Credentials required​

Authenticate using your Amplitude API Key and Secret Key

FieldRequiredSecretDescription
Data Residency RegionYesNoSelect 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 KeyYesNoYour Amplitude API Key. This can be found in the Amplitude project settings.
Secret KeyYesYesYour Amplitude Secret Key. This can be found in the Amplitude project settings.
Project NameYesNoYour Amplitude project name. This can be found in the Amplitude project settings.

Create a credential in Nexla​

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

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

    Resource descriptions are recommended but are not required. Use them to identify the Amplitude project and data residency region represented by this credential.

  3. Select your Amplitude data residency region in the Data Residency Region field. Choose Standard for projects served from https://amplitude.com, or EU for projects on EU data residency served from https://analytics.eu.amplitude.com. This selection determines the API base URL Nexla uses for all requests.

  4. Enter the project's API Key in the API Key field. This key was obtained from the Amplitude project settings in Prerequisites.

  5. Enter the project's Secret Key in the Secret Key field. Nexla combines the API Key and Secret Key as HTTP Basic Authentication credentials for all Amplitude API requests. The Secret Key is treated as a secret and stored securely.

  6. Enter the Amplitude project name in the Project Name field, exactly as it appears in the project settings. Nexla attaches this project name to ingested event type records so data from multiple projects can be distinguished downstream.

  7. Click the Save button at the bottom of the overlay. Nexla validates the credential by calling the Amplitude events list endpoint. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source​

How This Connector Works​

The Amplitude Feeds connector is a source-only ELT connector. Rather than configuring one endpoint at a time, you select the Amplitude objects you want from a catalog of feeds, and Nexla ingests each selected object as its own feed.

  • Discovery: When you create the source, Nexla discovers the feeds available from your Amplitude project and presents them for selection.

  • Sync strategies: Each feed uses the strategy suited to its data. The Event feed uses an incremental (auto-increment) strategy that advances a cursor on each run, while the Event Type feed uses a full-refresh strategy that reads the complete current list on every run.

  • Parallel ingestion: Selected feeds are ingested in parallel on the same schedule.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Amplitude Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Amplitude project and click Next; or, create a new Amplitude Feeds credential for use in this flow. The credential determines the project and the data residency region, so use the credential that matches the project you want to ingest.

Select the Objects to Ingest​

After authenticating, Nexla lists the objects available from the connector. Select one or both of the following objects. Each selected object becomes its own feed.

  • Event — Raw event data exported from the project through the Amplitude Export API (/api/2/export). Amplitude returns the export as a zipped archive of JSON event records, which Nexla unpacks and ingests row by row. This feed is incremental: each run exports events from the cursor position of the previous run up to the current time. Records are keyed by the combination of id, device_id, and client_event_time.

  • Event Type — The list of event types defined in the project, retrieved from the Amplitude events list endpoint (/api/2/events/list). This feed is full-refreshed on every run, and each record is tagged with the credential's project name. Records are keyed by the combination of id and project_name.

For the Event feed, you can configure the Lookback Time: Event Export setting, which controls the earliest point from which the first run exports events. Enter the value in YYYYMMddTHH format — for example, 20251022T10 for 2025-10-22 10:00:00. Subsequent runs continue from the cursor recorded by the previous run.

Amplitude makes event data available for export roughly two hours after ingestion, so the most recent events may not appear until a later run. If no events exist in the requested window, the Export API returns no data for that run.

Schedule and Activate​

  • Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, the Event feed ingests newly exported events since the previous run, and the Event Type feed is full-refreshed.

Reference​

For event schemas, export behavior, and endpoint details, see the Amplitude Export API documentation.