Skip to main content

Overview of export data

Updated over 2 months ago

Bluecore’s email service provider (ESP) and email eligibility data can be exported to inform strategic decisions around channel spend, campaign engagement, performance, audience, and marketing eligibility.

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

For information on creating and managing jobs, see how to export data.

Data types

ESP events

The following events are only available if using SendGrid:

  • Deliver

  • Hard bounce

  • Deferred

  • Dropped

  • Spam report

  • Soft bounce

The following table outlines which fields are available in which ESP export.

Field name

Open

Click

Send, deliver, and hard bounce

Deferred, dropped, spam report, and soft bounce

Namespace

Email

Event Name

Time

Unique Key

Updated At

Device

User Agent

Campaign ID

Campaign Name

Campaign Classification

Audience ID

Campaign Run ID

Campaign Run Time

Variant ID

Tracking Parameters

NQE

Click URL

Reason

ESP event descriptions

The following table outlines the ESP event fields and their definition.

Name

Type

Description

Nullable

Data origin

Namespace

String

The Bluecore Namespace

No

Bluecore

Email

String

The customer’s email

No

Bluecore

Event Name

String

The event name

No

Bluecore

Time

Date-time

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

No

Bluecore

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

Device

String

The device the customer used when the event occurred.

Yes

Bluecore

User Agent

String

The customer's user agent string.

Yes

Bluecore

Campaign ID

Integer

The campaign’s unique ID

No

Bluecore

Campaign Name

String

The name of the campaign

No

Client

Campaign Classification

Enum

The campaign’s classification. Valid values:

  • Batch

  • Promotional

No

Client

Audience ID

Integer

The audience’s unique ID

No

Bluecore

Campaign Run ID

String

The campaign’s alphanumeric unique 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

Tracking Parameters

String

JSON formatted list of all of the campaign’s tracking parameters

Yes

Client

NQE

String

The email’s unique ID.

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

No

Bluecore

Click URL (Expanded)

String

The URL that the customer clicked

Yes

Client

Reason

String

The reason the customer unsubscribed. See unsubscribe reasons for more information.

No

Bluecore

Eligibility descriptions

You can export the following eligibility reports:

  • Full list status:

    • Opted-in

    • Unsubscribed

    • Known

  • Opt-in events

  • Unsubscribe events

The following fields are available for all eligibility events.

Field name

Type

Description

Nullable

Data origin

Namespace

String

The Bluecore Namespace.

No

Bluecore

Email

String

The customer’s email.

No

Bluecore

Event Time

Date-time

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

No

Bluecore

Source

String

How the customer opted-in. See opt-in source reasons for more information.

Yes

Bluecore

Reason

String

The reason the customer unsubscribed. See unsubscribe reasons for more information.

Yes

Bluecore

Opt-in source reasons

Some files contain a source as to how the customer opted in. The following sources are:

  • Bluecore_capture

    • The customer opted in through a Site capture campaign.

  • External

    • The customer’s opt-in request was added via the Events API or a managed feed.

  • Integration

    • The customer’s opt-in request was captured using the Bluecore Website Integration.

Unsubscribe reasons

Some files contain a reason as to why the customer unsubscribed. The following reasons are:

  • Bluecore_email

    • The customer unsubscribed by clicking a link in a Bluecore email.

  • Bluecore_id_conflict

    • The customer was unsubscribed due to customer identity reconciliation issues.

  • External

    • The customer’s unsubscribe request was loaded into Bluecore through a managed feed.

  • Manual

    • The customer was unsubscribed in the Unsubscribe page in Bluecore.

  • Bounce_events

    • The customer was automatically unsubscribed due to the bounce threshold.

Did this answer your question?