Qualtrics Integration


Authenticx integrates with Qualtrics XM to surface post-interaction survey feedback directly alongside conversation intelligence. Once connected, survey responses are automatically matched to Authenticx conversations and the results (satisfaction scores, open-ended feedback, and embedded data fields) become searchable and reportable in the platform.


How It Works

Authenticx periodically exports responses from a configured Qualtrics survey using the Qualtrics REST API. Each response is matched to a conversation in Authenticx using a call identifier that your survey captures as an embedded data field or question answer. When a match is found, the survey fields are written to the conversation record as enrichment metadata.

The integration is read-only. Authenticx pulls data from Qualtrics and never writes back to your Qualtrics account.


Prerequisites

Before your Authenticx implementation team can activate this integration, the following must be in place on your Qualtrics account:

RequirementDetails
Qualtrics LicenseAPI access must be included in your Qualtrics license. Contact your Qualtrics Account Executive if you are unsure.
Brand Administrator accessA Brand Administrator in your Qualtrics account is required to enable API permissions and create the service user.
Survey with call ID passthroughThe target survey must capture a call or interaction identifier on each response. See Step 4 for details.

Step 1: Enable the Access API Permission

The Qualtrics user whose token Authenticx will use must have the Access API permission enabled. This is configured by a Brand Administrator.

  1. Log in to Qualtrics as a Brand Administrator.
  2. Navigate to Admin in the top navigation.
  3. Select the Users tab.
  4. Locate the user that will own the API token (see the note below about service users), then click the user's name to open their settings.
  5. Under User Permissions, enable Access API.
  6. Save the changes.

Recommendation: Create a dedicated service user (e.g., [email protected]) rather than using a named employee's account. This prevents the integration from breaking if the employee leaves or their credentials change.


Step 2: Generate an API Token

Each Qualtrics user has a unique API token. The token is tied to the account and authenticates all API requests Authenticx makes on its behalf.

  1. Log in to Qualtrics as the service user created in Step 1.
  2. Click the user icon in the top-right corner and select Account Settings.
  3. Click Switch to older version if prompted (the Qualtrics IDs section is in the legacy Account Settings view).
  4. Select Qualtrics IDs in the left navigation.
  5. In the API section, click Generate Token.

Warning: Only click Generate Token once. If a token already exists, do not regenerate it — doing so immediately invalidates the existing token and will break any integrations already using it. If you need to rotate the token, coordinate with your Authenticx implementation team first.

  1. Copy the token value and store it in a secure location. Provide this token to your Authenticx implementation team. Authenticx encrypts and stores it in an isolated vault scoped to your organization.

Step 3: Locate Your Survey ID and Datacenter URL

Authenticx needs two additional values to connect to the correct survey and route API calls to the right Qualtrics datacenter.

Survey ID

  1. Log in to Qualtrics and open the target survey.
  2. In the browser address bar, the Survey ID appears in the URL. It begins with SV_ followed by alphanumeric characters (e.g., SV_0abcDEFghiJKL).
  3. Alternatively, go to Account Settings → Qualtrics IDs and find the survey in the Survey IDs section.

Datacenter / Base URL

Your Qualtrics datacenter determines the base URL for all API calls. The format is:

https://{your-organization-id}.qualtrics.com

To find it:

  1. Go to Account Settings → Qualtrics IDs.
  2. Look for your Datacenter ID (e.g., iad1, ca1, fra1). This is the subdomain prefix Qualtrics uses for your account's API hostname.
  3. Your base URL will follow the pattern https://{datacenter-id}.qualtrics.com — for example, https://iad1.qualtrics.com.

Authenticx uses this URL as the base for all API requests. If the wrong URL is configured, the Qualtrics API returns a GRP_1 error that includes the correct host in the error message. Your implementation team can correct this without requiring any changes on your end.


Step 4: Configure Call ID Passthrough in Your Survey

For Authenticx to match a survey response to a conversation, the survey must capture a consistent call or interaction identifier on each response. This is the same identifier that exists on the Authenticx conversation record (typically a Client Call ID).

The recommended approach is to pass the call ID as Embedded Data when distributing the survey (e.g., via a survey link that includes the call ID as a URL parameter). The embedded data field name your Qualtrics implementation uses must be provided to your Authenticx implementation team for field mapping configuration.

ApproachHow It Works
Embedded Data (recommended)Include the call ID in the survey distribution link as a URL parameter (e.g., ?CALL_ID=abc123). Define the corresponding Embedded Data field in your Survey Flow. The field appears in every export response under that field name.
Hidden survey questionA question in the survey is pre-filled with the call ID via URL parameter and marked as hidden from the respondent. The question's Import ID is used as the source field name in the Authenticx metadata configuration.

Provide your Authenticx implementation team with the exact field name or Import ID used to capture the call identifier so it can be mapped correctly.


Step 5: Provide Credentials to Authenticx

Collect the following and share them securely with your Authenticx implementation team:

ValueDescriptionExample
API TokenThe token generated in Step 2.abc1XyZ...
Survey IDThe ID of the Qualtrics survey to pull responses from.SV_0abcDEFghiJKL
Base URLYour Qualtrics datacenter base URL from Step 3.https://iad1.qualtrics.com
Call ID Field NameThe Embedded Data field name or question Import ID that holds the call identifier.CALL_ID

Authenticx will use these to configure the integration and set up the field mapping.


Network Requirements

RequirementDetails
Outbound access from QualtricsNo outbound access from Qualtrics is required. Authenticx initiates all API calls to Qualtrics.
IP AllowlistingIf your Qualtrics account is configured to restrict API access by IP address, contact your Authenticx implementation team for the outbound IP ranges to allowlist.

What Authenticx Configures

Your Authenticx implementation team handles the following configuration on your behalf:

SettingDescription
Survey IDThe Qualtrics survey to pull responses from.
Base Integration URIYour Qualtrics datacenter URL.
API TokenStored encrypted in an isolated vault scoped to your organization.
Look-back windowHow many days of responses to evaluate on each run (default: 7 days).
Execution lagBuffer applied to the run end time to allow Qualtrics responses to fully record before export (default: 60 minutes).
Response completion delayOptional: treat responses as complete after a set number of days regardless of Qualtrics Finished status. Useful when surveys are left open for extended periods.
Field mappingMaps your Qualtrics response fields and embedded data to Authenticx conversation metadata fields.
Association fieldsDefines how Authenticx matches a survey response to a conversation (typically by ClientCallId).

Testing & Validation

RequirementDetails
Sample responsesProvide 3–5 known survey responses (by Qualtrics Response ID or recorded date) along with the call IDs they should match in Authenticx. These are used to verify the end-to-end match and enrichment flow.
Technical contactA Qualtrics administrator on your team should be available during onboarding to assist with embedded data configuration, field naming, and troubleshooting.
Staging environmentIf your organization uses a Qualtrics sandbox or test survey, your Authenticx implementation team can validate the integration against it before pointing to production.

Did this page help you?