Support Home > Reference Information > Traffic Import Tool

Traffic Import Tool

The following document defines the process for importing data from an external source into Kochava.


NOTE: It is very important to process all install events before processing any post-install events. Importing post-install events without an install record will create an install record for each post-install event. If the original install records are imported after, they will be viewed as duplicate records and discarded.


Data Needed Before Beginning Process:

  • A properly formatted CSV File (CSV)
  • A valid AWS (Amazon Web Service) account
  • S3 Bucket (ARN CSV)
  • Role for Cross-Account access (ARN CSV)


NOTE: For more information about obtaining an AWS Access Key ID and Secret Access Key for AWS CSV import, refer to our AWS Access support documentation.

Data Preparation

There are two main methods for importing data into Kochava, and each of the methods requires the data to be prepared before the import process can begin. For more information about data preparation, refer to the following methods:

  1. CSV File Format
  2. AWS Cross-Account Creation

Traffic Import Interface

  1. Log in to Kochava.
  2. Select Account Options>Traffic Import.



Import New Data

  1. Click Import Data.
  2. Select an App.
  3. Enter a Notification Recipient:
  4. a. Select/Enter an email address.
    b. Add a Slack Notification:

    i. Enter a Slack URL.
    ii. Enter a Slack Username. (optional)
    iii. Enter a Slack Channel. (optional)
    iv. Click Add.



    A. Enter an email address and/or Slack notification.



    b. AWS ARN CSV

    i. Enter the AWS File Location.

    1. Navigate to S3 bucket.
    2. Navigate to file.
    3. Select file.
    4. Click Properties.
    5. Cut and Paste link. Example:


    ii. Enter the AWS ARN Role:

    1. Navigate to IAM.
    2. From the left-side menu, Select Roles.
    3. Cut and Paste the Role ARN. Example: arn:aws:iam::350235873889:role/KochavaReadS3




    c. Tune

    i. Enter the Tune API Key.
    ii. Enter the Tune Site ID. (Tune Source App ID)
    iii. Enter the Date Range.
    iv. Enter the Tune Advertiser Account ID. (Tune Account ID)



    A. By default, the last 120 days are selected.


    NOTE: Tune will allow the last 120 days of data to be exported. By default, the date range is set to the last 120 available days.


  5. Select the Traffic Type:
  6. a. Install
    b. Post-Install Event


    NOTE: ALL installs MUST BE processed before any post-install events.


  7. Click Import.


    A. Select the Traffic Type. Install MUST be processed before Post-Install.

Traffic Import Overview

Each time data is imported into Kochava, an overview for each import is created. Imports that are being processed are indicated in blue, successful imports are indicated in green, failed imports are indicated in red, and cancelled imports are indicated in gray.


NOTE: While data is being imported, progress can be viewed by clicking the Expand button.

NOTE: An email will be sent when data is imported successfully. An email will also be sent when an error occurs with a description of the error during the import process.



A. Successful Import
B. Data Import Details
C. Cancelled Import
D. Unsuccessful Import
E. Error Message

Traffic Import Tools

Successful Data Import:

Import Tools>Recent Import (Provides sample data of the latest imports).


Unsuccessful Data Import:

Import Tools>Recent Import (Provides sample data of the latest imports).


Cancelled Import:

Import Tools>Recent Import (Provides sample data of the latest imports).
Import Tools>Restart (The Tune import will attempt to begin where the import stopped. The CSV import will start over again.)


CSV File Format for Data Import


Install CSV File Format:

The following fields are already provided to the Traffic Import UI and do not need to be provided in the CSV file:

  • kochava_app_id=selected by user
  • action=Install
  • import_source_name=File Import


NOTE: All of the columns listed below are required, but some of the values may be left empty. Refer to the * indications for further information.


