exporting contact event data guide

8/3/2019 Exporting Contact Event Data Guide

1/26

Last Update d: Novem ber 8, 2011


2/26

/ Responsys Interact Connect / Expo rtin g Contact Event Data / responsys.com i

Abou t expo rti ng Cont ac t Event Data .......................................................................................................................................... 2

Con fi gu ring a Con tact Even t Data expor t jo b ............................................................................................................................ 2

Using Cus tom Co lu mns .................................................................................................................................................................. 3

Abou t Cont ac t Even t Data ou tpu t fi les ....................................................................................................................................... 4

Contact Event Data output files ............................................................................................................................................... 5

Contact E vent Ty pe IDs ............................................................................................................................................................. 8

Launch Status Values ................................................................................................................................................................. 9

Launch Ty pe Values .................................................................................................................................................................. 10

Source Identification Values ................................................................................................................................................... 10

Fi le Layo uts ..................................................................................................................................................................................... 1

Launch State ............................................................................................................................................................................... 1

Bounced ...................................................................................................................................................................................... 12

Cli cked ........................................................................................................................................................................................ 13

Complain t ................................................................................................................................................................................... 14

Conver te d ................................................................................................................................................................................... 16

Fai led ............................................................................................................................................................................................1

Op ened ....................................................................................................................................................................................... 18

Sent .............................................................................................................................................................................................. 1

Skippe d ...................................................................................................................................................................................... 20

Form ............................................................................................................................................................................................ 2

Form Sta te .................................................................................................................................................................................. 22

Op te d In ...................................................................................................................................................................................... 22

Op te d Ou t .................................................................................................................................................................................. 23

Program ..................................................................................................................................................................................... 24

Program State ............................................................................................................................................................................ 25

Accessing the Resp onsys File Server ........................................................................................................................................ 25


3/26

/ Responsys Interact Connect / Expo rti ng Contact Event Data / responsys.com 2

The Export Contact Event Data feature lets you extract behavioral and other raw data about events from account-

wid e and campaign-speci fic response activities. For example, logs can tell you on a row-by-r ow basis who was

sent campaign X and when it was sent.

With this information, you can keep your system of record up to date with compliance data or load data into your

reporting system or other third party applications. Once you have exported the data, you can use it for:

Audit tracking

Scrubbing data

Downloading to ex ternal programs

Analyzing campaigns using your analytics or other software

Informa tion is expor ted t o flat te xt files that are available on the Responsys file server associated wit h your

account (fo r examp le, files.responsys.net or files.dc2.responsys.net) for 14 days. You can have the exp or t d ata files

package d in indiv idual ZIP archives and can also specify GPG/PGP encryp tion.

After you run an export for the first time, each subsequent report contains an incremental update of events that

occur red since the last successful expor t. You use the Launch_State values to create a looku p table o f events so

that you can match more recent events to an existing launch record. This is particularly important for triggeredevents where the launch date and send da te are not necessarily the same.

A Contac t Event Data Expor t job lets you select the data you want t o see, the format and locatio n of the expor t

file, and ho w of ten the file is created. Data is only available for 3 0 days, so best prac tice is to run expo rt j obs on a

daily basis.

Alth ough the da ta is available for expor t fro m the database for 30 days, the zip files, once you create them,

are only available on the server for 14 days.

You create and maintain a Contac t Event Data Export j ob the same way as other Interac t Connect Expor t jobs.Al thou gh you can create multipl e Contact Event Data Expor t jobs for each account, you can only have one active

Export Contact Event Data job per Event t ype. For example, you could set up one export job to out put Bounced

Event information and another to outpu t Complaint Event information, but you could not configure t wo active

export jobs to out put Bounced Event informati on.

1 From Interact Connect cl ick .2 Choose .3 On the Source page of the Wi zard, click check boxes for the Event Types you want to do wnload. Click .

We reco mmend that you star t wit h these event t ypes; you can include others as well.

Launch State

Opted In Opted Out

Complained

Bounced

4 Click .5 On the Target File page, in the File Location area, enter the access specifications for a Responsys file server or

choose an external server.

The File Location fo r a Responsys File Server w ould look like this:

Server: or (Check with Suppor t for your file server locatio n.)


4/26

/ Responsys Interact Connect / Expo rtin g Contact Event Data / responsys.com 3

Username: _scp( is the shor t name of your Responsys Interact Accoun t. It appears to the righ t o f the @ in

your admin login: admin@ )

Path: choose a location.

6 In the area, choose settin gs for the expo rt file. Select a character set.

