Skip to main content
Airbridge gathers as many identifiers as possible and chooses the most suitable one for various purposes.

​
Types of Identifiers Used in Airbridge

Airbridge uses five identifiers. These are Airbridge Device ID, Airbridge Device ID (User Count), User ID, Cookie ID, and Airbridge ID.
  • Airbridge Device ID and Airbridge Device ID (User Count) identify app users, while Cookie ID identifies web users.
  • User ID is the ID a user provides when signing up for your service.
  • Airbridge ID is an identifier Airbridge generates for unified analysis of user journeys across app and web. When you set [Identifier] to User in Funnel, Retention, and Revenue reports, the Airbridge ID is used as the user identifier.

​
Airbridge Device ID

Airbridge Device ID identifies users by device.
  • Airbridge collects GAID and App Set ID on Android, and IDFA and IDFV on iOS.
  • Airbridge prioritizes GAID on Android and IDFA on iOS, and falls back to App Set ID and IDFV when the prioritized identifier isn’t available.
  • If neither identifier is available on a device, the Airbridge SDK assigns a Random Generated ID.
Below is a list of identifiers that Airbridge may use as candidates for the Airbridge Device ID.
These identifiers typically appear as 32-character alphanumeric strings, such as 38400000-8cf0-11bd-b23e-10b96e40000d.
NoteSince only one of the candidate identifiers is selected as the Airbridge Device ID, the identifier used may vary depending on the specific Airbridge feature.
Below are the Airbridge features where the Airbridge Device ID is used.

​
Airbridge Device ID (User Count)

Airbridge Device ID (User Count) identifies users by device. Airbridge uses this ID for features that count users or group users into cohorts for analysis. Because these analyses require a user to be recognized as the same user throughout the analysis period, Airbridge prioritizes identifiers that aren’t affected by a user’s advertising identifier settings.
  • Airbridge collects GAID and App Set ID on Android, and IDFA and IDFV on iOS.
  • Airbridge prioritizes App Set ID on Android and IDFV on iOS, and falls back to GAID and IDFA when the prioritized identifier isn’t available.
  • If neither identifier is available on a device, the Airbridge SDK assigns a Random Generated ID.
Below is a list of identifiers that Airbridge may use as candidates for the Airbridge Device ID.
These identifiers typically appear as 32-character alphanumeric strings, such as 38400000-8cf0-11bd-b23e-10b96e40000d.
NoteSince only one of the candidate identifiers is selected as the Airbridge Device ID (User Count), the identifier used may vary depending on the specific Airbridge feature.
Below are the Airbridge features where the Airbridge Device ID (User Count) is used.

​
User ID

User ID is used to identify users based on the information they provide when signing up or logging in to your service. If Airbridge can’t collect this information directly, the client must send the user ID via a server-to-server (S2S) integration. Below are the Airbridge features where the user ID is used. Cookie ID is used to identify users based on information stored in cookies in web environments. Below are the Airbridge features where the cookie ID is used.

​
Airbridge ID

Airbridge ID is used to identify users by utilizing both the user ID and the Airbridge device ID when available. It is primarily generated based on the user ID, and if the user ID is not available, it is generated based on the Airbridge device ID. Airbridge ID is created by Airbridge to track user journeys across both app and web environments. Below are the Airbridge features where Airbridge ID is used.

​
Determining first events

Airbridge determines whether an event is the first based on either the Airbridge device ID or the user ID.
When this GroupBy option is selected, Airbridge determines whether an app event is the first based on the Airbridge Device ID. If the event is the first based on the Airbridge Device ID, it is marked as true. If not, it is marked as false. If the Airbridge Device ID is missing or invalid, the value is shown as null.Refer to the example below.
When this GroupBy option is selected, Airbridge determines whether a web or app event is the first based on the user ID. If the event is the first based on the user ID, it is marked as true. If not, it is marked as false. If the user ID is missing or invalid, the value is shown as null.Refer to the example below.In this example, the Order Complete event that occurred in the app is the first event. Although the Order Complete event on the web is the first from the web’s perspective, it is not considered the first event because first-event determination takes both web and app events into account.

​
Understanding Identifiers Used in Airbridge

NoteThe identifiers in the scenarios below are simplified to facilitate your understanding; real-world identifiers are more complex.
Identifiers used in Airbridge are not always collected. For example, Airbridge Device ID may be unavailable due to LAT (Limited Ad Tracking) or ATT (App Tracking Transparency) policies. Similarly, the user ID may not be available if the user does not sign up or log into your service.

​
Determining unique users in reports

Unique users refer to distinct users in reports, excluding those counted multiple times based on identifiers.
In general, when a user uses multiple devices to use your service, multiple device IDs will be collected, as illustrated in the table below.
Table
Determining unique users
To generate the Airbridge ID, Airbridge ties each user ID (Rachel) to the respective device IDs (T, A, C).As a result, when using the user ID or the Airbridge ID, only 1 unique user is identified. When using the device ID, 3 unique users are identified because each device ID is considered to be a different user.
Multiple users may be sharing a single device, as illustrated in the table below.
Table
Determining unique users
To generate the Airbridge ID, Airbridge ties each of the 2 user IDs (Daniel, Amy) to the respective device ID (B).As a result, when using the user ID or the Airbridge ID, 2 unique users are identified. When using the device ID, only 1 unique user is identified.
Oftentimes, the user ID is not available because the user does not bother to sign in every time. Without the user ID to be matched with device IDs, the Airbridge ID is generated for each device ID, as illustrated in the table below.
Table
Determining unique users
Multiple users may be sharing a single device whose device ID is Z. However, because there are no multiple user IDs available, a separate Airbridge ID (302) is generated for the device ID (Z).As a result, when using the device ID or the Airbridge ID, 3 unique users are identified. When using the user ID, only 1 unique user is identified because users whose user ID is not available cannot be identified.
Real-world scenarios are often complex, as illustrated in the table below.
Table
Determining unique users
To generate the Airbridge ID, Airbridge ties each of the 3 user IDs (Tai, Sunny, Dana) to the respective device IDs (A, B, C, D, E). Note that there is a case where 1 user ID (Dana) is tied to 3 device IDs (C, D, E). For the user whose device ID is available but the user ID is not, a separate Airbridge ID (403) is generated for the device ID (F).As a result, when using the Airbridge ID, 4 unique users are identified. When using the user ID, 3 unique users are identified, and when using the device ID, 6 unique users are identified.