If you've recently adopted Airbridge, we recommend importing your existing identifiers into Airbridge.
An app version with the Airbridge SDK must be released. Airbridge starts collecting events and data from the moment the SDK is installed.
The device IDs or user IDs you want to import must be ready in CSV format.
Secure a support channel to send the file and confirm the import: your Airbridge CSM or the Airbridge Help Center.
Submit your request at least 2 business days before the app version with the SDK is released.
When you first adopt Airbridge, for example by migrating from another solution, first events may spike right after adoption. This happens because Airbridge collects the identifiers it needs to determine first events for the first time. Importing your identifiers reduces the difference in your numbers before and after adoption.
When you import the identifiers of users who triggered a specific event, only that event is counted differently. See the examples below.
Note
The numbers start to change when a user updates to the app version with the Airbridge SDK. From that point on, the Airbridge SDK can collect events and data.
When you import the identifiers of users who triggered the app install event, you can distinguish users who already installed the app from users installing it for the first time. This import affects only the app install event. To distinguish first events for other events, import the identifiers for those events separately.
When a user who already installed the app updates to the app version with the Airbridge SDK and opens the app, the event is counted differently depending on whether you imported that user's identifier:
When you import the identifiers of users who triggered the Order Complete event, you can distinguish users who purchased before from users purchasing for the first time. This import affects only the Order Complete event. To distinguish first events for other events, import the identifiers for those events separately.
When a user who purchased before updates to the app version with the Airbridge SDK and opens the app, the event is counted differently depending on whether you imported that user's identifier:
Airbridge uses two main identifiers to determine first events: device ID and user ID.
In Airbridge reports, when you select the Is First Event per Device ID or Is First Event per User ID group-by, Airbridge determines first events based on each group-by's criterion. See the table below.
For example, suppose you imported only the device ID of existing user A, who has a purchase history, and didn't import their user ID. After user A updates to the app version with the Airbridge SDK and makes their first purchase in the app, first events are determined by group-by as follows:
Is First Event per Device ID: User A's device ID exists, so the event is not counted as a first event and returns false.
Is First Event per User ID: User A's user ID does not exist, so the event is counted as a first event and returns true.
Note
Airbridge determines first events only for events triggered by users whose identifiers were imported. Events triggered by users whose identifiers were not imported are unaffected.
Import device IDs, user IDs, or both, depending on what you want to measure.
Airbridge sends the events that occur first, based on device ID, via postback. So if you want to reconcile ad spend or optimize campaigns based on the events that occur first in Airbridge after adoption, import device IDs.
Follow the steps below to import your collected device IDs into Airbridge as a CSV file.
Enter your collected device IDs into the example CSV file below, following the rules. If you don't follow the rules, the data won't be processed correctly.
Attention
Submit your request at least 2 business days before the app version with the Airbridge SDK is released.
Send the CSV file with your device IDs, prepared according to the rules, to your Airbridge CSM. If you don't have a designated CSM, send it through the Airbridge Help Center. The import takes some time. Check whether the import is complete with your Airbridge CSM or support representative.
Attention
The import takes at least 2 business days. During this period, don't run ad campaigns or promotions that could collect a large volume of new identifiers. Identifiers collected during this period are not imported, so some events may be incorrectly counted as first events.
Airbridge determines first events for both app events and web events based on user ID. So if you want to measure first events across app and web on a per-user basis, import user IDs.
Follow the steps below to import your collected user IDs into Airbridge as a CSV file.
Enter your collected user IDs into the example CSV file below, following the rules. If you don't follow the rules, the data won't be processed correctly.
Attention
Submit your request at least 2 business days before the app version with the Airbridge SDK is released.
Send the CSV file with your user IDs, prepared according to the rules, to your Airbridge CSM. If you don't have a designated CSM, send it through the Airbridge Help Center. The import takes some time. Check whether the import is complete with your Airbridge CSM or support representative.
Attention
The import takes at least 2 business days. During this period, don't run ad campaigns or promotions that could collect a large volume of new identifiers. Identifiers collected during this period are not imported, so some events may be incorrectly counted as first events.
Identifier imported | How the event is counted | Effect on app install count |
|---|---|---|
No | When the user opens the app after updating, Airbridge has no collected data for the user, so it counts as a first app open event. A first app open event counts as an app install event, so the app install count may temporarily increase. | App install count increases |
Yes | When the user opens the app after updating, Airbridge has collected data for the user, so it counts as a repeat app open event. A repeat app open event counts as an app open event, so the app install count is unaffected. | App install count stays stable |
Identifier imported | How the event is counted | Effect on first Order Complete count |
|---|---|---|
No | When the user makes a purchase after updating, Airbridge has no collected data for the user, so it counts as a first Order Complete event. It counts as a first Order Complete event even if the user purchased before, so the first Order Complete count may temporarily increase. | First Order Complete count increases |
Yes | When the user makes a purchase after updating, Airbridge has collected data for the user, so it counts as a repeat Order Complete event. If the user purchased before, it counts as a repeat Order Complete event, so the first Order Complete count is unaffected. | First Order Complete count stays stable |
Group-by | First-event criterion | Event types you can check |
|---|---|---|
Is First Event per Device ID | Device ID | App events |
Is First Event per User ID | User ID | App events, web events |
Measurement goal | Recommended identifier | Scope of effect |
|---|---|---|
Ad spend reconciliation or app campaign optimization is the priority | Device ID | First events for app events |
Measuring app and web events together on a per-user basis | User ID | First events for app and web events |
Using both | Device ID and user ID, each in a separate file | Both of the above |
Rule | Details |
|---|---|
File name | · Format: · Example: |
File rules | · Device ID types such as GAID, IDFA, and IDFV are not distinguished. · Maximum file size is 500 MB. · You can upload multiple files at once. · Keep device IDs in a separate file from user IDs. |
Data period | · We recommend importing device IDs collected within the last 12 months. · You can adjust the collection period to fit your marketing campaign. For example, to count users who haven't purchased in over 6 months the same as users who have never purchased, import the identifiers of users who triggered the Order Complete event in the last 6 months. |
Data format | · Format: enter each ID as a version 4 UUID. · Example: |
Data arrangement | · Enter data starting from cell A1. · Use only column A. Don't use columns B, C, and so on. · Enter only device IDs. Don't enter any information other than device IDs. |
Rule | Details |
|---|---|
File name | · Format: · Example: |
File rules | · Maximum file size is 500 MB. · You can upload multiple files at once. · Keep user IDs in a separate file from device IDs. |
Data period | · We recommend importing user IDs collected within the last 12 months. · You can adjust the collection period to fit your marketing campaign. |
Data format | · Format: don't include spaces or double quotation marks ( · Example: |
Data arrangement | · Enter data starting from cell A1. · Use only column A. Don't use columns B, C, and so on. · Enter only user IDs. Don't enter any information other than user IDs. |
Was this helpful?