If you have internati onal characters in your DB, select .

Choose as the delimit er bet ween the fields (columns) in the dow nload file.

You can also choose comm a, semicolon, or pip e as the delimiter, but tabs wo rk best, especially if yo ure

including custom columns.

Choose whether t o enclose text colu mns in single quotes, double qu ote, or none.

Turn on the setting to expo rt column headers as the first line in the

exported fi le.

Choose whether to encrypt or compress your export job as a .zip file (or both).Alt hou gh you can choose not t o com press or encrypt the file, the resulting raw tex t file takes significantly

longer to do wnload (and consumes more stora ge space on your file system and ours).

Choose whether t o create a Ready File for validati on after the file is exporte d. Enter a file extension ifneeded.

The optio ns are none, an empty file, and a record coun t. Use an empty file to validate the comp leti on ofyour do wnload process. Use a record count f i le (recommended) to com pare simple record counts to verify

that all expect ed recor d coun ts were transferred. This is similar to the way the coun t file is used to validate

a job impo rt file. The Ready file and your expo rt jo b have the same name.

7 Click .8 On the page, select whethe r to receive email not ificati on after each job is run, only after a failed job,

or not at all. Enter one or more email addresses if needed. Click .

9 On the page, choose how oft en you want to expo rt the file (once a day is typicall y sufficie nt). Click.

10 On the page, choose whether to activa te or deactivat e the expor t. Ad d a name anddescript ion, and click .

The new job is listed on t he All Jobs tab.

There are times when the standard Contac t Event Data columns do not cap ture all the data elements you wan t to

report on, or you might need to feed additional information back to your System of Record. For example, you

migh t use the! MasterData/C ONTACT_LIST COUNTRY_ISO3 list column and wan t to include t his informati on in the

Contact Event Data output f i le.

Each account can have up to twelve custom columns. All custom column information per event must fit within a

field defined as varchar2(40 00 ), and must account for XML meta-data used to store the custom- column name-

value pair informati on in the given column. Custom column values are drawn from the Campaigns List or

associated Personalization Data sources as defined in the Campaig n Dashboard.

For more informati on about the Contact Event Data outpu t f i les that support custom columns, seeContact Event

Data Output Files.

The source Event determines how custom column information is captured.

Sent, Skipped, and Failed Events The Wo rklist based on the recipien t pro file in the List

Form Submission Events The incomin g name-value pair passed during the form post


5/26


Clicked and Converte d Events The value of the click or conver t event's querystrin g name /value pair.

This is because values set in the click tracking URL at the time of launch

for a campaign are typically better for campaign and recipient tracking

and attri but ion pro jects. Similarly, conversion paramete r values

determined and set at conversion time are typically the appro priate

source of custom field data.

Wh en tracking custo m field values for click events and conver t events, the name in the name-value pair must be

the tar get custo m colum n name. These are the expecte d for mats for links in email campaigns:

For example, if cid, vid, and oid are defined as custom fields, these incomin g values are persisted for this click

event and available for exp ort as Clicked Event da ta. Similarly, custom fields fo r Converte d Events should be

passed as name-value pairs in the conversion t racking URL and wo uld be specified by we bsite code at con version

time.

1 Make sure the desired custom data element /c olumn exists in the List or a Supple mental Data table associatedwith the campaign.

If a column of the same name exists in more than one Supple mental Table for a campaign, make sure the

custom column value is the same everyw here its used.

2 Log in as an admin user and click the link.3 Click .4 Click .5 Enter a name and description (optional) for the new custom column.

Make sure the name is the same as the column name in the List table /o bjec t.

6Click .The configurati on will apply f or all future launches.

Contact Event Data out put files contain infor matio n about each Event transactio n. Each row repr esents one Event

transaction /o ccurr ence. In general, each outpu t file contains data for only one Event Type. However, some outpu t

files contain informati on about multi ple closely related Event Types. For example, the Form Contac t Event Data

contains information about Form submissions and Form views.

Each Contac t Event Data outpu t file is a text flat file delimite d the character you choose: comma, semi-col on, 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 i dentifier for each recipient ).

For Contact Event Data output f i les that contain information about multiple event ty pes ( for example, the Form

Event Contact Data out put ), each event typ e is identified b y an Event Type ID value.

SeeContact Event Type IDsfor a mapping of Contac t Event Type ID values to their respect ive Event Names and

Ac tions. SeeFile Layoutsfor a descrip tion of the columns in the Con tact Event Data outp ut files.

