Amplitude

Jeongwon KimWritten by Jeongwon Kim,

Airbridge supports integration with Amplitude. With the integration, event data is sent to Amplitude, allowing you to leverage the data from Airbridge for more in-depth product analysis with Amplitude.

Note

Once the integration is complete, the attribution data collected by Airbridge is sent to Amplitude’s US server. If you want the data to be sent the EU server, contact your CSM.

Integration Methods: V1 and V2

Attention

To implement the integration with Amplitude, choose one integration method between V1 and V2 methods. When using both methods, event duplication may occur.

Airbridge supports 2 different methods for integrating with Amplitude. Select one of the V1 or V2 integration methods. Refer to the table below for details of the V1 and V2 methods.

V1

V2

API

Attribution API

HTTP V2 API

Pre-setup

Add codes into the Amplitude SDK to collect Ad ID (GAID for Android, IDFA for iOS, IDFV)

Add codes into the Airbridge SDK to get Amplitude Device ID

Events that can be sent

Target Events

All events (Target Events and In-app Events)

- Standard Events

- Custom Events collected more than once

Event properties that can be sent

12 event properties that are preset

Event properties you select from the 124 properties

User matching method

Ad ID is used. In case of failure, the Ad ID is discarded after 72 hours.

Identifiers are used in given priority. In case of failure, the user is logged as a new user.

Implementing Integration Through the V1 Method

The V1 method works through the attribution API provided by Amplitude. Airbridge starts sending the Target Event data collected after the integration implementation is complete with Amplitude. The event properties sent to Amplitude are logged as user properties in Amplitude.

Event properties other than the ones of Target Events cannot be sent to Amplitude using the V1 integration method. Implement the V2 integration method to send in-app events and their event properties to Amplitude.

Pre-setup for integration

The following steps must be completed to implement the integration through the V1 method.

Providing the API Key to Airbridge

1. Navigate to [Integrations]>[Third-party Integration] and select Amplitude V1.

2. Enter the API Key copied from the Amplitude dashboard.

3. Switch on the Send User Properties toggle. The properties of the Target Events will be sent to Amplitude, and the user property names will be prefixed with [Airbridge] in Amplitude.

Implementing Integration Through the V2 Method

The V2 method works through the attribution HTTP V2 API provided by Amplitude. Airbridge starts sending the Target Event and in-app event data collected after the integration implementation is complete with Amplitude. The event properties sent to Amplitude are logged as user properties in Amplitude.

The V2 method allows sending more event data to Amplitude than the V1 method. Before implementing the integration through the V2 method, check whether the event data you want to send from Airbridge to Amplitude is already being collected through the Amplitude SDK. Note that event duplication may occur if the event data sent from Airbridge to Amplitude is also collected through the Amplitude API.

Pre-setup for integration

The following steps must be completed to implement the integration through the V2 method.

Adding connections

Attention

Make sure the required codes are added to the Airbridge SDK before providing the API Key to the Airbridge dashboard. Otherwise, the integration's implementation will not be complete.

Refer to the following article from the developer guide and share it with your developer.

1. Navigate to [Integration]>[Third-party Integration] and select Amplitude V2.

2. Click Add Connection.

Connections

You can add multiple connections to send events to Amplitude. However, only a single connection can be enabled at a time. For example, if you want to switch to a new connection, you need to disable the current connection and enable the new connection to send data to Amplitude.

3. Enter the API Key copied from the Amplitude dashboard. If you have registered API keys with Airbridge before, you can also select from the list of already registered API keys.

4. Select the events you want to send to Amplitude. All events are selected by default. Click Select All or Clear All to select or clear all events. Standard Events are available for selection by default, whereas Custom Events are available only when Airbridge has collected the event at least once.

5. Select the event properties you want to send to Amplitude. Click Select All or Clear All to select or clear all events. The following event properties are sent to Amplitude by default and cannot be deselected.

  • Event Category, Event Timestamp, Device ID, Platform, User ID

Refer to the information below for event properties that can be also used as user properties in Amplitude when imported.

6. Configure the delivery rules. In the [Event Name Settings], select the event name rules for the events to be displayed in Amplitude when imported.

  • Send event name without [Airbridge] prefix: All events are imported to Amplitude with the event name used in Airbridge. This is the default settings.

  • Send event name with [Airbridge] prefix: All events are imported to Amplitude with the event name that is prefixed with [Airbridge]. In this way, the events sent from Airbridge can be easily distinguished from other events within Amplitude.

Click Add Rules to add delivery rules at the event and property level.

Note

All properties are imported to Amplitude with the property name used in Airbridge, without [Airbridge] as a prefix.

7. Configuring additional delivery rules is optional. You can create a connection without adding any delivery rules.

If you want to add a delivery rule, enter the rule name and configure the rule conditions. The rule name must be unique.

You can add multiple conditions to create a delivery rule. For example, if the delivery rule has been configured like in the image below, the Install (App) events are not sent to Amplitude if the Channel property is example_channel, and the Campaign property is not example_campaign.

To configure different conditions for one event or property, add additional delivery rules.

8. Click Add Connection when you are done. Note that the events that are used for configuring the delivery rules cannot be unchecked from the events selector in the [Select Events] step. You must first delete the relevant delivery rule if you don’t want to send certain events.

9. The default status for a new connection is Inactive. Click Activate > if you want to activate the connection.

10. Click Activate to activate the connection. When activated, the configured events and properties are sent to Amplitude.

Supported features

Edit connection settings

Click the connection to edit its connection settings, regardless of whether it is active. You can edit the event schema, delivery rules, and connection info. Be cautious when editing the connection settings of an active connection, as unintended events and event properties may be sent to Amplitude.

Managing connections

Using Airbridge Data in Amplitude

Once the integration is successfully implemented, Airbridge data is made available in Amplitude.

The user properties sent from Airbridge using the V1 integration method have their names prefixed with [Airbridge]. The events sent from Airbridge using the V2 integration method will have their names prefixed with [Airbridge] only when configured to do so.

Refer to the information below to learn how to use Airbridge data in Amplitude.

Attention

Was this page helpful?

Have any questions or suggestions?