Raw Data Exports

Last Updated: Dec 21, 2016 04:43PM PST
Apsalar's Raw Data Exports offer customers an additional level of access to their account. These Export Reports provide raw log data for your account for use with your own internal tools or simply to run enhanced queries.

After signing up for this feature, Export Reports will be available directly from your Company's individual Export site. For more information about setting up Raw Data Exports, contact your Apsalar Sales Executive. For steps in setting up programmatic access to download these raw data files, please see this support article.

Please note: This report is a batched reported that is generated/updated daily. It should update roughly the same time everyday as it’s scheduled, however due to attributions/volumes, the time may change slightly. You can view the update time by looking at the timestamp in the export directory: https://export.apsalar.com/clientname/


We offer a variety of Raw Data Exports, please see the descriptions below to find which reports are right for your Company:

Referral Export Report - device_export.csv  

CSV (comma separated values) file which contains all attributed installs for your account. All attributed installs for each of your applications will be included in this dynamic report updated nightly. The report will continue to grow for the life of your account.

Each line contains an individual install and re-engagement formatted with the following fields:
  • Keyspace: This identifies the keyspace of the device ID and can be one of the following: AIFA, ANDI, IDFA, APID (Apsalar ID)
  • Device ID: The device ID in the specified keyspace
  • Campaign name: The name of the campaign specified for the applicable Attribution Tracking Tag.
  • Campaign group: The name of the campaign group specified for the applicable Attribution Tracking Tag.
  • Campaign source: The name of the campaign source specified for the applicable Attribution Tracking Tag.
  • Country: The two-letter country code for the install.
  • Click timestamp: Timestamp of click in your account's timezone, formatted "YYYY-MM-DD HH:MM:SS".
  • Install timestamp: Timestamp of install in your account's timezone, formatted "YYYY-MM-DD HH:MM:SS".
  • Pricing model: CPM/CPC/CPI, if provided in the Attribution Tracking Tag.
  • Price: The price associated with the pricing model, if provided in the Attribution Tracking Tag.
  • Source App/Site ID: The source app or site on which the campaign was run, if provided in the Attribution Tracking Tag (In most cases it is the publisher ID).
  • Creative: The creative name or ID, if provided in the Attribution Tracking Tag.
  • Longname: The bundle ID (iOS) or package name (Android) for the application.
  • Attribution: "Install" or "Reengagement". Will indicate whether entry was attributed to a new user campaign or a re-engagement campaign.
  • Custom User ID: For users with configured custom user IDs, custom user IDs will be included in each entry when available.
  • IDFV: The Identifier for Vendor for the device for the application. This is only available on iOS devices and will be empty for Android applications.
  • State/Province: The state\providence for the install.
  • CityThe city for the install.
  • Manufacturer: The Manufacturer for the install.
  • Model: The device model for the install.
  • OS Version: The device OS version at the time of the install.​
  • Carrier: The carrier name for the install.
  • Conversion Type: For attributed installs, "C" for click-through or "V" for view-through
  • Fingerprint Indicator: For attributed installs, "F" or fingerprinted or "I" for identifier
  • App Store Flag: Android only.  Supported with Android SDK 6.4 and above.  "T" or "F".  Flag indicating if app was installed from the Google Play Store.  This value is blank for for iOS, or if using unsupported Android SDK.
  • Installer Source: Android only.  Supported with Android SDK 6.4 and above.  Value of installer package name.
Here's an example entry from an device_export.txt file:
AIFA,fd18c7f4-4118-48ec-90fd-e3174d8e0380,687855750,Google Adwords for Video,Google Adwords for Video,US,12/14/16 18:38,12/14/16 18:39,Mobile Web,,YouTube,abc123,com.test.app,Install,,,California,San Francisco,Micromax,Micromax Micromax E353,6.0.1,"Comcast Cable Communications, Inc.",C,F,T,com.android.vending

