Ketch and Qualtrics

Fulfill deletion requests against enterprise survey data, with the right account tier and the right kind of user generating the connecting credential.

Qualtrics

About Qualtrics

Qualtrics runs survey building, distribution, and response analysis at enterprise scale. Two setup details matter before connecting: this integration only works with Core XM, Design XM, or Customer Experience Management (CXM) accounts, and the API token used to connect specifically needs to be generated by an XM Directory user, not just any account with API access.

Ketch connects to Qualtrics with both requirements accounted for.

Capabilities

How Ketch works with Qualtrics

The Ketch Qualtrics integration covers Rights Orchestration, specifically Right to Delete.

Rights Orchestration

This integration requires a Core XM, Design XM, or CXM account; other Qualtrics account types aren't supported. Connection uses an API Token, which must be generated by an XM Directory user specifically, along with the account's Data Center ID.

With Ketch, teams can

  • Fulfill Right to Delete requests against Qualtrics survey data through the same workflow used for every other connected system
  • Know upfront which account tiers are supported, avoiding a setup attempt on an unsupported plan
  • Connect using a token generated by the correct user type, rather than discovering that requirement as an error

The gap

The problem this integration solves

Qualtrics's own account tiers and user role requirements need to be understood correctly before setup, or a connection attempt fails for reasons that aren't obvious:

01. Attempting to connect an unsupported account type fails, and it's better to know that upfront than after setup begins

02. An API token generated by the wrong type of user won't work for this integration, since it specifically requires an XM Directory user

03. Manually locating and removing a specific person's survey responses doesn't scale to real request volume

Ketch resolves the first two by stating the account and user requirements plainly, and the third by giving Qualtrics a structured, repeatable deletion workflow.

Why Ketch

Why teams choose Ketch for Qualtrics privacy compliance

Permissioning infrastructure that governs Qualtrics the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.

  • Clear about account and user requirements upfront

    The supported account tiers and the XM Directory user requirement for the API token are both stated plainly before setup.

  • One deletion workflow, not a manual process

    Qualtrics requests move through the same Data Subject Rights Automation used for every other connected system.

  • Backed by enforcement precedent

    The California Attorney General reached a $1.55 million settlement with Healthline Media over sharing sensitive data with advertisers without valid consent, a reminder that enterprise survey platforms carry real exposure when deletion isn't handled with real process behind it.

Questions about the Qualtrics integration

Integrations

Pre-built APIs with 1,000+ systems, apps, and models

Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.

Browse All Integrations

See Qualtrics permissioning running end to end

Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Qualtrics yourself.

Get Started Free

Get started in less than 5 min