All ext racted date and ti me values are format ted in Coor dinated Universal Time (UTC) for co nsistency and ease of

com parison. The event infor matio n contained in each Contact Event Data out pu t is the data accumulated since the


6/26


last successful Contact Event Da ta extract was prod uced. Therefore, it is quite likely the days Contact Event Data

output file may contain data for more than a single 24-hour period.

The table below pr ovid es a descript ion of each Contact Event, its corresponding data filename, and the typ e of

events or actions captured in the output file.

The output data filename is the name of the final text flat file that co ntains the outp ut data. The filename ofthe file(s) available on the file server depends on your conf igura tion of the Cont act Event Data job; comp ressed

files have a zip extension; encryp ted files have a gp g extension; ready and count files have extensions based on

your settings.

Launch State Data

regarding

when a launch

starts, pauses,

resumes, and

stops

accountID_LAUNCH_

STATE_YYYYMMDD_

HH24MISS.txt

: N/ A

: N/ A

Use this file to create a lookup ta ble for map ping

LAUNCH_ID value that appears in other out put files.

This mapping is particularly impor tant for triggered

launches, where the launch da te and send date are not

necessarily the same.

Bounced Bounce

transactions

_BOUNCE_

_

.txt

: No

: No

Starting in version 6.9, the Bounced Event Feed Typ e

does not support Custom Columns.

Clicked Tracked links _CLICK_

_ .txt

: Yes

: Yes

CUSTOMER_ID and Custom Column values are

populated from the event URL data.

Complaint Spam

complaints

reported by

ISPs via

feedback loops

_COMPLAINT

_ _

.txt

: No

: No

Converted Conversions

registered byConversion

Tracking

functionality

_CONVERT_

_.txt

: Yes

: Yes


po pulated f rom the event URL data. Includes

Purchase events.


7/26


Failed A Failed

event per

recipient per

campaign

launch

_FAIL_

_ .txt

Yes

Yes

The following conditions are some, but not all,

possible reasons for failure to launch a specific

message:

No Response from any of Nu mbe r MTAs

No Response from any of Nu mber MTAs (andSMTP 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 pr ofile list or Personalization da ta sources.

Opened Tracks

individual

recipients who

opened

campaign

messages

_OPEN_

_ .txt

: Yes

: Yes

Interact tracks open events via a 1x1 pixel image;

recipients must allow imag es to be displayed in orde rto kno w the recipient has opened the message.


populated from the event URL data.

Sent Messages by

recipient by

campaign

launch that

were

successfully

sent to the

target mailserver

_SENT_

_ .txt

: Yes

: Yes

Skipped Suppressions _SKIPPED_

_

.txt

: Yes

: Yes

The following conditions are some, but not all,

possible reasons for skipping a recipient when

launching a campaign:

Email is suppressed at the pod level, the

account level, or at the campaign level

Email 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

message or missing data for

such as Variable, Data Field, or

Document.

CUSTOMER_ID and Custom Co lumn values must be

part of the pr ofile list or Personalization da ta sources.


8/26


Form Form

Submission

and view

events

_FORM_

_ .txt: Yes

: Yes (Form Submits only )

Read the EVENT_TYPE_ID column for the specific

event ty pe designation.

: Custom Column values are popula ted

based on incomin g paramete rs (GET / POST request)

where names match Custom Colu mn names.

: Custom Column values ARE NOT

supported.

Form State Captures when

a form is

enabled or

disabled

_FORM_STAT

E_ _

.txt

: N/ A

: N/ A

Opted In Any individual

change to

permission

status value

_OPT_IN_

_ .txt

: Yes

: No

An OptIn event is recorded if:

A new recor d is inserted wi th an OptIn per mission

status

An existing rec ords permi ssion status is changed

from OptOut to OptIn

Permission status changes via:

View/ edit data screen

Form subm issions

Program Set Data calls

Web services

Opted Out Any individual

change to

permission

status value

_OPT_OUT_

_

.txt

: Yes

: Yes

An OptOut event is recorded if the existing record has

a permission status of Op tIn and is being changed t o

OptOut.

Permission status changes via:

View/ edit data screen

Form subm issions

One-click Opt Out form submission

Unsubscribe via an email reply (when the reply

address is hosted by Responsys)

Program Set Data calls

Web services


9/26


Program Information

for Program

Entry and

Program Exit

events

_PROGRAM_

_

.txt

N / A

N /A

Who entered a Program when; who exited a Program

when

Program State Includes

information

about when a

Program is

published or

unpublished

_PROGRAM_

STATE_ _

.txt

: N/ A

: N/ A

These Contact Event Type IDs are used in Contact Event Data out put files to iden tify the event in each row.

-1 Not specified Not Used Standard

1 Sent _Sent_ Standar d

2 Bounced _Bounced_ Standard

4 Opened _Opened_ Standard

5 Clicked _Clicked_ Standard

6 Converte d _Conversion_ Standard

7 Unsubscribed _Unsubscribed_ Standard

8 Failed _Failed_ Standard

10 Skipped _Skipped_ Standard

11 Entered_pr ogra m _Entered_pr ogra m_ Program

12 Ended_pr og ram _Ended_pro gram_ Program

14 Viewed_form _Viewed_form_ Form

15 Submitted_form _Submitte d_form_ Form

16 Forwar ded _Forwar ded_ Standard

17 Form_Abandoned _Form_Abandoned_ Form

18 Spam_Complaint _Spam_Comp laint_ Standard

19 Purchased _Purchased_ Standar d

20 Spent _Spent_ Standard

21 Joined_List _Joined_List_ List Occurs when a recipien t opts in to a

list)

