Importing Existing Attribution Data

Existing device attribution information can be uploaded and brought into the Singular platform!

NOTE: Historical data MUST be imported into your Singular production account BEFORE apps are live and pushed to the App Stores to avoid contamination of historic attributions. If the Apps are pushed before historical data is loaded, then spikes in Organic installs will occur and the attribution source for some of the devices will be incorrect. To avoid further data contamination, Singular will proceed with loading the remain data as Organic installs. This will still blacklist the historic device for future attributions through new paid UA efforts.

While we understand your existing users' dataset can be formatted in a variety of ways, we require a flat file of your historical data. To ensure a smooth and speedy import, provide flat files in the format specified below.

Please note that we only support importing devices with advertising IDs (IDFA or AIFA).

If data is not provided in this format, delays in processing or rejection of the file can occur. Singular will examine the data files provided and inspect for duplicate installs. If duplicates are found, the duplicates will be removed and a file with unique advertising IDs will be used for the data on-boarding. 

File Type

  • Provide data files on one of the two formats below:
    • unix encoded '.tsv' (tab separated file)
    • unix encoded '.csv' (comma separated file)


File Naming Convention

  • Use the following naming convention to keep your data files organized.
  • Provide one file per App

  • Filename Examples:
    • Date file is provided (YYYYMMDD)_App-Name_installs.tsv

      20170115_my-app-name_singular_installs.tsv

 

Sample File Layout with data (Historical Installs)

  • The App Longname and App Store URL Columns may be omitted if they are clearly noted for each file provided. 

install-data.png 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk