Add Contacts and Transactions to XMD Task

About the Add Contacts and Transactions to XMD Task

The Add Contacts and Transactions to XMD task allows you to map data imported into Qualtrics to your XM Directory. For example, you can use an Extract data from SFTP files task to import data into Qualtrics and then map that data to your directory.

This task is similar to the Load B2B account data into XM Directory task, but it allows you to map both contact data and transactional data to XM Directory.

Setting Up an Add Contacts and Transactions to XMD Task

1. Create an ETL workflow.
2. Select Data source (ETL extractor). In this step, you’ll extract data that you can load to another destination. See using Building ETL Workflows for more information.
   
   Qtip: Files must be less than 50 MB to be compatible with the add contacts and transactions to XMD task.
3. Click Add a data destination.
   
4. Choose the Add contacts and transactions to XMD task.
   
5. Choose the directory to map data to.
   
   Qtip: Most licenses only have a default directory, but some may have multiple directories.
6. Select a mailing list to map data to. You can also choose to create a new mailing list for this directory each time this workflow runs.
7. Select a data source. This should be the data extractor task you set up earlier.
8. Use the menus to map fields from your data extracting task to your XM Directory.
   
   Qtip: You can also map individual field values. See Mapping Field Values for more information.
9. To add custom fields to your mapping, click Add Field.
   Qtip: Source fields can only be mapped to one destination field within the task.
10. If you want to map transactional data in addition to contact data, select a field to use as the transaction date.
    
    Attention: When mapping transactional data you must map at least one contact field in the section above. You also must select a contact list that your transaction data will be added to.

    Qtip: When mapping transaction date fields during the set-up of your task, transaction dates are the dates a transaction occurred. Dates will be assumed to be in UTC unless the time zone is explicitly included in the date value. More information on these formats can be found on the Date Format Syntax support page. Here is a list of compatible time formats:

    • ISO-8601 (2006-01-02T15:04:05+07:00)
    • ANSIC (Mon Jan _2 15:04:05 2006)
    • UnixDate (Mon Jan _2 15:04:05 MST 2006)
    • RFC822 (02 Jan 06 15:04 MST)
    • RFC850 (Monday, 02-Jan-06 15:04:05 MST)
    • RFC1123 (Mon, 02 Jan 2006 15:04:05 MST)
11. Click Add Field to add more custom transaction fields, and use the dropdown menus to map values for these fields.
    Qtip: Transaction date field is required, and you will not be able to map additional transaction fields without mapping a value for this field.
12. When finished mapping fields, click Save.
    Qtip: This task obeys your directory’s contact deduplication rules.

Mapping Field Values

You can map individual field values to save into Qualtrics. You have the option of mapping fields manually, or uploading a file containing your mappings. Additionally, you can determine what happens to unmapped fields.

To start mapping field values, click Replace all values on the left with the values on the right under the desired field.

MAPPING VALUES WITH A FILE UPLOAD

You have the option of uploading a CSV or TSV file containing your mapping. This is recommended if you have many values to map. If you have already mapped some values, uploading a file will not replace those mappings. Your newly added mappings will be added beneath the already mapped values.

1. Click Replace all values on the left with the values on the right.
   
2. Click Download CSV Template. We recommend downloading the template since it contains the correct formatting.
3. Open this file in a spreadsheet editor on your computer, like Microsoft Excel or Google Sheets.
4. The first 2 cells will contain the headers “from” and “to.” These represent your source and destination values, respectively.
   
5. Add your field values. Your source values go in the “from” column and the destination values go in the “to” column. Make sure your file meets the following requirements:
   • You may have up to 500 mapping pairs. If your file contains more than 500 mappings, then you will receive an error message and only the first 500 rows will be uploaded.
   • Make sure your file contains the “from” and “to” headers. If these headers are not detected, then Qualtrics will assume the first column is “from” and the second column is “to.
6. Save your file as a CSV or TSV with UTF-8 encoding.
7. In the Add contacts and transactions to XMD task, click Choose file and then select the file from your computer. Your uploaded mapping will then populate in the task.
   

MANUALLY MAPPING VALUES

You can also map field values manually. This is recommended if you only have a few values to map.

1. Click Replace all values on the left with the values on the right.
   
2. Enter the source value in the first column
3. Enter the destination value in the second column
4. Click the blue plus sign ( + ) to add another mapping pair.

HANDLING UNMAPPED FIELDS

If a field value is not mapped, the field will be imported into Qualtrics using its source value. However, you can choose to map all unmapped values to a default field value.

1. Click Replace all values on the left with the values on the right.
   
2. Enable Map unmapped fields to a default field.
3. Enter the default field value.

DELETING MAPPINGS

1. Click the minus sign ( – ) next to a mapping pair to delete the mapping.
   
2. Click Clear all to delete all mappings for that field.

Troubleshooting Tips

• When investigating what went wrong with a workflow task, check out Workflows reporting for any errors and correct them before retrying your task.
• Contact deduplication allows you to retry your task without creating duplicate contacts. Make sure to set up contact deduplication rules when testing and retrying this task.

FAQs