Importing Raw Logs
Pixel logs can be imported to Parse.ly's backend in CSV format. Each row in the CSV file represents an event, which is analogous to a single request made by the Parse.ly tracker.
The following is an example of some different event types specified in CSV
format. The column names shown are the minimum set necessary to get useful
data out of the Parse.ly dashboard, but there are many other columns
supported, which are documented below. The order of the columns doesn't
matter, and you can choose to include or exclude most columns based on the
characteristics of your dataset. The only strictly required columns, which
must be non-empty for each row, are
timestamp_ms, though we recommend including all of the
The raw log file format follows this CSV specification, especially regarding things like literal commas and quote escaping.
apikey,url,referrer,action,user_agent,timestamp_ms,visitor.ip,visitor.site_id blog.parsely.com,https://blog.parse.ly/post/7908/prospective-students-reading/,https://blog.parse.ly/,pageview,Mozilla/5.0 (Linux; Android 8.0.0; Moto Z (2) Build/ODXS27.109-34-7) AppleWebKit/537.36 (KHTML\, like Gecko) Chrome/66.0.3359.158 Mobile Safari/537.36,1526428787.196,126.96.36.199,z3nv4P0KHOdpTJwsGV7jL blog.parsely.com,https://blog.parse.ly/post/3644/solve-digital-media-biggest-problems/,https://blog.parse.ly/post/7908/prospective-students-reading/,pageview,Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0,1526428787.196,188.8.131.52,z3nv4PaKHOhpTJjsGV7jL
A string representing the name of the Parse.ly apikey for which the event should be counted. This value will be provided by Parse.ly for each site tracked.
The url of the page on which the event happened. The Parse.ly tracker uses
window.location.href as a default for this value.
The HTTP referrer of the pageload on which the event happened. The Parse.ly
document.referrer as a default for this value.
A string indicating the event's type. Currently, only
pageview is supported
by this import process.
The user agent string of the agent (browser) in which the event happened.
A timestamp indicating the time at which the event was sent by the agent, in milliseconds, since epoch.
The IP address from which the event originated.
A UUID uniquely identifying the user on whose behalf the event was sent. Expected to be unique within a 30-day period across the site from which the event was sent.
#Other supported fields
A string uniquely identifying the user session from which the event originated. The Parse.ly tracker uses a 30 minute timeout to delineate user sessions.
A timestamp indicating the time at which the user session from which the event originated started, in seconds since epoch.
The url of the page on which the user session from which the event originated.
The Parse.ly tracker defaults this value to
The HTTP referrer of the pageload on which the user session from which the
event originated. The Parse.ly tracker defaults this value to
The start timestamp of the user session preceding the one from which the event originated, in seconds since epoch.