About Contact Event Data output files

Contact Event Data output files contain information about each Event transaction. Each row represents one Event transaction/occurrence. In general, each output file contains data for only one Event Type. However, some output files contain information about multiple closely related Event Types. For example, the Form Contact Event Data contains information about Form submissions and Form views.

Each Contact Event Data output file is a text flat file delimited the character you choose: comma, semi-colon, tab, or pipe character. All rows in the output file are related to your system of record data or reporting data based on the CUSTOMER_ID value (a unique identifier for each recipient).

The file layouts presented in this document contain the following information:

  • Field Name

  • Type and Maximum length (where applicable)

  • Null?: Whether or not the field is nullable.  A value of NO in this column means that the field is a required value for the event and won’t be null. A value of YES means that the field may have a null value.

  • Description/Comments: Provides additional information about the field.

For all types of event feed, all line breaks in text fields are automatically replaced with spaces, so that a single record is not broken into multiple rows.

NOTE: Oracle Responsys tracks many user-initiated behavioral events (e.g. opens and clicks) via URLs sent back to Oracle Responsys. These URLs can become corrupted before Oracle Responsys receives them, and the corrupted data is saved as-is into Oracle Responsys event logs. Although URL corruption might occur for a variety of reasons that Oracle Responsys does not cause and cannot fix, we provide a solution for identifying the problem and redirecting valid and invalid rows. For more information, see Troubleshooting Data Corruption.

For Contact Event Data output files that contain information about multiple event types (for example, the Form Event Contact Data output), each event type is identified by an Event Type ID value.

See Contact Event Type IDs for a mapping of Contact Event Type ID values to their respective Event Names and Actions. See File Layouts for a description of the columns in the Contact Event Data output files.

NOTE: In 18C, Responsys moved to a new data framework that allowed us to detect a large number of devices and their attributes with improved accuracy. This new data framework has now been applied to applicable CED Feeds for 18D. With the new device data framework, we have added new derived fields to applicable CED feeds. These fields contain various device attributes such as operating system, operating system vendor, browser, browser type, and device type. The new fields and attribute values will be different from legacy device fields and attribute values.

The fields OPERATING_SYSTEM, BROWSER, and BROWSER_TYPE will still be exported if your account was enabled to receive them in CED feeds. However, they contain legacy device data and will be deprecated in a future release.

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 Contact Event Data output is the data accumulated since the last successful Contact Event Data extract was produced. Therefore, it is quite likely the day’s Contact Event Data output file may contain data for more than a single 24-hour period.

Contact Event Data output files

See Contact Event Data output files for a full list.

Contact Event Type IDs

These Contact Event Type IDs are used in Contact Event Data output files to identify the event in each row.

Event ID

Event Name

Action

Event Type Category

1

Sent

_Sent_

Standard

2

Bounced

_Bounced_

Standard

4

Opened

_Opened_

Standard

5

Clicked

_Clicked_

Standard

6

Converted

_Conversion_

Standard

7

Unsubscribed

_Unsubscribed_

Standard

8

Failed

_Failed_

Standard

10

Skipped

_Skipped_

Standard

11

Entered_program

_Entered_program_

Program

12

Ended_program

_Ended_program_

Program

14

Viewed_form

_Viewed_form_

Form

15

Submitted_form

_Submitted_form_

Form

16

Forwarded

_Forwarded_

Standard

17

Form_Abandoned

_Form_Abandoned_

Form

18

Spam_Complaint

_Spam_Complaint_

Standard

19

Purchased

_Purchased_

Standard

20

Spent

_Spent_

Standard

21

Joined_List

_Joined_List_

List (Occurs when a recipient opts in to a list)

22

Activated_EMail

_Activated_EMail_

List

23

Deactivated_EMail

_Deactivated_EMail_

List

24

Activated_Mobile

_Activated_Mobile_

List

25

Deactivated_Mobile

_Deactivated_Mobile_

List

26

Activated_Postal

_Activated_Postal_

List

27

Deactivated_Postal

_Deactivated_Postal_

List

28

EMail_ChangeOfAddress

_EMail_ChangeOfAddress_

List

29

Mobile_ChangeNumber

_Mobile_ChangeNumber_

List

30

Postal_ChangeOfAddress

_Postal_ChangeOfAddress_

List

31

Deleted_From_List

_Deleted_From_List_

List

32

EnteredEnded_Program

_EnteredEnded_Program_

Program

44

