Traffic Import Tool

The following document defines the process for importing data from an external source into Kochava. This allows historical data from other providers to be ingested by Kochava and shown in analytics as well as providing a list of users who have already installed the app in the past for Kochava to deduplicate against.

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 User Interface

---

Import New Data

---

Source Type:

AWS CSV –

AWS ARN CSV –

---

Traffic Import Overview

---

Traffic Import Actions

Import Details:

Clicking on the up and down carrot icon will reveal the import details.

Recent Import:

Clicking on the stacked database icon will display the imported data.

Restart Import:

Clicking on the circular arrow will start the import process 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.

---

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

---

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 http://aws.amazon.com
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 and S3 Bucket Access

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

10. Click Next.
11. Click Create policy (will open a new window).
12. Select the JSON tab.
13. Enter the desired template code:

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”.

["arn:aws:s3:::my-bucket-1/my-file-1.csv","arn:aws:s3:::my-bucket-2/some/path/to/my-file-12.csv"].
 
{
  "Version": "2012-10-17",
  "Statement": [
	{
  	"Effect": "Allow",
      "Action":  "s3:GetObject",
      "Resource": ["arn:aws:s3:::INSERT-BUCKET-NAME-HERE/INSERT-FILE-PATH-HERE"]
	}
  ]
}

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.

{
  "Version": "2012-10-17",
  "Statement": [
	{
  	"Effect": "Allow",
  	"Action": "s3:ListBucket",
      "Resource": "arn:aws:s3:::INSERT-BUCKET-NAME-HERE"
	},
	{
  	"Effect": "Allow",
      "Action":  "s3:GetObject",
      "Resource": "arn:aws:s3:::INSERT-BUCKET-NAME-HERE/*"
	}
  ]
}