Skip to main content
Data exports

An overview of Bluecore data exports.

Updated over a month ago

Data exports overview

Data exporting allows you to take campaign results, audience information, or email service provider (ESP) events from Bluecore and use them in your other systems.

The table below highlights the different types of exports and how they can be accessed.

The following export types are:

  • Analytics

  • Audience

  • ESP/Email Unsubscribe

Analytics

Audience

ESP/Email Unsubscribe

Timing

Any time

As often as specified in the export campaign

Daily

Timeframe of data

Any specified timeframe

Current state at the time of the export

Daily, midnight to midnight UTC

How to access

Anyone with access to the Bluecore platform can export these manually

These files are SFTP’d to a location that you specify in the integration

You must request these files. Once the FDE team has set this process up for your company to receive these exports, your IT team will need to get access to Files.com to download these exports.

Analytics exports

Analytics can be exported through Bluecore at any time within the past two years. Analytics that provide an overview of data within Bluecore, such as all campaigns, are located in the Analytics section in the navigation bar, and analytics that focus on individual information, such as one campaign, are located on the individual campaigns.

Bluecore offers the following Analytics with exports:

Note: You may not have access to all of the Analytics and exports listed, depending on your Bluecore products. Contact your Customer Success Manager if you are interested in learning more.

Audience exports

Audiences can be exported once or on a recurring basis within your namespace. You can export the following information with your audience:

  • Email addresses and/or phone numbers (always included)

  • Any customer attributes

  • Any product attributes

  • Any percentile predictive scores:

    • PCLV

    • Discount affinity

    • Likelihood to unsubscribe

    • Likelihood to click

    • Likelihood to open

    • Likelihood to convert

    • Lifecycle stages

    • Channel affinity for email

    • Channel affinity for SMS/MMS

Note: The ability to use some percentile predictive scores depends on your contract. Likelihood to unsubscribe, click, and open require email campaigns. Channel affinity requires both email and SMS/MMS campaigns.

Create an audience export

In order to export audience data, you must first create an export integration, and then create an export campaign that uses that export integration.

Create a new export integration

Export integrations define where Bluecore sends the export.

When creating a custom integration, Bluecore recommends using a service account for SFTP access instead of a personal account.

Using a personal account may cause the SFTP integration to fail if changes are made to the account, like password updates.

To create an export integration, complete the following:

  1. In your Bluecore Namespace, navigate to Data > Integrations. The list of installed integrations displays.

  2. Click New Integration. The New Integration dialog box displays.

  3. Click Custom Integration. The Settings tab displays.

  4. Enter in the Vendor Name.

  5. Click on the Definitions tab. All customer and product attributes and percentile predictive scores display.

  6. Enable all definitions that you want to include with your audience export.

  7. Click Authentication. The Destination Settings tab of the export displays.

  8. Fill out the Host, Username, and Password fields.

  9. When finished, click Connect to verify the connection.

  10. Click on the Campaign tab.

  11. Fill out the following information:

    1. Directory

      1. Where to send the file.

Note: To export the file to Bluecore's Files.com instance, the directory should include the client's folder name (usually the Namespace) and the directory path. For example: /clientNamespace/audience_exports.

To export the file to a non-Bluecore hosted file share, use the necessary directory path. For example: /exports/audience_exports.

b. File Name

i. The naming convention you want the file to use.

c. Filename timestamped

i. Option to include a timestamp on the file.

ii. If enabled, it displays at the end of the filename in YYYYMMDDHHMMSS format.

iii. Defaults to not selected.

Note: The Filename timestamped selection is the only way to receive files with datetime variables in the filename.

d. Character Encoding

i. Options include:

1. UTF-8

a. Default

2. UTF-16

e. Row delimiter

i. Options include:

1. Windows

a. Default

2. Linux

f. Column Delimiter

i. Options include:

1. Comma (,)

a. Default

2. Pipe (|)

3. Tab

4. Semicolon (;)

g. Include Header Row

i. Options include:

1. Yes

a. Default

2. No

12. When finished, click Save. The integration is saved.

Create an audience export campaign

Once the integration is created, you need to create a campaign to export the audience data. To create an export campaign, complete the following:

  1. Navigate to Campaigns and select either Automated Campaigns or One-Time campaign, depending on if you want a recurring export or one-time export, respectively.

  2. Click New. The Channel dialog displays.

  3. Click Audience Exports Email and click Next.

  4. Enter in an export name.

  5. Select the audience you want to export.

  6. Choose the timeframe and how frequently you want the export to run.

  7. Select the custom integration you want to send the export.

  8. When finished, click Save & Continue. The Export tab displays.

Note: If you update the definitions on the export integration and want to pull those into your audience export campaign, you must create a new audience export campaign. You can’t add new definitions on an existing campaign.

ESP and email unsubscribe exports

ESP and email unsubscribe exports are generated daily and contain customer behavioral information for ESP events, such as clicks, and email unsubscribes.

You can use the export data to keep your system of record up to date for compliance, or import it into other third party applications.

Note: If your company is integrating with Bluecore, you can request these exports in your scope of work. If you have completed integration and didn't request these reports, contact your Customer Success Manager.

