Airbridge supports a variety of identifiers for attribution and reporting purposes. The identifiers are primarily collected via the Airbridge SDK integrated into your app or website.
Airbridge supports 3 types of identifiers: device ID, user ID, and Airbridge ID.
ID Type |
Description |
|---|---|
Device ID | - The device ID is a unique identifier assigned to each device. |
User ID | - The user ID is a unique identifier assigned to each user account or to each user that can be uniquely identified via the information submitted when signing up. |
Airbridge ID | - The Airbridge ID is a unique identifier generated by consolidating the device ID and the user ID. Each user ID is tied to one or more device IDs to complete the picture. |
Random Generated ID
If the GAID or the IDFA cannot be collected or used due to Limit Ad Tracking (LAT) or App Tracking Transparency (ATT), Airbridge uses the IDFV or the Random Generated ID instead. The Random Generated ID is an identifier randomly generated by the Airbridge SDK.
Airbridge supports different identifiers for different purposes, as illustrated below.
You can use different identifiers in different reports. To use the user ID in the Active Users Report, select web metrics.
Airbridge Report |
Device ID |
User ID |
Airbridge ID |
|---|---|---|---|
Actuals Report | Supported | - | - |
Trend Report | Supported | - | - |
Reinstall Report | - | - | - |
Retention Report | Supported | - | - |
Funnel Report | Supported | - | Supported |
Revenue Report | Supported | - | - |
Active Users Report | Supported | Supported* | - |
Audience Manager | Supported | - | - |
The data displayed in the Airbridge reports may differ depending on the type of identifier used. Read on to learn how different identifiers are collected and used in Airbridge.
Note
The identifiers in the scenarios below are simplified to facilitate your understanding; real-world identifiers are more complex.
Note that not all types of identifiers are collected at all times. The device ID may not be collected under certain conditions. The user ID may not be collected if the user does not sign up or sign in.
The Airbridge ID is automatically generated by Airbridge when either the user ID or the device ID is collected.
Device ID |
User ID |
Airbridge ID |
|---|---|---|
T | Lyla | 100 |
A | David | 101 |
C | - | 102 |
- | Sunny | 103 |
Once the availability of different identifiers has been confirmed, Airbridge proceeds to determine unique users using the identifiers.
Refer to the scenarios below to understand the identification process.
In general, when a user uses multiple devices to use your service, multiple device IDs will be collected, as illustrated in the table below.
Device ID |
User ID |
Airbridge ID |
|---|---|---|
T | Rachel | 200 |
A | Rachel | 200 |
C | Rachel | 200 |
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.
Device ID |
User ID |
Airbridge ID |
|---|---|---|
B | Daniel | 56 |
B | Amy | 57 |
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.
Device ID |
User ID |
Airbridge ID |
|---|---|---|
X | Noel | 300 |
Y | - | 301 |
Z | - | 302 |
Z | - | 302 |
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.
Device ID |
User ID |
Airbridge ID |
|---|---|---|
A | Tai | 400 |
B | Sunny | 401 |
C | Dana | 402 |
D | Dana | 402 |
E | Dana | 402 |
F | - | 403 |
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.
Was this page helpful?