Blueshift uses Amazon S3 buckets to store data, reports (campaign activity, segment, template), audit trail logs, and other related data. You can import this data for custom workflows or warehouse applications.
Note
If you don't want to use the S3 bucket provided by Blueshift and wish to export campaign activity and automatic campaign reports to your own Amazon S3 bucket, contact support@blueshift.com to set up data replication.
Access S3 folders
You can find the details for the S3 bucket and the credentials in the Account Settings > API keys tab. The account Admin role can access the S3 folder credentials from the Account settings page.
You can access the S3 folders using an FTP/SFTP client. Some examples of open-source FTP clients include Cyberduck, Transmit, FileZilla, and WinSCP.
Important update
A new folder named index_errors has been introduced as part of the S3 exports. It is available as a sub-folder under the errors folder and captures identifier resolution-related errors, such as when an identifier resolves to an inactive user. Currently, this folder is specific to the custom_lists export and does not affect other folder structures.
Blueshift data in S3 folders
The table below outlines the different folders and the types of data they contain in the S3 bucket.
| Folder | Description |
| audit_trails | Stores daily audit trail records in CSV format. Path: <site_name>/audit_trails/<year>/<month>/<day>. Filename: audit_trails_<start-datetime>_<end-datetime>_<batch-num>.csv.gz. |
| automatic_campaign_reports | Provides daily summaries of campaign statistics at trigger or experiment levels. Note: Contact support to enable these reports. Additional columns may be added as metrics evolve. |
| bounce reports | Contains bounce action rows with a reason column. Path: <site_name>/campaign_activity/bounce/<year>/<month>/<day>. |
| campaign_actions_dump | Stores campaign activity data, including error data, in a sub-folder. Updates are made daily and can be accessed via webhooks. |
| campaign_activity | Tracks campaign activity data (e.g., sends, clicks, opens) and writes updates every 5 minutes. Path: <site_name>/campaign_activity/<year>/<month>/<day>. |
| campaign_reports | Provides daily campaign statistics (no longer recommended; use automatic_campaign_reports instead). |
| campaigns | Includes execution statistics, rendered templates for debugging, precomputed segments, and summary report data. |
| catalog | Stores catalog exports in CSV format. Filename: <catalog_name>_<date>.csv or export_catalog_<date>.csv. |
| catalogs | Stores imported catalogs and associated error reports in sub-folders. |
| computed_events | Captures Blueshift-generated events (e.g., price changes, back-in-stock alerts). |
| creatives | Contains click reports: Sub-folder click_reports: Click data by date. Sub-folder raw_clicks: Raw click data. |
| custom_lists | Stores imported custom list files. |
| customer_attributes | Includes user import files and update logs: Sub-folder user_updates: Logs for user updates made via APIs. |
| errors | Logs backend processing errors during user data processing. |
| index_errors | Captures identifier resolution-related errors, such as cases where an identifier fails to match any existing user or resolves to a user who is no longer active in the system. Path: <site_name>/custom_lists/errors/<year>/<month>/<day>. |
| events | Logs events sent via file upload or API. |
| file_upload | Stores processed file uploads for recommendations or events. |
| import | Logs imported files for recommendations or events. |
| on_demand_campaign_reports | Stores campaign reports exported on demand via the dashboard. |
| promotions | Includes files related to promotions. |
| segment | Stores data exported for segments. |
| segment_export | Logs scheduled segment export data. |
| syndications | Stores files uploaded to syndication destinations. Also contains intermediate aggregated files. |
| useractions | Logs raw data for user campaign interactions. |
Comments
0 comments