- Migrate your event data export process
As part of scheduled work to improve the performance and reliability of our Data Export feature for Optimizely X, we are changing the way you access your Optimizely X event data files.
Please modify your event data export process to use the new AWS bucket name, folder path, and file naming structure according to the migration steps listed below. We will no longer generate event data in the current AWS bucket after July 14, 2017.
Update your event data export process to use this AWS bucket name: optimizely-export-ng/
Update the read folder to account_id/project_id/2.0/yyyy/mm/dd/experiment_id/
For example: 123456789/234567890/2.0/2017/04/06/987654321/
Update your process to extract and read the file parts.
In the new AWS bucket, the event data is stored in multiple file parts instead of a single file (like in the current bucket). The file parts use the following naming structure:
For example: 987654321-0-2017-03-06-r-00062.gz
Please note the following conventions:
The unzipped files do not have any file extension, but use the same tsv format
There are up to 30 file parts per experiment per day (filepartnum = 0-29)
Currently, the Raw Data Event Export feature is available on select plans; please reach out to your Customer Success Manager if you wish to utilize this feature. If you do not have a CSM, submit a ticket to the developer support team to verify your plan and eligibility.