22 Ac tiva ted_EMail _Act ivate d_EMail_ List

23 Deactivate d_EMail _Deactivated_EMail_ List

24 Activa ted_Mobile _Activated_Mobile_ List


10/26


25 Deactivate d_Mobile _Deactivated_Mo bile_ List

26 Activa ted_Postal _Activated_Postal_ List

27 Deactivate d_Postal _Deactivated_Postal_ List

28 EMail_ChangeOfA ddr ess _EMail_ChangeOfA dd ress_ List

29 Mobile_ChangeNumber _Mobile_ChangeNumber_ List

30 Postal_ChangeOfAddress _Postal_ChangeOfAddress_ List

31 Deleted_Fro m_List _Deleted_From_List_ List

32 EnteredEnded_Program _EnteredEnded_Program_ Program

33 FTAF_Sent _FtaFSent_ FTAF

34 FTAF_Failed _FtaFFailed_ FTAF

35 FTAF_Skippe d _FtaFSkippe d_ FTAF

37 FTAF_Clicked _FtaFClicked_ FTAF

38 FTAF_Link _FtaFLink_ FTAF39 FTAF_Submi t _FtaFSubmi t_ FTAF

40 FTAF_Opened _FtaFOpened_ FTAF

41 FTAF_Converted _FtaFConverted_ FTAF

105 Social_clic k _Social_click_ Social

106 Social_conve rsion _Social_conversion_ Social

119 Social_pu rchase _Social_pu rchase_ Social

The LAUNCH_STATE Feed ou tpu t uses a launch_status column to ind icate the launch state at the ti me of theevent t ransaction. Ideally, a series of launch state events will start wi th Build W ork List and finish with Comp lete,

meaning the campaig n launch activi ty co mple ted. These values can appl y to either a campaign or a form.

These are the launch_status values:

N Unknown

R Requested

B Building Wo rk List Creating the final list of recipien ts, accounti ng for reci pients who

are Undeliverable ( the deliverab ility p ermission status), and

opte d-out (if the campaign is a promoti onal campaign). Interactalso identi fies the recipients to skip due to supp ression settings.

L Wo rk List Complete The list of recipients for whom Interact will attempt to create a

personalized message

S Sending Sending the messages

C Completed The launch process has comp leted for t he given campaig n

launch.

P Paused The launch pro cess was paused.


11/26


T Stoppe d The launch process was stop ped.

M Resumed A paused launch was subsequently resumed.

F Failed The launch process failed.

The LAUNCH_STATE Feed ou tpu t uses a launch_type column to indica te the way a launch was requested at t he

time of the event transaction.

These are the launch_type values:

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

T Proof

X Spam Score A launch used to check the campaigns spam score.

V Preview

P Triggered Launches via Progra m, form foll ow -up, or the API's

tri gge redCampaignMessage metho d. A launch type of P is

created when the campaign is created. Howeve r, starting wi th

6.12.1, campa igns launched via Prog ram use the R launch ty pe.

U Usage Campaign Usage / Form Usage. The launch recor d is created

when users select Campaign Usage or For m URLs from the

object's context menu. Used primarily for testing purposes.

R Program Trigger ed Prog ram Trig gered Launch. As of 6.12.1, campai gns launched via

Program no lon ger use the Triggere d (P) launch recor d.

This launch type is created when the pro gram is published.