Accessing your Files.com exports

These exports are delivered through Files.com are generated daily and are available for seven days after generation. You are responsible for downloading the files and using them outside of Bluecore.

Note: In order to view exports, you must have a Files.com user. If you don’t have a Files.com user, log a ticket to the Support team or contact your Customer Success Manager.

To access your Files.com exports, complete the following:

  1. Enter in your username and password and click Continue. Your root folder displays.

  2. Navigate to the folder where the exports are located.

  3. Click the download button on the export you want to download.

Note: Bookmark https://files.bluecore.com/ so that you are always directed to the correct Files.com domain. If you do navigate to Files.com and sign in, type in triggermail as the domain name takes you to Bluecore’s Files.com account.

Export format

All Files.com exports are in the same format:

  • Comma delimited

  • Flat file

  • All dates and times in UTC

All campaign data is from the time of campaign execution. If a campaign name changes between sends, you will see multiple campaign names associated with a single campaign id.

Export data

The following is an overview of the fields in each file, what they mean, and the origin of the data.

ESP export

The ESP export contains data for the following email events:

  • Deliver

  • Open

  • Click

  • Unsubscribe

  • Soft bounce

  • Hard bounce

  • Halt

  • Spam report

  • Dropped

  • Deferred (if available)

Note: The ESP export is optional. If you would like to receive this export, contact your Customer Success Manager.

Field Name

Type

Description

Nullable

Data Origin

namespace

String

The Bluecore Namespace

No

Bluecore

email

String

The customer's email address

No

Bluecore

event

String

The event name

No

Bluecore

event_time

date-time

The date-time when Bluecore was informed about the event, in UTC

No

Bluecore

device_type

String

The device the customer used when the event occurred.

Only available for open, click, and unsubscribe events.

Yes

Bluecore

user_agent

String

The customer's user agent string.

Only available for open, click, and unsubscribe events.

Yes

Bluecore

click_url

String

The URL the customer clicked on.

Only available for click events.

Yes

Bluecore

unsubscribe_source

String

The source of unsubscribe events.

Only available for unsubscribe events.

Yes

Bluecore

campaign_id

Integer

The campaign's unique id

No

Bluecore

campaign_name

String

The campaign name

No

Client

campaign_classification

Enum

The campaign classification. Valid values:

  • Triggered

  • Promotional

  • Transactional

No

Client

audience_id

Integer

The audience's unique id that's referenced in the campaign.

If there are multiple ids, they are pipe (|) separated.

No

Bluecore

campaign_run_id

String

The alphanumeric campaign run id

No

Bluecore

campaign_run_time

Date-time

The date-time when the campaign ran, in UTC

No

Bluecore

variant_id

String

The A/B variant, if applicable

Yes

Bluecore

subject_line

String

The campaign's subject line

No

Client

tracking_parameters

String

JSON formatted list of all tracking parameters on the campaign

Yes

Client

nqe

String

The email's unique id.

Two records with the same NQE refer to the same email.

No

Bluecore

journey_id

String

The journey's unique id, if using Campaign Builder

Yes

Bluecore

journey_name

String

The journey's name, if using Campaign Builder

Yes

Client

unique_key

String

Alphanumeric primary unique id. Prevents accidental data duplication during data transformations.

No

Bluecore

updated_at

Date-time

When the data was last updated in Bluecore's data warehouse, in UTC

No

Bluecore

Email unsubscribe export

The email unsubscribe export displays campaign information on which customers clicked to unsubscribe.

This export is required if you use an ESP other than Bluecore, and recommended if Bluecore is your only ESP.

Note: If you do not receive the email unsubscribe export and would like to start receiving it, contact your Customer Success Manager.

Field Name

Type

Description

Nullable

Data Origin

namespace

String

The Bluecore Namespace

No

Bluecore

email

String

The customer's email address

No

Bluecore

event

String

The event name

No

Bluecore

event_time

date-time

The date-time when Bluecore was informed about the event

No

Bluecore

device_type

String

The device the customer used when the event occurred.

Only available for open, click, and unsubscribe events.

Yes

Bluecore

user_agent

String

The customer's user agent string.

Only available for open, click, and unsubscribe events.

Yes

Bluecore

campaign_id

Integer

The campaign's unique id

No

Bluecore

campaign_name

String

The campaign name

No

Client

campaign_classification

Enum

The campaign classification. Valid values:

  • Triggered

  • Promotional

  • Transactional

No

Client

audience_id

Integer

The audience's unique id that's referenced in the campaign.

If there are multiple ids, they are pipe (|) separated.

No

Bluecore

campaign_run_id

String

The alphanumeric campaign run id

No

Bluecore

campaign_run_time

Date-time

The date-time when the campaign ran

No

Bluecore

variant_id

String

The A/B variant, if applicable

Yes

Bluecore

subject_line

String

The campaign's subject line

No

Client

tracking_parameters

String

JSON formatted list of all tracking parameters on the campaign

Yes

Client

nqe

String

The email's unique id.

Two records with the same NQE refer to the same email.

No

Bluecore

Did this answer your question?