User Role | View | Edit |
Client Admin |
| ✓ |
Data Manager |
| ✓ |
Viewer | ✓ |
|
Unlock insights and streamline your data workflows by exporting email service provider (ESP) and eligibility data from Bluecore directly to an SFTP or Google Cloud Storage bucket.
When creating an export job, you specify which event to export, the destination, and the frequency. You can update these settings at any time.
The exported data follows a schema, making it easier to integrate with your systems.
Once an export job is set up, you can be notified when it runs.
To learn more about export job and run statuses, see Understanding export job and run statuses.
Prerequisites to create an export job
A pre-configured export integration, for either Google Cloud Storage or an export SFTP so that the job knows where to export the file.
The target folder that the file exports to must exist, because the path will be validated before you can save the job.
If you are exporting to Files.com, you can choose to export files to your parent Namespace file path, if applicable.
If you are planning to export data with a date range that’s greater than 30 days and less than two years, contact support@bluecore.com with the requested date range and link to the paused job.
If you are planning to export data with a date range that’s greater than two years, contact support@bluecore.com with the requested date range and the required job configuration details.
Create an export job
Navigate to Data > Event Exports. The list of event exports appears.
Click New Event Export Job. The list of destination integrations appears.
Click the destination integration in which you want to send the file. The Event Exports Job page appears.
Fill out the details about the export job and, when finished, click Save Job.
Job Timezone and file dates
To use your local day and time for the export data date range and job schedule, select your timezone in the Job Timezone dropdown.
The date and time data contained in the export files are always recorded in UTC. The Job Timezone only affects the export data date range and job schedule, not the timestamp data.
Export file name structure
The export file name is constructed using the file name, extension, and run ID, and other settings that you choose when creating or editing a job.
The file name structure is made up of the following:
<File name>-<date range>-<partition ID>-<wildcard>-<run ID>.<extension>
File name
The name of the file that you input in the Job Settings section.
Date range
If you select Append date range to file name, the date range of the data in the file.
Format:
YYYYMMDD-YYYYMMDDExample: One file representing May 5th, 2025 through May 6th, 2025 would be
20250505-20250506.
Partition ID
If you selected Split files by day, this identifier represents the specific day’s data.
Format:
YYYYMMDDExample: One file representing March 5th, 2025 would be
20250305.
Wildcard
Indicates if the file is part of a set of sharded files due to the original file being over 1GB. The wildcard starts from 0 and goes up sequentially.
Format:
000000000000Example: If one file was split into three files, the first would be
000000000000, the second would be000000000001, and the third would be000000000002.
Run ID
The ID associated with the run that created this export.
Format:
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Extension
The combination of the selected file type.
Example: if you selected a CSV file type, the extension would be .csv.