# Amplitude Destination

## About this integration

Amplitude is a platform designed to track events and segment data on websites and mobile applications. With Amplitude, you can analyze user actions to gain valuable insights into the behaviors that drive engagement, retention, and conversion.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

[identify](/api/cdp/#operation/identify), [track](/api/cdp/#operation/track), [alias](/api/cdp/#operation/alias), [page](/api/cdp/#operation/page), and [group](/api/cdp/#operation/group)

Actions Amplitude

 We use Amplitude’s v2 API

While we show the schemas that we map data to below, you’ll need to check out Amplitude’s documentation to learn more about their API.

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Amplitude** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Api Key**: Amplitude project API key. You can find this key in the "General" tab of your Amplitude project.
        
    2.  **Secret Key**: Amplitude project secret key. You can find this key in the "General" tab of your Amplitude project.
        
    3.  **Endpoint**: The region to send your data.
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

### Log Event[](#log-event-cloud)

Default Trigger: `type = “track”`

Send an event to Amplitude.

### Identify User[](#identify-user-cloud)

Default Trigger: `type = “identify”`

Set the user ID for a particular device ID or update user properties without sending an event to Amplitude.

### Map User[](#map-user-cloud)

Default Trigger: `type = “alias”`

Merge two users together that would otherwise have different User IDs tracked in Amplitude.

### Group Identify User[](#group-identify-user-cloud)

Default Trigger: `type = “group”`

Set or update properties of particular groups. Note that these updates will only affect events going forward.

### Log Purchase[](#log-purchase-cloud)

Default Trigger: `type = “track”`

Send an event to Amplitude.

### Log Event V2[](#log-event-v2-cloud)

Default Trigger: `type = “track”`

Send an event to Amplitude