Skip to main content

Amplitude - Event Ingestion

Send events and track user behavior with Amplitude's HTTP V2 API. This connector is used for ingesting events, identifying users, tracking groups, and sending attribution data from your backend to Amplitude.

When to Use This Connector​

Use this connector when you need to:

  • Send events to track user actions and behavior
  • Import historical event data in bulk
  • Update user properties without sending events
  • Track group/account properties (B2B analytics)
  • Send attribution data for marketing campaigns

For querying analytics data or accessing user profiles, see Amplitude Overview for other connector options.

Authentication​

This connector uses API Key authentication passed in the request body (not in headers).

  • Credential Format: Just your API key
  • Example: abc123xyz789

General Settings​

Before using the connector, configure your region:

  • Region - Select your Amplitude data region:
    • us - Standard US region (most common)
    • eu - European Union region for EU data residency

Your region determines which API endpoints are used.

Setting up Authentication​

Step 1: Get Your API Key​

  1. Go to amplitude.com and log in to your account
  2. Click on Settings (gear icon) in the top right corner
  3. Scroll to Connections → API Keys
  4. Click Generate API Key → Give it a name (e.g., "Webrix")
  5. Copy the API Key value

Step 2: Configure in Webrix/MCP​

Enter only your API key (not the secret key):

abc123xyz789

Note: For this connector, you only need the API key. The secret key is not used for event ingestion.

Available Tools​

This connector provides 5 tools for event ingestion:

1. Send Events​

Track user actions and events from your backend using Amplitude's HTTP V2 API. Supports event properties, user properties, and device/user identification.

2. Send Batch Events​

Send up to 2,000 events in a single request for bulk ingestion. Ideal for importing historical data or handling high-volume event streams.

3. Identify User​

Update user properties without sending an event. Use this to enrich user profiles with attributes like email, name, plan type, or custom properties.

4. Group Identify​

Set or update properties for groups (companies, organizations, accounts). Essential for B2B analytics to track account-level attributes.

5. Send Attribution Event​

Send attribution data to track campaign performance and user acquisition sources. Attribute users to specific marketing campaigns, channels, or UTM parameters.

Regional Differences​

US Region (Standard)​

  • API Endpoint: api2.amplitude.com
  • All ingestion features available

EU Region​

  • API Endpoint: api.eu.amplitude.com
  • All ingestion features available
  • Data stays within EU boundaries for compliance

Troubleshooting​

"Invalid API key"​

Cause: The API key is incorrect or has been regenerated.

Solution:

  • Verify you copied the complete API key from Amplitude
  • Ensure there are no extra spaces or line breaks
  • Check that the API key hasn't been regenerated
  • Make sure you're using the API key from the correct Amplitude project

"Region mismatch" or "404 Not Found"​

Cause: You selected the wrong region for your Amplitude project.

Solution:

  • Check your Amplitude project's region in the project settings
  • Update the Region setting in the connector to match (us or eu)
  • EU projects must use the eu region setting

"Authentication failed"​

Cause: The API key is not being sent correctly in the request body.

Solution:

  • This connector automatically includes the API key in the request body
  • Verify your API key is correct in the connector settings
  • Check that you're using the correct region setting

Rate Limits​

Amplitude has rate limits on its APIs:

Ingestion APIs

  • 1,000 events per second per project
  • Up to 2,000 events per request (for batch operations)
  • 500,000 events per device/user per 24 hours
  • User property updates limited to 1,800 per hour per user

Solution:

  • Use batch operations for bulk data (Send Batch Events)
  • Implement exponential backoff for rate limit errors (429 status)
  • For very high volume, consider batching events before sending
  • Monitor your ingestion rate and adjust as needed

Best Practices​

  1. Event Naming: Use consistent, descriptive event names (e.g., "Button Clicked", not "btn_click")

  2. User Identification: Always include either user_id or device_id with events

  3. Deduplication: Use insert_id for critical events to prevent duplicates

  4. Batch Operations: For high-volume data, use Send Batch Events instead of multiple Send Events calls

  5. Timestamp Format: Use milliseconds since epoch for event timestamps

  6. Property Structure: Keep event and user properties flat and simple for easier analysis

  7. Rate Limiting: Implement retry logic with exponential backoff for production applications

  8. Testing: Test with small data sets first before sending large volumes

Additional Resources​