Transactions
About Transactions
Transactions allow you to record interaction data about events associated with your contacts by representing a specific interaction at a specific moment in time. Transaction data serves as a rich data source to understand how customers interact with your brand and offers deep insights into past behaviors. Once you have transaction data in Qualtrics, you can distribute surveys that are customized based on this transaction data, create segments, and target workflows based on transaction data.
Transactional data is similar to embedded data, however, it allows you to record multiple values for the same field without overwriting historical values. You can manually upload transactional data, or save survey response data as a transaction for your contacts using an XM Directory task.
Transactions are a feature exclusive to XM Directory.
Preparing a Transaction File for Import
To save transaction data in Qualtrics, you can import a file containing your data. This section covers how to format your file so it imports correctly into Qualtrics. When saving your file, make sure you’ve saved it with UTF-8 encoding.
Template File
Qualtrics provides a template file with the correct formatting. We recommend you use this file to get started with importing transactions. To find the template file, click Download a sample template while creating your transactions.
After downloading the file, open it in a spreadsheet editor such as Excel and make any necessary changes. The following sections cover required and recommended fields.
Required Fields
In your file, you must have the following fields:
- Transaction Date: The datetime of the transaction. Transaction dates must be in ISO-8601 format (e.g. YYYY-MM-DDTHH:mm:ss+ZZZZ ; more information about these symbols can be found on the Date Format Syntax support page).
Example: Let’s say our transaction date is March 31, 2021 at 9:00:00AM EDT (UTC-4). This date in ISO-8601 format is 2021-03-21T13:00:00.000Z. Note how the time has been converted from EDT to UTC.
- At least one contact field. This can be:
- First name: The contact’s first name
- Last name: The contact’s last name
- Email: The contact’s email address.
- External data reference: A reference ID number for the contact.
You will not be able to import transactions if you are missing the above fields.
Recommended Fields
In addition to the above required fields, we recommend you include the following fields to ensure an organized and high-quality directory:
- First name: The contact’s first name.
- Last name: The contact’s last name.
- Email: The contact’s email address.
- Phone: The contact’s phone number.
- External data reference: A reference ID number for the contact.
In addition to the above recommended fields, you can include embedded data in your transaction uploads.
Creating a Transaction Group
A transaction group is simply a collection of transactions. You can import a file with your transaction data to save in Qualtrics.
- In your directory, go to the Transactions tab.
- Click Create a group of transactions.
- Give your transaction group a name.
- If desired, add a description to your transaction group. This field is for your organization purposes.
- Select the mailing list to associate the transactions with.
- Click Next.
- Click Select a file and choose the file you prepared earlier.
- Choose the Delimiter for your file, or the character that separates data values. Your options include comma, tab, and semicolon.
- Choose the Enclosure for your file, or the character that encloses your data. Your options include single quote and double quote.
- Click Next.
- Map your imported fields to Qualtrics fields using the dropdown menu. You can map fields to the following XM directory fields:
- Embedded data: Saves the field as an embedded data field with the contact. If the field does not exist, it will be created. If the field does exist, its value will be updated.
-
Qtip: If your contact file has a field used as embedded data and transactional, one being upper case and one being lower case, both fields will pull into the survey data and display their respected values. If the transactional field has a value for the contact, and the embedded data field is missing a value, in the survey data, the embedded data field will display the value the contact has for transactional.
-
- Transaction information: Saves the field as transactional data with the contact. A new transaction record will be created for your contact with this transaction information and the associated transaction date.
- Transaction date: The datetime of the transaction. Transaction dates must be in ISO-8601 format (e.g. YYYY-MM-DDTHH:mm:ss+ZZZZ ; more information about these symbols can be found on the Date Format Syntax support page). This field is required.
Example: Let’s say our transaction date is March 31, 2021 at 9:00AM EDT (UTC-4). This date in ISO-8601 format is 2021-03-21T09:00:00-0400.
- Email: The email address associated with the contact
- First name: The contact’s first name.
- Last name: The contact’s last name.
- Phone: The contact’s phone number.
- Language: The contact’s preferred language.
- External data reference: A reference ID number.
- Unsubscribe: Used to update the contact’s opt-out status in the associated mailing list. A value of “Yes” will unsubscribe (i.e. opt-out) the contact, while a value of “No” will keep the contact subscribed to mailings (i.e. opted-in).
- Exclude from import: Excludes the field from being imported. Use this option for any unneeded fields in your file.
Qtip: In addition to the required transaction date field, you must map at least one contact field. This includes first name, last name, email, and external data reference.
- Embedded data: Saves the field as an embedded data field with the contact. If the field does not exist, it will be created. If the field does exist, its value will be updated.
- Click Upload the file.
- Click Add your contacts.
Managing Transaction Groups
You can search your transaction groups by transaction group name at the top of the Transactions page. You can sort the table of transaction groups by name and creation date by clicking the field name in the transactions table.
To view the transactions within a transaction group, click the group name.
You can then use the Transaction group options dropdown to perform the following actions:
- Edit this transaction group: Allows you to change the transaction group’s name and / or description.
- Delete this transaction group: Deletes the transaction group. Note that the transactions will still exist for each contact.
Viewing a Single Transaction
After opening your transaction group, you can view more information about a single transaction by clicking the transaction. A window on the right hand side of the page will open with more information.
The Profile tab contains more information about the contact associated with the transaction. You can view all contact data and attributes in this window, and search for a specific field by using the search bar at the top of the window.
The Timeline tab contains a touchpoint timeline for the contact. Click on an interaction to expand it and see all associated transaction data. The transaction data associated with this specific transaction group will be listed under the “related” section, and any historical transactions for the contact will be listed below.
If needed, you can delete a single transaction from your transaction group. To delete a transaction, click the three dots next to the transaction and then Remove this transaction information.
Distributing to Transactions
You can send surveys and emails to your transactions from the Distributions section of XM Directory.
When creating your distribution, choose All Transaction Groups and then select the transaction group you want to distribute to.
Please see the Send Emails in XM Directory support page for step-by-step instructions on creating distributions in XM Directory.
Using the Qualtrics Transactions API
In addition to importing transactions right inside Qualtrics, you can also create and manage transactions through the Qualtrics API. Check out the following API documents for more information:
- Using Transactions in XM Directory
- Create Contact Transactions
- Get Contact Transaction
- List Contact Transactions
- Append Contact Transaction
- Update Contact Transaction
- Delete Contract Transaction