> 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/qualtrics-integration/configure-custom-fields-in-a-qualtrics-screener.md).

# Configure custom fields in a Qualtrics screener

When you use a Qualtrics screener to fill a Private Panels study, basic information is passed back to Qualtrics. This information links each participant's response within Private Panels to their response in Qualtrics. However, you have the option of passing additional data back to Qualtrics using custom fields.

Custom fields map panel properties (data that lives in Private Panels) to embedded data (data that lives in Qualtrics). This lets you get the full picture of your participants regardless of where you're analyzing data.

**To configure custom fields in a Qualtrics screener:**

{% hint style="success" %}
**Tip:** You can also configure custom fields when first connecting a Qualtrics screener to your study. The fields described below are also displayed in the initial screener-creation modal.
{% endhint %}

{% stepper %}
{% step %}
On the **Screeners** tab of your Private Panels study, click the Qualtrics screener you want to edit. The screener's settings are displayed.
{% endstep %}

{% step %}
Under **Custom fields**, click **Edit custom fields**. A modal is displayed.

<div align="left"><figure><img src="/files/NJDpDNLcUCfUQdDAJFTT" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **+ Add custom field**.&#x20;

<div align="left"><figure><img src="/files/7bZ8zjC8Ccnt9JYiw0xc" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
**Note:** You'll automatically see `PrivatePanelsStudyPersonUuid` and `PrivatePanelsPersonUuid` here and in Qualtrics. These are the two pieces of embedded data passed by default. Do not delete these.
{% endhint %}
{% endstep %}

{% step %}
Then, select a panel property from the left-hand drop-down.

<div align="left"><figure><img src="/files/JyHuqGYynTLJNzBe9cJc" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** This is the data that lives within Private Panels that you want to send back to Qualtrics.
{% endhint %}
{% endstep %}

{% step %}
Enter the Qualtrics property key in the **Embedded data** field to the right of your new custom field.

<div align="left"><figure><img src="/files/jUB5HVI6OR98WMKdtwdl" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** This is the Qualtrics property key where you want to store this data. This property key must match exactly what you have in Qualtrics.
{% endhint %}
{% endstep %}

{% step %}
Click **Save**.
{% endstep %}
{% endstepper %}

Now, your custom fields are added and the associated data will be sent back to Qualtrics for each new submission your screener receives. You'll see a list of configured custom fields on the **Screener settings** page:

<figure><img src="/files/39XiNHdGWGkxw4B3d7KH" alt="" width="563"><figcaption></figcaption></figure>

For information on how to display this data in Qualtrics, see the section below.

### Display embedded data in Qualtrics

Once you've configured custom fields, the data is passed back to Qualtrics for each new screener response. However, to see it in Qualtrics, you'll need to add the columns to your specific views.

**To display embedded data in Qualtrics:**

{% stepper %}
{% step %}
In Qualtrics, click **Column chooser**. A drop-down is displayed.
{% endstep %}

{% step %}
Select **Embedded data**. A list of data passed to Qualtrics from Private Panels is displayed. These are the custom fields you configured in Private Panels.
{% endstep %}

{% step %}
Select the custom fields you want to add to your view.

<div align="left"><img src="/spaces/T7fhyut5rrQHwe5QRGot/files/1104290db5415a0ec971ece6e75780ac8c45aa26" alt="" width="563"></div>
{% endstep %}
{% endstepper %}

Now, your selected fields are displayed within Qualtrics:

![](/spaces/T7fhyut5rrQHwe5QRGot/files/d8e2c41fae61d15fb730530f437f6b71738bb856)

**For more information on the Qualtrics integration, see the following resources:**

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Set up the Qualtrics integration</td><td><a href="/pages/4skY09Vval3O9jbMS9TA">/pages/4skY09Vval3O9jbMS9TA</a></td></tr><tr><td>Connect a Qualtrics screener to a study</td><td><a href="/pages/SgS9WxxL5L42kzaCjxwA">/pages/SgS9WxxL5L42kzaCjxwA</a></td></tr><tr><td>View response data for a Qualtrics screener</td><td><a href="/pages/nh6V7xkw2aqk2nj9OIkv">/pages/nh6V7xkw2aqk2nj9OIkv</a></td></tr><tr><td>Troubleshooting the Qualtrics screener</td><td><a href="/pages/zhYGNDRNTLoe1jHgGqqX">/pages/zhYGNDRNTLoe1jHgGqqX</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.dscout.com/private-panels/integrations/qualtrics-integration/configure-custom-fields-in-a-qualtrics-screener.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.