Exports raw data to downloadable files. Data is split into roughly 256 MB files, and is not necessarily ordered. Exports can be made in JSON or CSV format. For JSON format, each file contains 1 line per session, with each session JSON-encoded. For CSV format, data is split into separate files for sessions, states, events, event parameters, and user attributes.
Note that for daily exports, you may see some variation in sessions data results. This is because sessions data can come in up to 8 days after a user's last interaction with your app.
Export files are automatically deleted 24 hours after export occurs. Data becomes available to export every 2 hours, and only for complete sessions. You cannot export data that has become available more than 60 days ago. You may only export data 24 times per day. Exports with invalid arguments do not count towards this limit.
Use getExportResults with the returned
jobId to get the results.
If you are building a request to Manually Export Data to an S3 bucket and the s3BucketName, s3AccessId or s3AccessKey are inserted as parameters in the URL, then, take in mind that any special characters that these parameters may contain needs to be URL encoded when being inserted inside the URL.
For example, a plus character (+) will be equal to (%2B).
If you configure the exportData API to send the files to an S3 bucket, they are not being stored on our servers afterwards. In this case, they cannot be accessed via the link in getExportResults.