Email

Exports delivered via email are embedded in the body of the email message unless Send exported data as attachment is on.

Email to address

Address(es) to receive the email, separated by comma.

Email from address

Address that appears in the From field. This value is auto-generated and shown as a read-only field with this format:

mec-export-[companyUrlName]@[broadcasterDomain]

Email from name

Name that appears in the From field. This value is auto-generated and shown as a read-only field with this format:

MEC Export for [companyName]

Email subject

Subject field description. For example, Medallia $COMPANY_NAME$ Survey IDs.

You can use the Filename variables in the Email options. For example, the subject might include a date/time, like this: Opt-Out list as of $DATETIME$.

File transfer protocol

Automatically delivers the exported file to an external system using one of these file transfer protocols:

• FTP — Standard FTP.
• SFTP w/ password — Secure FTP using a password for authentication; encrypts both commands and data.
  Important: Password authentication is deprecated and will be obsolete in a future release. Preferentially, use public key authentication for new connections with Medallia-owned servers or client-owned servers. For information about public key authentication, see Generating SSH Key pairs.
• SFTP w/ public Key — SFTP using a certificate for authentication.
• FTPS Explicit — Secure FTP using a root certificate from a certificate authority.

For FTP delivery, define these protocol properties:

For a discussion of how SFTP uses keys and passphrases, see SSH key pairs.

Control files

To avoid trying to access the downloaded file before the file transfer is complete, some systems look for a control file to indicate the transfer is complete. A control file is a small, typically empty, text file that Experience Cloud writes on the target system after it finishes sending the main data file.

Typically, the filename of the control file is similar to that of the data file so they can be programmatically associated by the client IT system. In some situations, the filename itself is the same but the directory is different. Here are some examples:

These variables can be used to create the control file's filename:

• $COMPANY_NAME$ — From the Company settings screen.

• $COMPANY_URL$ — From the Company settings screen.

• $EXPORT_FILENAME$ — The entire filename of the data file.

• $EXPORT_FILENAME_PREFIX$ — The portion of the export's filename that is NOT automatically appended by Medallia Experience Cloud.

• $EXPORT_FILENAME_SUFFIX$ — The portion of the export's filename that IS automatically appended by Medallia Experience Cloud.

While most control files are empty, some IT systems require them to contain some metadata about the export itself. These variables can be used to create in the control file's content:

• $BYTES_WRITTEN$ -— The count of bytes written to the export file.

• $COMPANY_NAME$ — From the Company settings screen.

• $COMPANY_URL$ — From the Company settings screen.

• $EXPORT_FILENAME$ — The entire filename of the data file.

• $EXPORT_DURATION_MSEC$ — The count of milliseconds spent creating the export file.

• $EXPORT_NAME$ —  The name of the export specification in Experience Cloud.

• $NUM_ROWS$ —  The count of records (not including any header row, if the file format supports such a row) in the export file.

• $MD5$, $SHA1$, $SHA256$, $SHA384$, & $SHA512$ — The cryptographic hash of the export file's contents.

Amazon S3

Delivers files to a secure Amazon S3 bucket; requires an AWS access account.

The export includes an additional verification header (an MD5 hash) that allows exports to WORM (Write-Once Read-Many) Amazon S3 buckets.

While Medallia only requires that you provide the access key and the secret key to deliver the files, we recommend that you implement the following Amazon IAM policy on your S3 bucket to enable minimum access for Experience Cloud to act as an S3 client:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Objects",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:GetObject",
                "s3:DeleteObject"
            ],
            "Resource": "...(to be filled in)..."
        },
        {
            "Sid": "Bucket",
            "Effect": "Allow",
            "Action": "s3:ListBucket",
            "Resource": "...(to be filled in)..."
        }
    ]
}

Google Cloud Storage

Delivers files to an existing, secure Google Cloud Storage (GCS) bucket; requires a service account type of GCS OAuth2 credentials. With each file upload, the MD5 hash in Base64 format is calculated and included in the delivery.

Export to Auto Importer

The data are in a feed file delivered directly to the Auto Importer for reprocessing. Some typical applications include:

• To junk records (e_status = 7): hide them and remove them from all reports.
• To mask sensitive data from the record after the processing invitations or survey responses. For example, the email address and last name fields might be replaced with a string of asterisks, like *****.

In each of the scenarios above, the Exporter identifies records to reprocess, and an Auto Importer specification makes the specific changes to the same records.

Auto importer options:

Auto importer processor

The specification that will receive and reprocess the records.

Processing mode

How the auto importer should process the records.

• Pretend — Runs the data through the processor without committing the changes to the database. You can see how the records would be process with the Import Processing Reports.