Field Example Description Req.
usertime 1456163286 *Epoch timestamp for record of when the install occurred Yes
imported_attribution InMobi **The name of the network or publisher attributed to the install. Yes
ip **The IP address of the device on install. Yes
device_type idfa The Device ID type associated to the device ID (IDFA and ADID only). Yes
device_id fdad9921-821a-c6bc-8e87-94e0a3f83a5e The device id for the device that installed the app. (IDFA or ADID). Yes
device_ua Mozilla/5.0 (iPhone; U; CPU iPhone OS 5_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16 **A string representation of the device user agent as provided by the client. This string is useful when campaigns require fingerprint attribution Yes

*Defaults to current datetime if left empty
**Must have column but value can be empty


Post-Install CSV File Format:

The following fields are already provided to the Traffic Import UI and do not need to be provided in the CSV file:

  • kochava_app_id=selected by user
  • action=Event
  • import_source_name=File Import


Field Example Description Req.
event_name Purchase *Name of the app event Yes
imported_attribution InMobi The name of the network or publisher that was attributed to the event. Yes
event_value “sku”:123, “price”:”50.00”,”Qty”:1 The event value pairs for the event from the app. Yes
usertime 1456163286 Epoch timestamp for record of when the install occurred. Yes
ip The IP address of the device on event. Yes
device_type idfa The device ID type associated to the device ID (IDFA and ADID only) Yes
device_id fdad9921-821a-c6bc-8e87-94e0a3f83a5e The device ID for the device that installed the app (IDFA or ADID). Yes

*Will default to current datetime if left blank.

AWS Cross-Account Setup


Creating a Web Service Account:

NOTE: If an Amazon Web Service Account has already been created, proceed to the Creating an S3 Bucket section.


  1. Navigate to
  2. Click Create an AWS Account.
  3. Follow the on-screen instructions.

    Creating an S3 Bucket:

    In order to create an S3 bucket, refer to Amazon’s Create the Buckets for Your Website support documentation.


    Create an AWS Role for Cross-Account Access

    1. Log in to the AWS Console.
    2. From the Services drop-down menu, Select IAM.



    4. From the left navigation panel, Select Roles.
    5. Click the Create New Role button.



    7. Enter a Role Name (e.g., KochavaReadS3).
    8. Click Next Step.
    9. Under Select Role Type, Click Role for Cross-Account Access.
    10. Click Allows IAM users from a 3rd party AWS account to access this account.



    12. Enter the Kochava AWS account number 719465667078 into Account ID.
    13. Enter the External ID.

      NOTE: The External ID is provided by a Kochava Account Manager (account_id). The External ID must be formatted as “account:account_id”.

      NOTE: DO NOT check the Required MFA checkbox.


    15. Click Next.



      NOTE: The Attach Policy screen will appear; DO NOT select a policy.


    17. Click Next.
    18. Click Create Role.


    Specify the S3 Bucket Access for the AWS Role:

    1. From the Roles list, Select the Kochava role (e.g., KochavaReadS3).

      NOTE: When selecting the Kochava role, click on the name of the role. If only the selection box is clicked, nothing will happen.


    3. At the bottom of the Summary screen, Select the Permissions tab.
    4. Click the Inline Policies expand button.



    6. Click the Click Here link.
    7. Select Custom Policy.

      NOTE: If Policy Generator is selected, refer to AWS for any support questions.


    9. Enter a Policy Name (e.g., KochavaReadBucketFile).
    10. Copy the Policy Document from one of the example templates.
    11. Enter the associated Bucket Name.
    12. Enter the associated File Name.

      Template Example 1:

      This template will provide Kochava read access to specific files within one or more buckets, but no access to other files in those buckets.


      NOTE: The Resource value is an array of ARNs, so you can specify multiple bucket/file combinations, for example, “Resource”.



      Template Example 2:

      This template will provide Kochava access to all the files within a bucket.


      NOTE: If there will be multiple files involved over a period of time, this approach will be simpler than creating or updating roles for each new file or set of files.



    14. Click Validate Policy.
    15. Once the policy has been validated, Click Apply Policy.


      A. Template Example 1 Entered.


    Last Modified: May 18, 2017 at 3:01 pm