Note: Facebook data will appear as organic until the Facebook Terms of Service has been signed. You can find that here: https://www.facebook.com/ads/manage/advanced_mobile_measurement/tos.  

Note: As a Facebook MMP, Apsalar retains 6 months of Facebook attribution data.

 

Daily Event Export Report - YYYYMMDD.csv.bz2

CSV (comma separated values) file which contains all events for the day specified in the filename. All events for each of your applications will be included in these files generated each morning.

Daily Event Export Reports are available for only 4 days. For example, the report for February 14th, 2014 will be available from February 15th, 2014 through February 18th, 2014. After this 4 day window, the Daily Event Export will be removed from your Export site.

Each line in the file contains an individual event formatted with the following fields (the column names you will find in the file are in parentheses):

  • Timestamp (timestamp): UNIX format in seconds (UTC)
  • IP (ip): IP Address from which call was received
  • Platform (platform): 'iOS' or 'Android'
  • Longname (longname): Bundled Identifier / Class Package
  • SDK Version (sdk): Version of Apsalar SDK
  • Device ID (udid): The canonical device ID in Apsalar. The keyspace of this ID is found in the udid_keyspace column
  • Session ID (session): Session ID sent with event call
  • Name (name): Name of event; this can be a pre-configured Apsalar event sent from the SDK('_session', '_end', '_heartbeat', '_click',etc..) or the name of a custom event configured within your application
  • Arguments (arguments): JSON dictionary of arguments included in event call, if available.
    For '_session' calls, the following attributes will be included:
    • '_av' - Application Version
    • '_c'  - Connection Type ("wifi" or "wwan")
    • '_n'  - Application Name
    • '_v'  - OS Version
    • Android only arguments:
      • '_ma' - Manufacturer
      • '_ab' - ARM EABI
      • '_br' - Android Brand
      • '_de' - Android Device
      • '_mo' - Android Model
      • '_pr' - Android Product
    • For '_click' calls, the following attributes will be included:
      • 'campaign' - Campaign Name
      • 'cr'  - Creative name/ID
      • 'network'  - Campaign Source
      • 'pl'  - Campaign Group
  • IDFA (idfa\aifa): The Advertising Identifier for the device 
  • Device ID Keyspace (udid_keyspace): The keyspace of the canonical device ID in Apsalar. For iOS, this will be UDID, IDFA, APID, or MAC1. For Android, this will be ANDI or AIFA. For _click events, the keyspace may also be GAID, H5CK, DPID, MWEB, or OPNU.
​Here is an example entry from a Daily Event Export Report:
1393145858,0.0.0.0,iOS,com.sampleorg.sampleapp,4.0.3,d0dd0000-0000-0000-0000-000000000000,g0gg0000-0000-0000-0000-000000000000,sampleEvent,"{""SampleProduct"": ""Fake_Item"", ""SampleCost"": ""10.00""}",f0ff0000-0000-0000-0000-000000000000,APID

Lifetime Revenue Export Report - revenue_dump.txt

TSV (tab separated values) file which contains the lifetime revenue for each device unique to each application on your account. This dynamic report is updated nightly and contains a single entry for each device, application pair.

For example if Device XXX has installed your applications A, B, and C, there will be three different entries in the Lifetime Revenue Export Report for Device XXX.

Each line in the file contains an individual device, application pair formatted with the following fields:

  • Keyspace: This identifies the keyspace of the device ID and can be one of the following: UDID, IDFA, ANDI, APID (Apsalar ID)
  • Device ID: The device ID in the specified keyspace
  • App Name: Bundle ID or Package name
  • Revenue: Total revenue reported for this device for the specified app, in your account's currency type.
Here's an example entry from a seg_dump.txt file:
IDFA	00000000-0000-0000-0000-000000000000	com.sampleorg.sampleapp	125.49299
support@apsalar.com
http://assets1.desk.com/
apsalarinc
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
Invalid characters found
/customer/en/portal/articles/autocomplete