Several Contact Event Typ e data outp ut fi les have a column named SOURCE that identifies the applicatio n or

mo dule that ini tiated ( raised) the specific event. For example, if a recip ient op ts-in via a hosted fo rm, the SOURCE

value is Form f or the OPTIN Contac t Event Type Data recor d.

These are the source ident ificatio n values:

Form FR

Program PR

User Interface UI

UI Data Viewer UV

UI List Upload UU

Exchange Webservice XW Interact API (aka Web Services API)

Exchange Connect XC Interact Connect


12/26


Exchange Salesforce Connecto r XS Salesforce Connecto r integ ration mod ule

Spam Comp laint SC

Reply-To Email RT Email reply sent to a Responsys-hosted reply to add ress, and

pro cessed by the Reply To Handling featu re

Unknown UN

These are the layouts of th e expor t files.

All t imestamps are presented in UTC wi th this format: - -

ACCOUNT_ID NUMBER NO Acc ount number (for example. 1234)

LIST_ID NUMBER Numerical identifier for the List object used by the

Campaign

EVENT_CAPTURED_DT TIMESTAMP(6) NO Date and time the system was inform ed abou t the event

EVENT_STORED_DT TIMESTAMP(6) NO Date the event transaction was stored into the Event DB

CAMPAIGN_ID NUMBER Numerical identi fier of the specific campaign

LAUNCH_ID NUMBER NO Numerical identi fier of the launch instance

EXTERNAL_CAMPAIGN_ID VARCHAR2(255) A string value matchin g the campaign name assigned by

your Web analytics package for the specific campaign

Used to associate system events t o events and data in

your Web analytics package

SF_CAMPAIGN_ID VARCHAR2(255) A string value matching the ID of the associated

Salesforce campaign objec t

Only used with Interact Connect f or Salesforce

integration.

CAMPAIGN_NAME VARCHAR2(255) Name of the Campaign.

LAUNCH_NAME VARCHAR2(255) Campaign name at launch ti me (same as

CAMPAIGN_NAME)

LAUNCH_STATUS CHAR(1) NO The state of t he campaign launch at the time o f the

event row.

SeeLaunch Status Valuesfor more information.

LAUNCH_TYPE CHAR(1) NO The metho d by which the campaign was launched.

SeeLaunch Type Valuesfor more information.

LAUNCH_CHARSET VARCHAR2(255) Language character set for the campaign .

Normally, this value is either ISO-8859-1 or UTF-8, but

depends on the exact campaign configuration.

PURPOSE CHAR(1) Campaign pur pose: Promo ti onal or Transacti onal.


13/26


= promotional

= transactional

SUBJECT VARCHAR2(255) The campaigns subject line.

Can include buil t-in func tions, as this the raw subject l ine

as config ured in the Campaign Dashboard.

DESCRIPTION VARCHAR2(4 0 0 0) Campaign Descriptio n, as entered in the Campaign

Dashboard.

PRODUCT_CATEGORY VARCHAR2(255)

PRODUCT_TYPE VARCHAR2(255)

MARKETING_STRATEGY VARCHAR2(255) Marketing Strategy Category as configured in the

Campaign Dashboard.

Possible values are configure d in the accounts

Administrative Configuration screens available to the

admin user.

MARKETING_PROGRAM VARCHAR2(255) Marketing Program Category as configured in theCampaign Dashboard.

Possible values are config ured in the accounts

Administrative Configuration screens available to the

admin user.

LAUNCH_ERROR_CODE VARCHAR2(255)

LAUNCH_STARTED_DT TIMESTAMP(6)

LAUNCH_COMPLETED_DT TIMESTAMP(6 )

EVENT_TYPE_ID NUMBER NO Numerical value that denotes the event typ e for the

given event transaction

SeeContact Event Type IDsfor more information.



Campaign

RIID NUMBER NO Unique ID assigned for this specific List record

CUSTOMER_ID VARCHAR2(255) A unique identif ier of the recipient/ record that matches

a custo mer ID or unique identi fier in your system of

record.

EVENT_CAPTURED_DT TIMESTAMP(6) NO Date and time the system was inform ed abou t the event .

EVENT_STORED_DT TIMESTAMP(6) NO Date the event transaction was stored into the Event DB.

CAMPAIGN_ID NUMBER NO Numerical identi fier of the specific campaign


EMAIL VARCHAR2(255) NO Email address that initiated the bounce event


14/26


The email address of the response event may di ffer fro m

the email address in the List. This is because recipients

can forwar d messages from one email account to