• Active — Update the records in the database.

To create the export/import process:

1. Create a new Export specification.
   1. Assign a Name.
   2. For Export Via, choose Manual (or Email). For now you need to generate the export file. Later you will change this to deliver to the Auto Importer.
   3. Click Save.
2. Define at least these properties:
   • Filename — Include $DATETIME$ in the file to make it easier to identify specific update jobs in the Import Processing Reports.
   • Success and Failure email report addresses — (Optional) To receive a summary reports of the jobs. Note that successful jobs send two emails: success notification and feed file summary report.
   • Fields to export — Include just the fields necessary to identify the records to update; for survey records just include a_surveyid.
   • Schedule options — (Optional) You might want to define the schedule later, after testing the updates in pretend mode.
   • Filtering options — Specify the filtering conditions, possibly with Episode filters, to identify the records to extract and update. Tip: For now, create a small set of records for testing.
3. Click Save.
4. Click Download to create a CSV (Excel 2007) file to use for creating the Auto Importer specification.
   Warning: As of the Fall 2023.3 release, files exported as CSV, pipe, and tab delimited formats start with a tab character for field values beginning with =, +, -, or @. For example, -100 changes to \t-100 (ASCII 9 for tab). This mitigates a security risk that could allow code malicious injection into spreadsheet programs. Applications processing CSV files must comply with RFC-4180 and should trim whitespace from field values before use — that is, remove surrounding whitespace (tab, newline, or space characters) before using the value. For more information, see CWE-1236.
5. Create an Auto Importer specification to reprocess the records. See Auto Importer Processors for more information.

   • Use the downloaded CSV file to define the input columns in the specification.
   • Select Duplicate checking.
   • Consider defining a Deletion schedule for the company in Company settings or importer to delete the feed files after some number of days.
   • Here is a simple example of an import specification that appends " massupdated" to the customer's last name.

     <import-spec inputType="CSV" columnsCheck="ALLOW_EXTRA_COLUMNS" name="Simple survey import">
     	<input-column heading="surveyid" />
     	<output-column-group pluginName="Survey" recordUpdateMode="UPDATE" multiUpdateMode="UPDATE_ALL">
     		<output-column>
     			<input-column heading="surveyid" />
     			<target-field fieldId="surveyid" fieldName="Survey ID" requiredness="REQUIRED_USED_FOR_DUPLICATE_CHECK" type="INTEGER" />
     		</output-column>
     		<output-column>
     			<target-field fieldId="e_lastname" fieldName="Last name" requiredness="REQUIRED" type="STRING">
     				<javascript-transform><![CDATA[
     					return original['e_lastname'] + " massupdated";
     				]]></javascript-transform>
     			</target-field>
     		</output-column>
     	</output-column-group>
     </import-spec>

6. Modify the new Export specification.
   • Export Via — Choose Export to Auto Importer.
   • Auto importer processor — The specification that will receive and reprocess the records.
   • Processing mode — Choose Pretend until you are ready to begin actually updating the records. Pretend-mode runs the data through the processor without committing the changes to the database. You can see how the records would be process with the Import Processing Reports. Later, set this to Active to perform the actual updates.
7. Click Export survey data now to test the process.
   1. Review the update activity on the Feed Files screen.
   2. Make any necessary changes to the export and import specifications.
   3. Repeat until the results have been verified as desirable.
8. After verifying the process, change these properties
   • Processing mode — Choose Active to perform the actual updates.
   • Schedule options — Define the schedule.
9. Click Save.

The exporter and importer will now update records per the schedule.

Manual and Responses, Invitations, and AskNow filter downloads

Exports the records currently shown on the Filter tab of the Responses, Invitations report, or AskNow standard report when the user chooses the Download option on the report screen.

The Responses / Invitations filter options configure the export when using manual or filter downloads.

Responses max records

Maximum count of records to include in the export. The default value is 2,000. Additionally, depending on the export format, the maximum count allowed is:

• Excel 2007 — 100K records.

• SPSS — 350k records.

• All others — 140k records.

Available for roles <Add Roles>

Assigns one or more user roles to Responses Filter or Invitation Management exports. It is only possible to have one export from the responses tab for a given role. If one export is configured for all users and another is for corporate administrators, the administrators will get the more role-specific configuration.

To see the Export option, the Role needs these Capabilities:

• Web Data Exports to access the dropdown.
• RI Data Exports to export from Responses reports filter.
• IM Data Exports to export from Invitation Ranker reports filter.

Available export formats

One or more export formats to be available to the report user. The user then chooses the format to download.