Contact Event Data output files

The tables in this section provide a description of each Contact Event, its corresponding data filename, and the type of events or actions captured in the output file.

NOTES:

  • The output data filename is the name of the final text flat file that contains the output data. The filename of the file(s) available on the file server depends on your configuration of the Contact Event Data job. For contact interaction and contact permission events, the file name will contain SMS, MMS, PUSH, or WEBPUSH if the feed is for those channels. (Files for Email omit the channel name.) For example, a Clicked events feed for Email could have the file name 1234_CLICK_20190103_130532.txt, but a Clicked events feed for SMS could have the file name 1234_SMS_CLICK_20190103_231059.zip.

  • The output file extension is based on how the Connect job is set up: compressed files have a zip extension; encrypted files have a “gpg” extension; files that you choose to neither encrypt nor compress will be plain text with a “txt” extension; ready and count files have extensions based on your settings in Connect.

Launch Events

Event Feed Type Description Output File Name Comments

Launch State

Data regarding when a launch starts, pauses, resumes, and stops

accountID_
LAUNCH_STATE_
YYYYMMDD_
HH24MISS.txt

CUSTOMER_ID Support: N/A

Custom Columns Support: N/A

Use this file to create a lookup table for mapping LAUNCH_ID value that appears in other output files.

This mapping is particularly important for triggered launches, where the launch date and send date are not necessarily the same.

Response / Standard Events

Event Feed Type

Description

Output File Name

Comments

Bounced

Bounce transactions

accountID_
BOUNCE_
YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: No

Custom Columns Support: No

Starting in version 6.9, the Bounced Event Feed Type does not support Custom Columns. 

Clicked

Tracked links

accountID_CLICK_YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

CUSTOMER_ID and Custom Column values are populated from the event URL data.

Complained

Spam complaints reported by ISPs via feedback loops

accountID_
COMPLAINT_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: No

Custom Columns Support: No

Converted

Conversions registered by Conversion Tracking functionality

accountID_
CONVERT_
YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

CUSTOMER_ID and Custom Column values are populated from the event URL data. Includes Purchase events.

Failed

A “Failed” event per recipient per campaign launch

accountID_FAIL_
YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

The following conditions are some, but not all, possible reasons for failure to launch a specific message:

  • No Response from any of Number MTAs

  • No Response from any of Number MTAs (and SMTP Server Busy on Failover)

  • SMTP Error

  • SMTP Error (and SMTP Server Busy on Failover)

  • SMTP Server Busy

CUSTOMER_ID and Custom Column values must be part of the profile list or Personalization data sources.

Opened

Tracks individual recipients who opened campaign messages

accountID_OPEN_
YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Oracle Responsys tracks open events via a 1x1 pixel image; recipients must allow images to be displayed in order to know the recipient has opened the message.

CUSTOMER_ID and Custom Column values are populated from the event URL data.

Does not contain contain open events classified as Auto Opened. This data is available in the CED feed file for Auto Opened events.

Sent

Messages by recipient by campaign launch that were successfully sent to the target mail server

accountID_SENT_
YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Skipped

Suppressions

accountID_
SKIPPED_YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

The following conditions are some, but not all, possible reasons for skipping a recipient when launching a campaign:

  • Email domain is suppressed at the pod level, the account level, or at the campaign level

  • Email address is suppressed at the pod level, the account level, or the campaign level

  • Invalid email address

  • Missing data for $replacementField$

  • Personalization errors, including problems with <Format Type> message or missing data for <Dynamic Values> such as Variable, Data Field, or Document.

CUSTOMER_ID and Custom Column values must be part of the profile list or Personalization data sources.

Dynamic Content

Dynamic content

accountID_DYNAMIC_CONTENT_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Auto Opened

Tracks campaign message opens that Responsys attributes to privacy protection-enabled mail applications, such as iOS 15 native mail clients.

accountIDAUTO_OPEN
YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Oracle Responsys tracks open events via a 1x1 pixel image; recipients must allow images to be displayed in order to know the recipient has opened the message.

Responsys classifies all Opened events with only "Mozilla/5.0" in the user-agent string as Auto Opened events.

CUSTOMER_ID and Custom Column values are populated from the event URL data.

 

Form Events

Event Feed Type

Description

Output File Name

Comments

Form

 

Form Submission and view events

accountID_FORM_YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes (Form Submits only)

Read the EVENT_TYPE_ID column for the specific event type designation.

Form Submits: Custom Column values are populated based on incoming parameters (GET / POST request) where names match Custom Column names.