another before ultimately handling the message.

EMAIL_FORMAT CHAR(1) NO Recipients preferred email content f orma t, HTML or

Text.= HTML

= Text

= No Preferred

= Multi-part

BOUNCE_TYPE CHAR(1) NO Hard or Sof t bounce

= Hard bo unce

= Soft B ounce

REASON VARCHAR2(500) Bounce category value (e.g. USER_NOT_FOUND,

CONNECTION_REFUSED, etc.)

REASON_CODE VARCHAR2(50 0) The bounce message as provi ded by the ISP.

Informational text the ISP

pro vides when bouncing a message. This informa tional

text is important in determining if a block has occurred,

and also includes ways to contac t the ISP regardin g

questions

SUBJECT VARCHAR2(255) The bo unced messages subject line value

CONTACT_INFO VARCHAR2(1000) Addi tional data for you to understand how to best

follo w up wi th com plaints, bounc es, skips and changed

contact data

Possible values depend upon the subject Channel for thegiven event:

Email Channel: Recipients email add ress (from the

List)

Mobile Channel: Recipients mobile numb er (fr om th e

List)

EVENT_TYPE_ID NUMBER NO Numerical value that denotes the event type for the

given event transactionSeeContact Event Type IDsfor more information.



Campaign





15/26


record





EMAIL_FORMAT CHAR(1) NO Recipients preferred email con tent fo rmat, HTML or

Text.

= HTML

= Text

= No Preferred

= Multi-part

OFFER_NAME VARCHAR2(255) NO The name of the link.

The LINK_NAME value from the campaig ns link table

OFFER_NUMBER NUMBER NO Numerical identi fier used for click tracking

OFFER_CATEGORY VARCHAR2(255) The link categ ory value.

The LINK_CATEGORY value from the campaigns link

table

OFFER_URL VARCHAR2(4 0 0 0) NO The URL of the clicked link





Campaign

RIID NUMBER Unique ID assigned for this speci fic List reco rd



record




LAUNCH_ID NUMBER Numerical identi fier of the launch instance

EMAIL_FORMAT CHAR(1) Recipients preferred email content f orma t, HTML or

Text.

= HTML

= Text


16/26


= No Preferred

= Multi-part

REASON VARCHAR2(500 ) Method by which the complaint was captured:

SP:Spam Complaint

SP:Spam Complaint Transfer (Com plaints that were

obtained via the Interact 5.x implementation during

the first 30-6 0 days after switching to Interact 6.x)

EMAIL VARCHAR2(255) Recipients email address that the spam

com plaint. If recipients have forwar ded the message to a

second (o r thir d) email add ress, this is the email address

used to make the complaint.

This may diffe r fro m the email addr ess in the List.

This is because recipients can for ward messages from

one email account to another before ult imately

complaining.

EMAIL_ISP VARCHAR2(255) ISP of the recipients email address (e.g. Yahoo!,Hotmail, etc.)

If the ISP is unkno wn / unca tegorize d, a value of Oth er

is presented.

COMPLAINER_EMAIL VARCHAR2(255) Recip ients email address that the spam

complaint report.

The email address of the spam co mplaint event may

differ from the email addre ss in the List. This is because

recipients can for ward messages from one email account

to another before ult imately complaining.

SPAM_TYPE NUMBER(8,2) Hardcoded to 0, which translates to AUTO_SPAM.


follow-up with complaints, bounces, skips and changed

contact data

Possible values depend upo n the subject Channel for the

given event:

Email Channel: Recipients email addr ess (from the

List)


List)

COMPLAINT_DT TIMESTAMP(6) Date the com plaint was repor ted to the ISP.


17/26


As of Responsys Interact 6.8, the Converted event replaces the Purchase event. It uses the previous Purchase

export schema, with three additional columns: ORDER_ID, ORDER_TOTAL and ORDER_QUANTITY.





Campaign




record





SOURCE CHAR(100 ) Ap plicati on / mod ule that initiates the event

Conversion / Purchase events are initiated / reported by

an external source (y our W eb site), so this value will

always be Unknown.

See Expor ted value is Source Value found in the table

of theSource Identification Valuessection.


Text.

= HTML

= Text

= No Preferred

= Multi-part

OFFER_NAME VARCHAR2(255) NO The name of the link that initiate d the Conversion.

The LINK_NAME value from the campaig ns link table

OFFER_NUMBER NUMBER NO Numerical identi fier used for click tracking

OFFER_CATEGORY VARCHAR2(255) The link categ ory value.

