File Layouts for Email

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record.

NOT POPULATED AT THIS TIME

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Email address that initiated the bounce event

The email address of the response event may differ from the email address in the List. This is because recipients can forward messages from one email account to another before ultimately handling the message.

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Hard or Soft bounce

H = Hard bounce

S = Soft Bounce

Bounce category value (e.g. USER_NOT_FOUND, CONNECTION_REFUSED, etc.)

The bounce message as provided by the ISP.

ISP bounce message: Informational text the ISP provides when bouncing a message.  This informational text is important in determining if a block has occurred, and also includes ways to contact the ISP regarding questions

The “bounced” message’s subject line value

Additional data for you to understand how to best follow up with complaints, bounces, skips and changed contact data

Possible values depend upon the subject Channel for the given event:

• Email Channel: Recipient’s email address (from the List)

• Mobile Channel: Recipient’s mobile number (from the List)

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

The name of the link.

The LINK_NAME value from the campaign’s link table

Numerical identifier used for click tracking

The link category value.

The LINK_CATEGORY value from the campaign’s link table

The URL of the clicked link

Available only if enabled for your account.

The User Agent String, which identifies the user’s device and browser version.

The user’s operating system.

NOTE: This field contains legacy device data and will be deprecated in a future release.

The user’s browser.

NOTE: This field contains legacy device data and will be deprecated in a future release.

The user’s browser type.

NOTE: This field contains legacy device data and will be deprecated in a future release.

Available only if enabled for your account.

The user’s operating system.

Available only if enabled for your account.

The user’s operating system vendor.

Available only if enabled for your account.

The user’s browser.

Available only if enabled for your account.

The user’s browser type.

Available only if enabled for your account.

The user’s device type.

The version of the MVT campaign

The date and time of the MVT run

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Available only if enabled for your account.

IP address of the device from which the recipient clicked.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Method by which the complaint was captured:

• SP:Spam Complaint

• SP:Spam Complaint Transfer (Complaints that were obtained via the Oracle Responsys 5.x implementation during the first 30-60 days after switching to Oracle Responsys 6.x)

Recipient’s email address that reported the spam complaint. If recipients have forwarded the message to a second (or third) email address, this is the email address used to make the complaint.

NOTE: This may differ from the email address in the List. This is because recipients can forward messages from one email account to another before ultimately complaining.

ISP of the recipient’s email address (e.g. Yahoo!, Hotmail, etc.)

If the ISP is unknown / uncategorized, a value of “Other” is presented.

Recipient’s email address that accepted the spam complaint report.

The email address of the spam complaint event may differ from the email address in the List. This is because recipients can forward messages from one email account to another before ultimately complaining.

Hardcoded to “0”, which translates to AUTO_SPAM.

Additional data for you to understand how to best follow-up with complaints, bounces, skips and changed contact data

Possible values depend upon the subject Channel for the given event:

• Email Channel: Recipient’s email address (from the List)

• Mobile Channel: Recipient’s mobile number (from the List)

Date the complaint was reported to the ISP.

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Application / module that initiates the event

Conversion / Purchase events are initiated / reported by an external source (your Web site), so this value will always be Unknown.

Exported value is “Source Value” found in the Source Identification Values table.

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

The name of the link that initiated the Conversion.

The LINK_NAME value from the campaign’s link table

Numerical identifier used for click tracking

The link category value.

The LINK_CATEGORY value from the campaign’s link table

The URL of the “clicked” link that initiated the Conversion

The order ID value of the specific order as passed by you when registering the Conversion.

The value from the OrderID name-value pair when calling the Conversion Tracking image pixel

The total amount of the order as passed by you when registered in the Conversion.

The value from the OrderTotal name-value pair when calling the Conversion Tracking image pixel

The total number of items in the order as passed by you when registering the Conversion / Purchase

The value from the NumItem name-value pair when calling the Conversion Tracking image pixel

Available only if enabled for your account.

The User Agent String, which identifies the user’s device and  browser version.

The user’s operating system.

NOTE: This field contains legacy device data and will be deprecated in a future release.

The user’s browser.

NOTE: This field contains legacy device data and will be deprecated in a future release.

The user’s browser type.

NOTE: This field contains legacy device data and will be deprecated in a future release.

Available only if enabled for your account.

The user’s operating system.

Available only if enabled for your account.

The user’s operating system vendor.

Available only if enabled for your account.

The user’s browser.

Available only if enabled for your account.

The user’s browser type.

Available only if enabled for your account.

The user’s device type.

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Available only if enabled for your account.

IP address of the device from which the recipient clicked.

Numerical value that denotes the event type for the given event transaction. See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Email address of the recipient. The value depends on the launch conditions:

• Live Launch: the Value is the email address from the List

• Proof Launch to a Proof List: the Value is the email address from the Proof List

• Proof Launch to specific email address(es) or Proof Launch personalized against Proof List: Value is the email address specified during the Proof Launch setup

Domain value of the recipient’s email address (e.g. yahoo.com)

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

See SENT

Numeric identifier of dynamic content that was sent

Message size in bytes

See SENT

Additional data for you to understand how to best follow up with complaints, bounces, skips and changed contact data.

Possible values depend upon the subject Channel for the given event:

• Email Channel: Recipient’s email address (from the List)

• Mobile Channel: Recipient’s mobile number (from the List)

Reason for the failure to send the message

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Available only if enabled for your account.

The User Agent String, which identifies the user’s device and browser version.

The user’s operating system.

NOTE: This field contains legacy device data and will be deprecated in a future release.

The user’s browser.

NOTE: This field contains legacy device data and will be deprecated in a future release.

The user’s browser type.

NOTE: This field contains legacy device data and will be deprecated in a future release.

Available only if enabled for your account.

The user’s operating system.