Form Views: Custom Column values ARE NOT supported.

 

 

Form State

Captures when a form is enabled or disabled

accountID_FORM_STATE_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: N/A

Custom Columns Support: N/A

Permission Events

Event Feed Type

Description

Output File Name

Comments

Opted In

Any individual change to permission status value

accountID_OPT_IN_YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: No

An OptIn event is recorded if:

  • A new record is inserted with an OptIn permission status

  • An existing record’s permission status is changed from OptOut to OptIn

Permission status changes via:

  • View/edit data screen

  • Form submissions

  • Program Set Data calls

  • Web services

Opted Out

Any individual change to permission status value

accountID_
OPT_OUT_
YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

An OptOut event is recorded if the existing record has a permission status of OptIn and is being changed to OptOut.

Permission status changes via:

  • View/edit data screen

  • Form submissions

  • One-click OptOut form submission

  • Unsubscribe via an email reply (when the reply address is hosted by Oracle Responsys)

  • Program Set Data calls

  • Web services

Program Events

Event Feed Type

Description

Output File Name

Comments

Program

Information for Program Entry and Program Exit events

accountID_
PROGRAM_
YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: N/A

Custom Columns Support: N/A

Who entered a Program when; who exited a Program when

Program State

Includes information about when a Program is published or unpublished

accountID_
PROGRAM_
STATE_YYYYMMDD_HH24MISS.txt

CUSTOMER_ID Support: N/A

Custom Columns Support: N/A

SMS Events

Event Feed Type

Description

Output File Name

Comments

MO Forward Sent

 

 

CUSTOMER_ID Support: Yes

Custom Columns Support: No

MO Forward Failed

 

 

CUSTOMER_ID Support: Yes

Custom Columns Support: No

Push Events

Event Feed Type

Description

Output File Name

Comments

Button Clicked

Tracks the responses of recipients to Interactive Push Notification Campaigns.

accountID_PUSH_
BUTTON_CLICKED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: No

Uninstall

Tracks app uninstalls.

accountID_PUSH_
UNINSTALL_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: No

Message Center Events

Event Feed Type

Description

Output File Name

Comments

Message Center Sent

Messages by recipient by campaign launch that were successfully sent to the target mobile app's message center

accountID_PUSH_INBOX_SENT_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Message Center Failed

A "Failed" event per recipient per Message Center campaign launch

accountID_PUSH_INBOX_FAILED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

The following conditions are some, but not all, possible reasons for failure to launch a specific message:

  • No Response from any of Number MTAs

  • No Response from any of Number MTAs (and SMTP Server Busy on Failover)

  • SMTP Error

  • SMTP Error (and SMTP Server Busy on Failover)

  • SMTP Server Busy

CUSTOMER_ID and Custom Column values must be part of the profile list or Personalization data sources.

Message Center Skipped

Suppressions

accountID_PUSH_INBOX_SKIPPED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

The following conditions are some, but not all, possible reasons for skipping a recipient when launching a campaign:

  • Email domain is suppressed at the pod level, the account level, or at the campaign level

  • Email address is suppressed at the pod level, the account level, or the campaign level

  • Invalid email address

  • Missing data for $replacementField$

  • Personalization errors, including problems with <Format Type> message or missing data for <Dynamic Values> such as Variable, Data Field, or Document.

CUSTOMER_ID and Custom Column values must be part of the profile list or Personalization data sources.

Message Center Displayed

Tracks Message Center messages that are displayed to mobile app users in a short/preview format (usually as part of a list)

accountID_PUSH_INBOX_DISPLAYED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Message Center Opened

Tracks when mobile app recipients tap Message Center messages to view the detailed promotional content

accountID_PUSH_INBOX_OPENED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

Oracle Responsys tracks open events via a 1x1 pixel image; recipients must allow images to be displayed in order to know the recipient has opened the message.

CUSTOMER_ID and Custom Column values are populated from the event URL data.

Message Center Clicked

Tracks when mobile app recipients click "call to action" links in opened Message Center campaign messages

accountID_PUSH_INBOX_CLICKED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: Yes

CUSTOMER_ID and Custom Column values are populated from the event URL data.

Web Push Events

Event Feed Type

Description

Output File Name

Comments

Closed

Tracks closed Web Push Notifications

accountID_WEBPUSH_
CLOSED_YYYYMMDD_HH24
MISS.txt

CUSTOMER_ID Support: Yes

Custom Columns Support: No

Next steps

About Contact Event Data output files

File Layouts for Launch State

Learn more

Configuring a Contact Event Data export job

File Layouts