The LINK_CATEGORY value from the campaigns link

table

OFFER_URL VARCHAR2(40 0 0) NO The URL of the clicked link that initiated the

Conversion

ORDER_ID VARCHAR2(255) The order ID value of the specific orde r as passed by you

when registering the Conversion.

The value from the OrderID name-value pair when

calling the Conversion Tracking image pixel


18/26


ORDER_TOTAL NUMBER(18,2) The total amount o f the order as passed by you wh en

registered in the Conversion.

The value from the Orde rTotal name-value pair when


ORDER_QUANTITY NUMBER(18,2) The total numbe r of items in the orde r as passed by you

when registering t he Conversion / Purchase

The value from the NumIte m name-value pair when







Campaign




record



CAMPAIGN_ID NUMBER NO Numerical identi fier of the specific campaignLAUNCH_ID NUMBER NO Numerical identi fier of the launch instance

EMAIL VARCHAR2(255) Email address of the reci pient. The value depends on the

launch conditions:

Live Launch: the Value is the email addr ess from the

List

Proof Launch t o a Proof List: the Value is the email

address from the Proo f List

Proof Launch to specific email address(es) or Proof

Launch personalized against Proof Lis t: Value is the

email address specified d uring the Proof Launch setup

EMAIL_ISP VARCHAR2(255) Domain value of the recipien ts email address (e.g.

yahoo.com)


Text.

= HTML

= Text

= No Preferred

= Multi-part


19/26


OFFER_SIGNATURE_ID NUMBER See SENT

DYNAMIC_CONTENT_SIG

NATURE_ID

NUMBER See SENT

MESSAGE_SIZE NUMBER Message size in by tes

SEGMENT_INFO VARCHAR2(4 0 0 0) See SENTCONTACT_INFO VARCHAR2(1000) Addi tional data for you to understand how to best


contact data.

Possible values depend upon the subject Channel for the

given event:


List)

Mobile Channel: Recipients mo bile number (from the

List)

REASON VARCHAR2(50 0) Reason for the failure to send the message






CampaignRIID NUMBER NO Unique ID assigned for this specific List record



record

EVENT_CAPTURED_DT TIMESTAMP(6) NO Date and time the system was inform ed abou t the event.




EMAIL_FORMAT CHAR(1) NORecipients preferred email content f orma t, HTML or

Text.

= HTML

= Text

= No Preferred

= Multi-part


20/26



given event transaction.




Campaign


The value depends on the launch condi tion:

Live Launch: The RIID is drawn from the distri buti on

List object

Proof Launch personalized against the live

distri buti on List: The RIID is drawn fr om th e

distribution List object

Proof Launch personalized against the Proof List: The

RIID is drawn fr om t he Proof List object



record





EMAIL VARCHAR2(255) NO Recipients email address

The value depends on the launch condi tions:


List

Proof Launch to a Proo f List: the Value is the email



Launch personalized against Proo f List: Value is the


EMAIL_ISP VARCHAR2(255) Domain value of the reci pients email address (e.g.

yahoo.com)


Text.

= HTML

= Text

= No Preferred

= Multi-part

OFFER_SIGNATURE_ID NUMBER Igno re

DYNAMIC_CONTENT_ NUMBER Ignore


21/26


SIGNATURE_ID


SEGMENT_INFO VARCHAR2(4000) If the message was sent wi th mu ltip le segments, this

infor matio n is not usable. It is, however, usable for single

segment sends (PR:Value).



contact data


given event:


List)

Mobile Channel: Recipients mo bile numb e r (from the

List)






Campaign




record





EMAIL VARCHAR2(255) Recipients email address

The value depends on the launch condi tions:


List Proof Launch t o a Proof List: the Value is the email



Launch personalized against Proo f List: Value is the


EMAIL_ISP VARCHAR2(255) Domain value of the recipien ts email address (e.g.

yahoo.com)



22/26


Text.

= HTML

= Text

= No Preferred

= Multi-part

OFFER_SIGNATURE_ID NUMBER N / A

DYNAMIC_CONTENT_SIG

NATURE_ID

NUMBER N/A


SEGMENT_INFO VARCHAR2(4 0 0 0) SeeSent.



contact data


given event:


List)


List)

REASON VARCHAR2(50 0) Reason for skippi ng the message




LIST_ID NUMBER Numerical identi fier for the List object used by the Form




record

EVENT_CAPTURED_DT TIMESTAMP(6) NO Date and time the system was infor med abou t the event



LAUNCH_ID NUMBER Numerical identi fier of the launch instance