Available only if enabled for your account.

The user’s operating system vendor.

Available only if enabled for your account.

The user’s browser.

Available only if enabled for your account.

The user’s browser type.

Available only if enabled for your account.

The user’s device type.

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Available only if enabled for your account.

IP address of the device from which the recipient clicked.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Available only if enabled for your account.

The User Agent String, which identifies the user’s device and browser version.

Available only if enabled for your account.

The user’s operating system.

Available only if enabled for your account.

The user’s operating system vendor.

Available only if enabled for your account.

The user’s browser.

Available only if enabled for your account.

The user’s browser type.

Available only if enabled for your account.

The user’s device type.

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Available only if enabled for your account.

IP address of the device from which the recipient clicked.

Numerical value that denotes the event type for the given event transaction.

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

The value depends on the launch condition:

• Live Launch: The RIID is drawn from the distribution List object

• Proof Launch personalized against the live distribution List: The RIID is drawn from the distribution List object

• Proof Launch personalized against the Proof List: The RIID is drawn from the Proof List object

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s email address

The value depends on the launch conditions:

• Live Launch: the Value is the email address from the List

• Proof Launch to a Proof List: the Value is the email address from the Proof List

• Proof Launch to specific email address(es) or Proof Launch personalized against Proof List: Value is the email address specified during the Proof Launch setup

Domain value of the recipient’s email address (e.g. yahoo.com)

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Ignore

Numeric identifier of dynamic content that was sent

Message size in bytes

If the message was sent with multiple segments, this information is not usable. It is, however, usable for single segment sends (PR:Value). 

Additional data for you to understand how to best follow up with complaints, bounces, skips and changed contact data

Possible values depend upon the subject Channel for the given event:

• Email Channel: Recipient’s email address (from the List)

• Mobile Channel: Recipient’s mobile number (from the List)

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account. Organizational unit ID of the targeted organizational unit.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event.

Date the event transaction was stored into the Event DB.

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s email address

The value depends on the launch conditions:

• Live Launch: the Value is the email address from the List

• Proof Launch to a Proof List: the Value is the email address from the Proof List

• Proof Launch to specific email address(es) or Proof Launch personalized against Proof List: Value is the email address specified during the Proof Launch setup

Domain value of the recipient’s email address (e.g. yahoo.com)

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

N/A

Numeric identifier of dynamic content that was sent

Message size in bytes

See Sent.

Additional data for you to understand how to best follow up with complaints, bounces, skips and changed contact data

Possible values depend upon the subject Channel for the given event:

• Email Channel: Recipient’s email address (from the List)

• Mobile Channel: Recipient’s mobile number (from the List)

Reason for skipping the message

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Form

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Numerical identifier of the Form

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Form

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the Form

Name of the Form

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the specific campaign

Numerical identifier of the launch instance

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Application / module that initiates the event

Exported value is “Source Value” found in the Source Identification Values table.

Method used to add the recipient to the List (does not include bulk loads).

• DV:MERGE (Data Viewer edit / merge)

• FR:MERGE (Update / insert via a Form as a result of a form submission)

• PR:MERGE

• WS:MERGE

• Confirmed Opt-in

Recipient’s email address

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Campaign

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the specific campaign

Numerical identifier of the launch instance. The value of the launch ID is null in the following cases:

• When you manually opt out a record

• When an unsubscribe request is sent via email without a complete header

• When the recipient clicks the Spam button, in some cases the ISP does not send the complete header with the request

Recipient’s preferred email content format, HTML or Text.

H = HTML

T = Text

N = No Preferred

M = Multi-part

Application / module that initiates the event

Exported value is “Source Value” found in the Source Identification Values table.

Method used to add the recipient to the List (does not include bulk loads)

• SP: Spam Complaint

• SP: Spam Complaint Transfer

• Unsubscribe Page

• US: Unsubscribe

• US: Unsubscribe Transfer

• DV: Merge (Data viewer)

• FR: Merge (Form)

• PR: Merge (Program)

• WS: Merge (Webservices)

Email address that initiated the OptOut event. The email address of the response event may differ from the email address in the List; Recipients often forward messages from one email address to another where the recipient ultimately handles the message

Additional data for you to understand how to best follow-up with complaints, bounces, skips and changed contact data

Possible values depend upon the subject Channel for the given event, provided the RIID value is included in the unsubscribe request.

• Email Channel: Recipient’s email address (from the List)

• Mobile Channel: Recipient’s mobile number (from the List)

• Default: Email address that initiated the OptOut event.  (This usually occurs when an unsubscribe request is made via an email reply.)

The identifier of the test version

The date and time of the personalization message

Applies only if Targeting By Organization is enabled for the account.

Organizational unit ID of the targeted organizational unit.

Numerical value that denotes the event type for the given event transaction. See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Program

Unique ID assigned for this specific List record

A unique identifier of the recipient/record that matches a customer ID or unique identifier in your system of record

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier for the given Program

Numerical identifier of the recipient’s specific entry into the program

The Program name

The version of the Program used by this event

Numerical value that denotes the event type for the given event transaction

See Contact Event Type IDs for more information.

Account number (for example. 1234)

Numerical identifier for the List object used by the Program

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the given Program

The Program name

Account number (for example. 1234)

Numeric identifier of the List object used by the Campaign

Date and time the system was informed about the event

Date the event transaction was stored into the Event DB

Numerical identifier of the specific campaign

Numeric identifier of the launch instance

Name of the dynamic content region

Name of the dynamic content rule

The type of content for the selected rule:

text=A block of text explicitly added in the dynamic content rule

doc=The path and name of a document in the content repository

no =No content

The HTML code / text of the content region

Recipient’s preferred email content:

H = HTML

T = Text

N = No Preferred

M = Multi-part

Numeric hash of the signature

Ignored