Email Async Open or Auto Opened

_AUTO_OPENED_

Standard

401

SMS Sent

_SMS_Sent_

SMS

403

SMS Delivery Receipt

_SMS_Delivery_Receipt_

SMS

407

SMS Opt Out

_SMS_OptOut_

SMS

408

SMS Failed

_SMS_Failed_

SMS

410

SMS Skipped

_SMS_Skipped_

SMS

502

Push Bounced

_Push_Bounced_

Push

509

Push Inbox Sent

_Push_Inbox_Sent

Push

515

Push Clicked

_Push_Button_Clicked_

Push

522

Push Uninstall

_Push_Uninstall_

Push

10101

Web Push Opt In

_WebPush_OptIn_

Web Push

10101

Web Push Opt Out

_WebPush_OptOut_

Web Push

10101

Web Push Sent

_WebPush_Sent_

Web Push

10102

Web Push Bounced

_WebPush_Bounced_

Web Push

10104

Web Push Opened

_WebPush_Opened_

Web Push

10105

Web Push Button Clicked

_WebPush_ButtonClicked_

Web Push

10110

Web Push Skipped

_WebPush_Skipped_

Web Push

10119

Web Push Converted

_WebPush_Converted_

Web Push

10132

Web Push Closed

_WebPush_Closed_

Web Push

1010123

Web Push Failed

_WebPush_Failed_

Web Push

Launch Status Values

The LAUNCH_STATE Feed output uses a launch_status column to indicate the launch state at the time of the event transaction. Ideally, a series of launch state events will start with Build Work List and finish with Complete, meaning the campaign launch activity completed. These values can apply to either a campaign or a form.

These are the launch_status values:

Launch Status Value

Description

Comments

N

Unknown

 

R

Requested

 

B

Building Work List

Creating the final list of recipients, accounting for recipients who are Undeliverable (the deliverability permission status), and opted-out (if the campaign is a promotional campaign). Oracle Responsys also identifies the recipients to skip due to suppression settings.

L

Work List Complete

The list of recipients for whom Oracle Responsys will attempt to create a personalized message

S

Sending

Sending the messages

C

Completed

The launch process has completed for the given campaign launch.

P

Paused

The launch process was paused.

T

Stopped

The launch process was stopped.

M

Resumed

A paused launch was subsequently resumed.

F

Failed

The launch process failed.

V

Recovered

The launch was recovered by Support.

Launch Type Values

The LAUNCH_STATE Feed output uses a launch_type column to indicate the way a launch was requested at the time of the event transaction.

These are the launch_type values:

Launch Type Value

Description

Comments

S

Standard

Ad hoc launches either via "launch now" or scheduled launches

T

Proof

 

X

Spam Score

A launch used to check the campaign’s spam score.

V

Preview

 

P

Triggered

Launches via form follow-up or the API’s triggeredCampaignMessage method. A launch type of P is created when the campaign is created.

Before 6.12.1, “P” also applied to Program.  However, starting with 6.12.1, campaigns launched via Program use the R launch type.

U

Usage

Campaign Usage / Form Usage. The launch record is created when users select Campaign Usage or Form URLs from the object's context menu. Used primarily for testing purposes.

R

Program Triggered

Program Triggered Launch.  As of 6.12.1, campaigns launched via Program no longer use the Triggered (P) launch record.

This launch type is created when the program is published.

Q

Program Triggered  Launch

Triggered Program Proof Test Launch.

 

Source Identification Values

Several Contact Event Type data output files have a column named SOURCE that identifies the application or module that initiated (raised) the specific event. For example, if a recipient opts-in via a hosted form, the SOURCE value is Form for the OPTIN Contact Event Type Data record.

These are the source identification values:

SOURCE Value

Abbreviation

Comments

Form

FR

 

Program

PR

 

User Interface

UI

 

UI – Data Viewer

UV

 

UI – List Upload

UU

 

Exchange – Webservice

XW

Oracle Responsys API (aka Web Services API)

Exchange – Connect

XC

Connect

Exchange – Salesforce Connector

XS

Salesforce Connector integration module

Spam Complaint

SC

 

Reply-To Email

RT

Email reply sent to a Oracle Responsys -hosted reply to address, and processed by the Reply To Handling feature

Unknown

UN

 

Unsubscribe Page/Link

UL

 

Next steps

About Contact Event Data output files

File Layouts for Launch State

Learn more

Configuring a Contact Event Data export job

File Layouts