Learn how to import your organization's existing install attribution information into the Singular platform.
What are attribution data imports?
When you switch from a different attribution provider to Singular, we offer you the unique option of importing your apps' existing user base.
This import allows Singular to mark these users as existing users and keep install numbers accurate. It helps, but does not prevent, an "organic spike" when switching to Singular while also protecting you from being billed twice for the same app install on the respective device.
Note that you must import the historical data into your Singular account before any apps are receiving live traffic in Singular. If you release your app to the app stores before you load historical data, there will be spikes in organic installs and the attribution source for some of the devices will be incorrect.
How are your existing users identified by Singular?
For Android devices:
- The device's Google Advertising ID (GAID) or Android App Set ID (ASID) is REQUIRED!
For iOS devices:
- The device's Identifier for Vendor (IDFV) is REQUIRED!
- The device's Identifier for Advertising (IDFA) is optional but should be provided if you have it!
Important! Devices without valid identifiers will not be imported.
Singular does not use Custom User IDs for the import process (or for any attribution functionality), even if you share Custom User IDs with Singular.
Note: If you have internal BI postbacks configured, these users you import will have "Imported Users" in the Network field.
How does Singular ingest the data?
Singular will ingest the data you provide as long as the data is formatted following the data file specifications below:
Data File Specifications:
- The filename format should start with the Date of the file generation in YYYYMMDD and specify the App Name and Platform. YYYYMMDD_App-Name_Platform_Import.csv
Example: 20170115_SingularDeviceAssist_iOS_Import.csv
- Data file should be in Unix-encoded CSV (comma-separated) format.
- Data file must be formatted correctly without errors.
- Data files must be ≤ 2GB in size each. For large datasets, you may split the files.
- All data files must include the proper header row as defined in the specifications.
- All UUIDv4 identifiers (e.g., IDFA, IDFV, GAID, ASID) must be 36 characters in length.
- Duplicate rows must be removed.
- Rows without a valid device identifier will not be imported.
- Leading and trailing spaces must be removed from all values.
Important! If the data file does not meet these requirements, it will be rejected, and the import will be delayed until a correct file is provided.
Data File Layout Specification
Sample Files
20170115_SingularDeviceAssist_Android_Import.csv
20170115_SingularDeviceAssist_iOS_Import.csv
| Column Name | Required | Description | Example Value |
| app_name | The App Name as displayed in Singular’s Apps page | My App | |
| app_id | App’s package name/bundle ID for Android/iOS respectively.
Notice: do not use the App Store ID (example: id1441750662) |
com.singular.app | |
| os | Specify Android or iOS | Android or iOS | |
| idfa | iOS ID for Advertisers: If both IDFA and IDFV are available, you should provided both. | DFC5A647-9043-4699-B2A5-76F03A97064B | |
| idfv | |
iOS ID for Vendors | 21DB6612-09B3-4ECC-84AC-B353B0AF1334 |
| gaid | Google Advertising ID | 8ecd7512-2864-440c-93f3-a3cabe62525b | |
| asid |
|
App Set ID: Only Required if GAID is not provided. If both GAID and ASID are available, you should provided both. | 38400000-8cf0-11bd-b23e-10b96e40000d |
| android_id |
|
Android ID: Only Required if GAID and ASID are not provided. If both GAID and ASID are available, you should not provided the Android ID. | fc8d449516de0dfb |
| user_id | Custom User ID | player_1234 | |
| device_maker | Only for Amazon devices | Amazon |