Please contact your Customer Success Manager (CSM) to enable this feature.

ABOUT ANALYTICS EXPORTS

Analytics Exports allows you to extract behavioral and other raw event data about events and campaign-specific activities.

This information can be used to keep your system of record up to date with compliance data, or loaded into a reporting system or other third party applications.

Bluecore provides these files on a daily basis and each subsequent run contains data collected in the previous day.

ABOUT ANALYTICS EXPORTS OUTPUT FILES

Analytics Exports Output Files contain information about each event transaction. Each row represents one Event transaction/occurrence. Each output file contains data for one or multiple Event types, as explained in the schemas below.

Analytics Exports are exported to comma-delimited flat files that are available on Bluecore’s Secure FTP server. Files can be compressed or encrypted upon request.

All extracted date and time values are formatted in Coordinated Universal Time (UTC) for consistency and ease of comparison. The event information contained in each Analytics Exports output is the data recorded between the previous two midnights, UTC.

Analytics Extracts Output Files will be available in the Bluecore Secure FTP server for seven (7) days from the date each file is made available. You are responsible for any use of Analytics Extract Output Files outside of the Bluecore UI.

ANALYTICS EXPORTS FILE LAYOUTS

DELIVERED

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
campaign_name	STRING	NO	The campaign name.
subject_line	STRING	NO	The subject line of the campaign.
campaign_id	INTEGER	NO	The numerical identifier of the campaign.
audience_id	INTEGER	NO	The campaign audience ID (pipe-separated if multiple).
nqe	STRING	NO	The unique ID for the particular email. Two records with the same NQE refer to the same email.
variant	STRING	YES	The A/B test variant, if applicable.

OPENED

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
campaign_name	STRING	NO	The campaign name.
subject_line	STRING	NO	The subject line of the campaign.
campaign_id	INTEGER	NO	The numerical identifier of the campaign.
audience_id	INTEGER	NO	The campaign audience ID (pipe-separated if multiple).
nqe	STRING	NO	The unique ID for the particular email. Two records with the same NQE refer to the same email.
variant	STRING	YES	The A/B test variant, if applicable.
useragent	STRING	NO	The user agent string that identifies the user's device and browser version.

CLICKED

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
campaign_name	STRING	NO	The campaign name.
subject_line	STRING	NO	The subject line of the campaign.
campaign_id	INTEGER	NO	The numerical identifier of the campaign.
audience_id	INTEGER	NO	The campaign audience ID (pipe-separated if multiple).
nqe	STRING	NO	The unique ID for the particular email. Two records with the same NQE refer to the same email.
variant	STRING	YES	The A/B test variant, if applicable.
url	STRING	NO	The URL of the link the recipient clicked.
useragent	STRING	NO	The user agent string that identifies the user's device and browser version.

OPTINS

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
source	STRING	NO	The origin of optin record. Possible values are: “bluecore_capture” - This includes all options from forms created using the Bluecore Capture tools. “external” - This includes all options from file transfers or other external sources. “integration” - This includes all options recorded directly from the JavaScript integration.

UNSUBSCRIBE

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
campaign_name	STRING	NO	The campaign name.
subject_line	STRING	NO	The subject line of the campaign.
campaign_id	INTEGER	NO	The numerical identifier of the campaign.
audience_id	INTEGER	NO	The campaign audience ID (pipe-separated if multiple).
nqe	STRING	NO	The unique ID for the particular email. Two records with the same NQE refer to the same email.
variant	STRING	YES	The A/B test variant, if applicable.
reason	STRING	NO	The reason for the customer being unsubscribed. Possible reasons include: “bluecore_email” - Unsubscribed from link in Bluecore email. “bluecore_id_conflict” - Unsubscribed due to customer identity reconciliation issues. “external” - Unsubscribe records received by Bluecore from external source. “manual” - Unsubscribed via Bluecore UI. “bounce_events” -Automatically unsubscribed due to bounce threshold.

OTHER DELIVERABILITY EVENTS

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
campaign_name	STRING	NO	The campaign name.
subject_line	STRING	NO	The subject line of the campaign.
campaign_id	INTEGER	NO	The numerical identifier of the campaign.
audience_id	INTEGER	NO	The campaign audience ID (pipe-separated if multiple).
nqe	STRING	NO	The unique ID for the particular email. Two records with the same NQE refer to the same email.
variant	STRING	YES	The A/B test variant, if applicable.
event_type	STRING	NO	The name of the event. Possible values are: "soft_bounce" "hard_bounce" "spamreport"

PURCHASE DATA

Bluecore does not provide exports of attributed purchases. Instead we can provide data on all purchases, which you can leverage alongside our other exports (e.g. click data), within your own attribution model.

Field Name	Type	Nullable	Description
namespace	STRING	NO	The partner namespace.
email	STRING	NO	The email address of the recipient.
event_time	TIMESTAMP	NO	The date and time the system was informed about the event.
total	STRING	NO	The total amount spent in purchase.
order_id	STRING	NO	The ID for the order. This is most often the ID recorded from the website or feed, but when the upstream data source omits the order id we generate an arbitrary value.
product_ids	STRING	NO	A pipe-separated list of products purchased.

Export Analytics