Uploading data files enables you to get started using CoolaData without adding code to your site/app.
Note: We do not recommend using data files to send “live” data – use CoolaData’s REST API and/or trackers for that.

Load events to your project from Amazon’s S3 storage by entering the file URI, access key, and secret key (if the file is private).
You can also use other storage services, if they only require a URI. Simply enter URI alone and click import.

All files must comply with the following file format and event structure:

 

File format

The file postfix must be .json and not includes csv in the file name.

The JSON file should contain rows of new line-delimited JSON documents.

The JSON file must have a flat format (record) in JSON standard (CoolaData does not support a hierarchical JSON format), as such:

{"key":"value","key":"value", ...}
{"key":"value","key":"value", ...}
{"key":"value","key":"value", ...}
{"key":"value","key":"value", ...}

The content of each row may be different – for example, a payment event has currency and amount properties, but a login event will not.
Values that are not specified for a specific event will be treated as nulls (a null field should be left empty).

{"user_id": "PU4UplQaZtaYWgRdLcntauwg","age":21,"gender":"f", "session_id": "4353p1ujlco2on1lbzmmwrnu", "event_time_ts":"2012-10-15 04:06:30", "event_name":"login","ip":"255.255.255.1","country":"USA","city":"CHICAGO","browser":"moz","membership":"gold","referals":"2","social":"fblike"}
{"user_id": "PU4UplQaZtaYWgRdLcntauwg", "age":21,"gender":"f", "session_id": "4353p1ujlco2on1lbzmmwrnu", "event_timestamp":"2012-10-15 04:06:35", "event_name":"refresh","ip":"255.255.255.1","country":"USA","city":"CHICAGO","browser":"moz","membership":"gold","referals":"2","social":"fblike"}
{"user_id": "PU4UplQaZtaYWgRdLcntauwg", "age":21,"gender":"f", "session_id": "4353p1ujlco2on1lbzmmwrnu", "event_time_ts":"2012-10-15 04:06:40", "event_name":"additem","ip":"255.255.255.1","country":"USA","city":"CHICAGO","browser":"moz","qty":"1","membership":"gold","referals":"2","social":"fblike"}
{"user_id": "PU4UplQaZtaYWgRdLcntauwg", "age":21,"gender":"f", "session_id": "4353p1ujlco2on1lbzmmwrnu", "event_time_ts":"2012-10-15 04:06:45", "event_name":"payment","ip":"255.255.255.1","country":"USA","city":"CHICAGO","browser":"moz","currency":"usd","cur_amount":"100","qty":"1","level":"3","rank":"novice","membership":"gold","referals":"2","social":"fblike"}

 

Event structure

Each record (row) describes one event (which represents a user activity). Every event must include the following properties:

  • event_name (string)
  • event_time_ts (timestamp in milliseconds)
  • user_id (string)

In addition to the above mandatory properties, each event can include any number of custom properties.

Event example:

{
"user_id": "2",
"event_time_ts": 1425920218354,
"event_name":"Purchase",
"{u}user_city": "New York"
}
Print Friendly, PDF & Email