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

Import New Data

1. Click Import Data.
2. Select an App.

Notification Settings:

1. Enter a Notification Recipient:
1. Select/Enter an email address.
2. Add a Slack Notification:
1. Enter a Slack URL.
2. Enter a Slack Username. (optional)
3. Enter a Slack Channel. (optional)
4. Click Add.

 


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

Source Type:

AWS CSV –

1. 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: https://s3-us-west-2.amazonaws.com/kochava-traffic-import/Install/Gilt+iOS+iPad.csv”>https://s3-us-west-2.amazonaws.com/kochava-traffic-import/Install/Gilt+iOS+iPad.csv

2. Enter the AWS Access Key ID and AWS Secret Access Key :
1. Navigate to My Security Credentials.
2. Open the Access Keys section.
3. Cut and Paste the Access Key ID and Secret Access Key.

Example: AKIBIZG57ZSYADFS2ZHD

 

AWS ARN CSV –

1. 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: https://s3-us-west-2.amazonaws.com/kochava-traffic-import/Install/Gilt+iOS+iPad.csv”>https://s3-us-west-2.amazonaws.com/kochava-traffic-import/Install/Gilt+iOS+iPad.csv

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

 

Tune –

1. Enter the Tune API Key.
1. Enter the Tune Site ID. (Tune Source App ID)
2. Enter the Date Range.
3. 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.

2. Select the Traffic Type:
1. Install
2. Post-Install Event

 

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

 

3. 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. Failed Import

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.

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

1. Log in to the AWS Console.
2. From the Services drop-down menu, Select Security, Identity, & Compliance > IAM.

 



 

3. From the left navigation panel, Select Roles.
4. Click the Create Role button.
5. Select AWS account.
6. Select An AWS account > Another AWS account.
7. Enter the Kochava AWS account number 719465667078 into Account ID.
8. Select Options > Require external ID.
9. Enter an External ID.

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/*"
	}
  ]
}

 

14. Update the “Resource”.
15. Click Next: Tags.

 


A. Update the Resources field.

 

NOTE: At this point another Tag may be added but is optional.

16. Click Next: Review.
17. Enter the Policy Name.
18. Enter the Policy Description.
19. Click Create policy.

 



 

NOTE: At this point if you are not navigated back to the Roles page, click on the Roles page tab in your browser.

20. Refresh the Roles Permissions policy screen.

NOTE: You do not need to refresh the entire page, AWS provides a refresh (↺) button to update the roles.

21. Select the recent created policy.
22. Click Next.
23. Enter a Role Name (e.g., KochavaReadS3).
24. Enter a Role Description.
25. Click Create role.