About exporting Contact Event Data
The Export Contact Event Data feature lets you extract behavioral and other raw data about events from account-wide and campaign-specific response activities. For example, logs can tell you – on a row-by-row 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 external programs
-
Analyzing campaigns using your analytics or other software
Information is exported to flat text files that are available on the Oracle Responsys file server associated with your account (for example, files.responsys.net or files.dc2.responsys.net) for 14 days. You can have the export data files packaged in individual ZIP archives and can also specify GPG/PGP encryption.
After you run an export for the first time, each subsequent report contains an incremental update of events that occurred since the last successful export. You use the Launch_State values to create a lookup table of events so that you can match more recent events to an existing launch record. This is particularly important for triggered events where the launch date and send date are not necessarily the same.
NOTE: Post-19A, if you change a campaign’s name, folder, marketing program, marketing strategy, subject line, or external campaign ID, then historical and new launches for both triggered and standard launches will take these new values in Insight. This update applies to all channels. It does not impact the CED behavior as CED retains an unchanged ‘snapshot’ of values.
Next steps
Configuring a Contact Event Data export job