> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/integrations/metrics-tools/qualtrics.md).

# Qualtrics

Pull survey and experience data from Qualtrics into Smaply journey maps

Connect Qualtrics to surface survey responses and experience scores directly on journey-map stages, like CSAT next to a support touchpoint or NPS at the end of an onboarding journey.

#### Why connect Qualtrics

* Ground experience moments in real customer feedback
* Single API-token auth means no admin approval flow

{% hint style="info" icon="tag" %}
The Qualtrics integration is available on the **Governance** plan.
{% endhint %}

#### In this section

* [**Set up Qualtrics**](https://helpdesk.smaply.app/integrations/metrics-tools/qualtrics/how-to-set-up-the-qualtrics-integration.md) - Connect at the account level using your Qualtrics API token and base URL.
* [**Use Qualtrics in a metric**](https://helpdesk.smaply.app/integrations/metrics-tools/qualtrics/how-to-use-qualtrics-in-a-metric.md) - Add survey data to journey-map metric cards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdesk.smaply.app/integrations/metrics-tools/qualtrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
