Import RudderStack data into Amplitude

What it is

RudderStack is a customer-data-pipeline tool: applications send events to RudderStack once, and RudderStack fans them out to whichever downstream destinations are configured - a warehouse, other analytics tools, marketing platforms. Adding Amplitude as a RudderStack destination means Amplitude receives a copy of that same event stream, mapped through RudderStack's connection settings rather than through Amplitude's own SDK calls in your codebase.

This is the inverse relationship of instrumenting Amplitude directly: instead of Amplitude's SDK being the point of capture, RudderStack is, and Amplitude becomes one of potentially several places that data lands.

When you need it

• An organization has already standardized instrumentation on RudderStack (often for warehouse-first or self-hosted data-pipeline reasons) and wants to add Amplitude as an analysis layer without asking engineering to add a second, parallel SDK integration.
• You're evaluating Amplitude and want to pilot it against real production event volume with minimal engineering lift, since routing an existing RudderStack stream to a new destination is typically a configuration change, not a code change.
• A compliance or infrastructure requirement mandates a single, centrally-governed event pipeline (RudderStack) rather than multiple vendor SDKs embedded directly in application code, and Amplitude needs to fit into that architecture rather than around it.

Implementation, done properly

1. Before connecting anything, audit RudderStack's existing tracking plan - event names, property types, and identity fields - because whatever inconsistency already exists there (duplicate event names, untyped properties) will arrive in Amplitude exactly as-is; this integration doesn't clean data in transit.
2. Add Amplitude as a destination in RudderStack's dashboard, authenticated with an Amplitude API key scoped to the correct project (and correct environment - keep a staging RudderStack destination pointed at a staging Amplitude project, not production, for testing the connection).
3. Map RudderStack's identity fields (`userId`, `anonymousId`) to Amplitude's user ID and device ID model explicitly - getting this mapping wrong is the most common cause of an Amplitude instance where the same real person appears as multiple disconnected users.
4. Decide deliberately whether RudderStack's `track`, `identify`, `page`, and `screen` calls should all forward to Amplitude, or only a subset - forwarding every call type by default, including ones Amplitude doesn't use meaningfully, adds event volume (and cost) without adding analytical value.
5. Run the connection against a low-volume test event first, confirm it in Amplitude, and only then enable it for the full production event stream - reversing a bad full-volume connection after the fact means cleaning up a project's worth of miscategorized historical data.

How to verify it worked

1. In RudderStack's own event delivery logs, confirm events routed to the Amplitude destination show a successful delivery status, not just that they were accepted into RudderStack's pipeline.
2. In Amplitude's Events explorer, confirm the events arriving match RudderStack's tracking plan in name and property shape - specifically check that property types (string vs. number vs. boolean) survived the trip, since a type mismatch is a common failure mode between pipeline tools and Amplitude's typed property system.
3. Pick one real user, trigger a sequence of actions through the actual product (not a synthetic test event), and confirm that same sequence appears correctly ordered and correctly attributed to one Amplitude user profile.
4. Compare total daily event volume between RudderStack's own delivery metrics and Amplitude's ingested count for the same day - a persistent, non-trivial gap indicates either a filtering rule in the RudderStack destination configuration or an Amplitude-side sampling or plan-volume limit worth checking against current account settings.

Related: Amplitude alternatives and comparisons · Setting up Amplitude in React, React Native, and Expo · Amplitude implementation sprint