Connectors / Service / Amplitude



Amplitude is a product analytics service that makes it easier for companies to understand user behaviour, ship the right features and improve business outcomes.


Whether you want to understand how users are navigating through your application, which features engage them the most, or how to improve long-term user retention, Amplitude helps you answer questions critical to your product development strategy. It’s also the only analytics solution built to meet the needs of modern product teams, with real-time analytics, cross-platform tracking, powerful behavioural analytics, and Enterprise-level security and customer support.


When using the Amplitude connector, a new authentication has to be created in the step editor. Drag an Amplitude connector in the workflow and click on the 'New Authentication' button.

To create a new authentication you will need an API key from Amplitude platform.

To get the Api key you will have to create an Amplitude account. One way to get the API key is to go to the main Analytics Amplitude website and click the 'Explore demo now' button.

Add your email address in the next popup window and check you email inbox for the confirmation link.

After clicking the link in your email you will be provided with another window that will request for your details to finish creating your account.

The API key can be found in your project's Settings page.

Add the API key in the Authentication window and click the 'Add authentication' button.

Available Operations

The examples below show one or two of the available connector operations in use.

Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.

Example usage - Create or update user

In the API docs this operation can be found under 'Identify API'.

This operation will update an existent user but if you send a request with a user ID that is not in the Amplitude system yet, then the user tied to the user ID will not be marked new until their first event.

The following screenshot shows how you would create or update a user using jsonpaths such as $.steps.trigger.body.user-id which pull in data from a previous step in your workflow.

In this case the workflow has been triggered by a webhook event so we are able to pull in the required values for creating/updating the user:

If the data was not being pulled in from the trigger, but from a previous service connector step such as Segment, the datapath might be something like $

Use the 'Debugger' by clicking the 'Debug' button at the top of the page to check if the operation was successful.

Example usage - Create attribution event

In the Amplitude API docs this operation can be found under 'Attribution API'.

An attribution event can be created either for IOS or Android. Just fill in the input fields and click the 'Run workflow' button.

Example usage - Batch create events

In the API docs this operation is named 'Batch Event Upload API'.

The Batch Event Upload endpoint can be used to send data directly from your server. This endpoint is recommended for Customers that want to send large batches of data at a time, for example through scheduled jobs, rather than in a continuous realtime stream. Due to the higher rate of data that is permitted to this endpoint, data sent to this endpoint may be delayed based on load.

Please see our guide to using batch update operations for suggestions on using our CSV Reader to manage your batches of data.

The properties panel for the operation shows the fields that need to be populated for each event:

Use the 'Debugger' by clicking the 'Debug' button at the top of the page to check if the operation was successful.

All Operations

Latest version: