> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/integrations/private-panels-integrations/qualtrics-integration/troubleshooting-the-qualtrics-integration.md). # Troubleshooting the Qualtrics integration If you run into issues when using the Qualtrics integration, refer to the errors below for advice on how to resolve them:

When setting up the integration, I get a Qualtrics token error.

If you see the following error when trying to set up the Qualtrics integration, you likely don't have the correct permissions in Qualtrics: `Qualtrics token must belong to a Brand Administrator.`

Work with the other members of your team to obtain the right level of access in Qualtrics (Brand Administrator). Or, have the team member who is already a Brand Administrator provide the details requested when setting up the integration.

When connecting a screener to my study, I get a generic error.

If you see the following error when trying to connect a screener to your Private Panels study, the issue likely originates on the Qualtrics side: `Qualtrics integration error, please contact support.`

Try again later, or contact Qualtrics Support if you need immediate help.

If the above guidance doesn't help, reach out to your Account Director or the [Dscout Support Team](mailto:support@dscout.com) for assistance. **For more information on the Qualtrics integration, see the following resources:**


Set up the Qualtrics integration	Set up the Qualtrics integration
Connect a Qualtrics screener to a study	Connect a Qualtrics survey to a study
View response data for a Qualtrics screener	View response data for a Qualtrics screener
Configure custom fields in a Qualtrics screener	Configure custom fields in a Qualtrics screener

--- # 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://help.dscout.com/private-panels/integrations/private-panels-integrations/qualtrics-integration/troubleshooting-the-qualtrics-integration.md?ask=&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.