Enriched Events Export replaces Results Export and Raw Events Export as Optimizely's source-of-truth events dataset. Results Export and Raw Events Export will no longer be supported beginning November 15, 2020. Please refer to the Enriched Events Export documentation for how to get started.
I don't see a status.yaml file.
If you don't see a status.yaml file, the raw data is still copying into the S3 bucket. When the status.yaml file appear, the process is complete and it's safe to begin copying the raw data.
The status.yaml file says export failed.
Please file a support ticket so we can look into this issue.
I need a script or code for accessing my data.
We don't recommend specific programs for accessing raw data through Amazon S3 or provide scripts for data retrieval. You may need technical help on your end to develop a solution that meets your business needs.
My raw data doesn't match the results page.
It's important to understand that the raw event data is not results data. The data we provide access to is a raw list of events we received, not a list of results data. Event data goes through an attribution process described in our knowledge base. Our raw data comes from before attribution occurs.
Raw event data will contain events from users who may or may not count for an experiment. Events may exist in exports outside of the time frame in which an experiment ran. Recreating the results page's numbers out of raw data will be nontrivial, as it would require recreating our entire attribution model in your queries.
The password column is missing in the credentials file I received from Technical Support.
We don't provide access to the AWS web console, which is why there's nothing in the password column. All you need are the
AWS_ACCESS_KEY_ID and the
AWS_SECRET_ACCESS_KEY to access your data.
The timestamp field in Raw Events Export files shows unrealistic timestamps.
For example, the timestamp may be 544444509761, which is Friday, April 3, 1987 10:35:09.761 AM. The timestamp field is taken directly from the request headers and payload that originated the POST request to the logx.optimizely.com events endpoint. The timestamps in optimizely-export-ng are raw in that we don't do any processing to it. This means that the timestamp was given to use by the visitor who triggered an event, more specifically, it's the timestamp of their client that handled the request.
Updated almost 2 years ago