FORM_ID NUMBER Numerical identi fier of the Form

FORM_NAME VARCHAR2(255) NO Name of the Form as assigned


23/26





ACCOUNT_ID NUMBER NO Acc ount number (for example. 1234)LIST_ID NUMBER Numerical identi fier for the List objec t used by the Form

EVENT_CAPTURED_DT TIMESTAMP(6) NO Date and time the system was infor med abou t the event


FORM_ID NUMBER Numerical identi fier of the Form

FORM_NAME VARCHAR2(255) NO Name of the Form

FORM_DESCRIPTION VARCHAR2(255) A descripti on of the Form






Campaign


CUSTOMER_ID VARCHAR2(255) A unique identif ier of the recipient /recor d that matches


record






Text.

= HTML

= Text

= No Preferred

= Multi-part


Exporte d value is Source Value f ound in theSource

Identification Valuestable.

REASON VARCHAR2(500) Method used to add the recipient to the List (does not

include bulk loads).


24/26


DV:MERGE (Data Viewer edit / mer ge)

FR:MERGE (Upda te / insert via a Form as a result of a

form submission)

PR:MERGE

WS:MERGE

EMAIL VARCHAR2(255) NO Recipients email address






Campaign




record






Text.

= HTML

= Text

= No Preferred

= Multi-part


Exporte d value is Source Value f ound in the table of

th eSource Identification Valuesfor more information.

REASON VARCHAR2(500) 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


25/26


US: Unsubscr ibe Transfe r

DV: Merge (Data vie wer)

FR: Merge (Progra m)

PR: Merge (Form)

WS: Merge (W ebservices)

EMAIL VARCHAR2(255) NO Email address that initiated the Opt Out event

The email address of the response event may di ffer fro m

the email address in the List; Recipients often f orwa rd

messages from one email address to another where t he

recipient ultimately handles the message


follow-up with complaints, bounces, skips and changed

contact data


given event, pro vide d the RIID value is included in th e

unsubscribe request. Email Channel: Recipients email addr ess (from the

List)


List)

Default: Email address that initiate d the OptOu t

event. (This usually occurs when an unsubscribe

request is made via an email reply.)






Program



a custo mer ID or unique identi fier in your system ofrecord



PROGRAM_ID NUMBER NO Numerical identi fier for the given Progra m

ENACTMENT_ID NUMBER NO Numerical identifier for the recipients specific entry into

the program

PROGRAM_NAME VARCHAR2(255) NO The Progra ms name as set by you


26/26

PROGRAM_VERSION NUMBER The version of the Program used by this event

DESCRIPTION VARCHAR2(1000) The Program s description as set by you






Program


EVENT_STORED_DT TIMESTAMP(6) Date the event transaction was stored into the Event DB

PROGRAM_ID NUMBER NO Numerical identi fier for the given Progra m

PROGRAM_NAME VARCHAR2(255) NO The Programs name as set b y yo u

PROGRAM_DESCRIPTION VARCHAR2(4 0 0 0) The Programs descript ion as set by you

The Responsys File Server suppo rts Secure Copy (SCP) and Secure FTP (SFTP). Access to the file server via these

pro toc ols is perfor med using SSH2 key authentica tion and you r assigned login.

In order to access the Responsys File Server, You must pr ovid e Responsys a public SSH2 key wit h the follo wingattributes:

SSH2 com pliant

RSA or DSA compatible

At least 1024 bi t strong

We reco mmen d the key pair is generated wi thou t a passphrase

Af ter receivin g you r publ ic SSH2 key, we associate the key wi th you r Responsys File Server account.

You maintain p ossession of the p rivate SSH2 key and ensure the priva te key is available to your machine(s) that

will b e remo tely accessing the Responsys File Server to d own load t he Contact Event Data o utp ut files. Responsys

uses the public SSH2 key to authen ticate you when you are tr ying to access the Responsys File Server account

wi th a login we pro vide. If an indivi dual has SSH2 key informa tion tha t does not match the pu blic SSH2 key we

have on record, the ind ivid ual is not g ranted access to the SCP account.

Many SCP and SFTP progra ms are available for several operatin g systems. A popular W indo ws pro gram is

Wi nSCP; MacOS X has scp and sftp built -in; several Linux based operating systems are shipped with scp and /o r

sftp.

You can use one of these tools to create SSH2 key pairs:

Unix/ Linux: com mand line tools such as ssh-keygen

Wind ows: PuttyGen

exporting contact event data guide

Documents