# Home

<h2 align="center">Get help with Dscout</h2>

<p align="center">Recruit participants, run research, and analyze results with Dscout.</p>

<p align="center"><button type="button" class="button primary" data-action="search" data-icon="magnifying-glass">Search...</button></p>

<h4 align="center">Explore by study type</h4>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>Prototype and concept feedback</td><td><a href="/usability-tests/what-are-usability-tests-in-dscout">Usability tests</a></td><td><a href="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2F913czSQ2ux3pTjX8AZJR%2F01-pointer-in-browser.png?alt=media&amp;token=9829e5e9-7ab2-4702-9017-e5a206d01af1">01-pointer-in-browser.png</a></td></tr><tr><td><strong>Media surveys</strong></td><td>Media-rich questions and insights</td><td><a href="/media-surveys/what-are-media-surveys-in-dscout">Media surveys</a></td><td><a href="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2F1zHHHObZbpTZeIThi9JV%2F02-message-camera-video.png?alt=media&amp;token=f698b879-bd23-4744-bbf7-c97ba5d26755">02-message-camera-video.png</a></td></tr><tr><td><strong>Intercept studies</strong></td><td>In-the-moment insights</td><td><a href="/intercept-studies/what-are-intercept-studies-in-dscout">Intercept studies</a></td><td><a href="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2F8yC6vL9dxSd5Om9cuvUd%2F03-intercept.png?alt=media&amp;token=7d8c83f8-661a-4d13-ab21-8654410a3772">03-intercept.png</a></td></tr><tr><td><strong>Diary studies</strong></td><td>Experiences over time</td><td><a href="/diary-studies/what-are-diary-studies-in-dscout">Diary studies</a></td><td><a href="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FXeIJZdEknsrUYjYsxKfJ%2F04-diary.png?alt=media&amp;token=4c739d34-1987-4cd6-9ea2-0c53a5542c55">04-diary.png</a></td></tr><tr><td><strong>Interview studies</strong></td><td>Moderated sessions</td><td><a href="/interview-studies/what-are-interview-studies-in-dscout">Interview studies</a></td><td><a href="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2Fc4IE0hLWAOWGvxGKaehU%2F05-person-in-corner-brackets.png?alt=media&amp;token=129695bb-f5e9-411a-b375-867c8341ab55">05-person-in-corner-brackets.png</a></td></tr></tbody></table>

<p align="center"><a href="#explore-all-documentation">↓ View all categories</a></p>

***

{% columns %}
{% column %}

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FaFy9QoEbFzIcNrookrU1%2FDscout%20MCP.jpg?alt=media&amp;token=e6948321-236c-4f4b-88de-f803b26591e4" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

### <i class="fa-mcp">:mcp:</i> Dscout MCP

Build, launch, and analyze studies directly in your AI workflow. [Learn more](/dscout-ai/dscout-mcp) or select your tool below:

<a href="https://claude.ai/directory/dscout-researcher?q=dscout" class="button primary" data-icon="claude">Connect to Claude</a>

<a href="/dscout-ai/dscout-mcp/set-up-the-dscout-mcp" class="button primary" data-icon="sparkles">Connect to other tools</a>
{% endcolumn %}
{% endcolumns %}

<h4 align="center">Explore all documentation</h4>

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting started</strong></td><td><a href="/getting-started/dscout-quickstart-guide">Getting started</a></td></tr><tr><td><strong>Study basics</strong></td><td><a href="/study-basics/question-types">Study basics</a></td></tr><tr><td><strong>Recruit participants</strong></td><td><a href="/recruit-participants/what-are-dscout-screeners">Recruit participants</a></td></tr><tr><td><strong>Usability tests</strong></td><td><a href="/usability-tests/what-are-usability-tests-in-dscout">Usability tests</a></td></tr><tr><td><strong>Media surveys</strong></td><td><a href="/media-surveys/what-are-media-surveys-in-dscout">Media surveys</a></td></tr><tr><td><strong>Intercept studies</strong></td><td><a href="/intercept-studies/what-are-intercept-studies-in-dscout">Intercept studies</a></td></tr><tr><td><strong>Diary studies</strong></td><td><a href="/diary-studies/what-are-diary-studies-in-dscout">Diary studies</a></td></tr><tr><td><strong>Interview studies</strong></td><td><a href="/interview-studies/what-are-interview-studies-in-dscout">Interview studies</a></td></tr><tr><td><strong>Dscout AI</strong></td><td><a href="/dscout-ai/what-is-dscout-ai">Dscout AI</a></td></tr><tr><td><strong>Integrations</strong></td><td><a href="/integrations/export-dscout-data-to-heymarvin">Integrations</a></td></tr><tr><td><strong>Account management</strong></td><td><a href="/account-management/organization-account-settings">Account management</a></td></tr><tr><td><strong>Privacy and feedback</strong></td><td></td></tr></tbody></table>

<h4 align="center">Can't find what you're looking for?</h4>

<p align="center"><a href="mailto:support@dscout.com" class="button primary">Contact support</a></p>


# Dscout quickstart guide

Looking to uncover insights to help you build better products? You’re in the right place! With our various research tools—both moderated and unmoderated—Dscout makes it easy to gather rich, human-centered data at scale.

But where to start? We’ve put together this guide to help you make some important first decisions to kick off your research.

{% hint style="success" %}
For the best experience, use **Google Chrome** or **Microsoft Edge** when working with Dscout. Other browsers may cause inconsistent performance or limit access to certain features.
{% endhint %}

### Choose a study type

At Dscout, you have five study types to choose from:

* **Usability test**: Quickly capture how users interact with your website, prototype, or app to uncover pain points and improve UX. For more information, see [What are usability tests in Dscout?](/usability-tests/what-are-usability-tests-in-dscout)
* **Media survey**: Collect in-the-moment feedback through video, photos, and open-ended responses to bring your research to life. For more information, see [What are media surveys in Dscout?](/media-surveys/what-are-media-surveys-in-dscout)
* **Intercept studies:** Catch participants in the moment as they make important decisions while browsing the web. For more information, see [What are intercept studies in Dscout?](/intercept-studies/what-are-intercept-studies-in-dscout)
* **Diary**: Understand behaviors and experiences over time with longitudinal studies that capture real moments as they happen. For more information, see [Set up a Diary study](/diary-studies/what-are-diary-studies-in-dscout/set-up-a-diary-study).
* **Interview**: Conduct one-on-one video sessions with participants to dig deeper, ask follow-ups, and explore reactions in real time. For more information, see [Set up an interview study](/interview-studies/create-an-interview-study).

Still not sure which study type makes sense for your research? Use the tables below for a more detailed breakdown:

#### Unmoderated studies

|                                                                                       | Usability tests                                 | Media surveys                                   | Intercept studies          | Diary studies                                    |
| ------------------------------------------------------------------------------------- | ----------------------------------------------- | ----------------------------------------------- | -------------------------- | ------------------------------------------------ |
| **Continuously recorded**                                                             | ✅ (privacy blur available)                      |                                                 | ✅ (privacy blur available) |                                                  |
| **Single-entry**                                                                      | ✅                                               | ✅                                               | ✅                          |                                                  |
| **Multi-entry**                                                                       |                                                 |                                                 |                            | ✅                                                |
| **Device support**                                                                    | Desktop *or* mobile (one device type per study) | Desktop *or* mobile (one device type per study) | Desktop only               | Desktop or mobile (one device type per activity) |
| **Recruitment options**                                                               |                                                 |                                                 |                            |                                                  |
| **Auto-recruit**                                                                      | ✅                                               | ✅                                               | ✅                          |                                                  |
| **Add participants from screeners** (manual recruit)                                  | ✅                                               | ✅                                               |                            | ✅                                                |
| **Bring your own participants** (via share link or email)                             | ✅                                               | ✅                                               |                            | ✅                                                |
| **Add participants from Private Panels**                                              | ✅ (via Dscout or Private Panels)                | ✅ (via Dscout or Private Panels)                |                            | ✅ (via Private Panels)                           |
| **Multi-variate**                                                                     | ✅                                               | ✅                                               | ✅                          |                                                  |
| **Auto-transcription**                                                                | ✅                                               |                                                 | ✅                          |                                                  |
| **Playlist creation**                                                                 | ✅                                               | ✅                                               | ✅                          | ✅                                                |
| [**Explore your data**](/dscout-ai/dscout-ai-studio/explore-your-data) (add-on)       | ✅                                               | ✅                                               | ✅                          |                                                  |
| [**AI summaries**](/dscout-ai/built-in-ai-features/ai-summaries) (add-on)             | ✅                                               | ✅                                               | ✅                          | ✅                                                |
| [**AI themes**](/dscout-ai/built-in-ai-features/ai-themes) (add-on)                   | ✅                                               | ✅                                               | ✅                          | ✅                                                |
| [**AI notable moments**](/dscout-ai/built-in-ai-features/ai-notable-moments) (add-on) | ✅                                               |                                                 | ✅                          |                                                  |

#### Moderated studies

|                                                                                       | **Interview studies**                           |
| ------------------------------------------------------------------------------------- | ----------------------------------------------- |
| **Continuously recorded**                                                             | ✅                                               |
| **Single-entry**                                                                      | ✅                                               |
| **Multi-entry**                                                                       |                                                 |
| **Device support**                                                                    | Desktop *or* mobile (one device type per study) |
| **Auto-recruit**                                                                      |                                                 |
| **Add participants from screeners** (manual recruit)                                  | ✅                                               |
| **Bring your own participants** (invite via share link or email)                      | ✅                                               |
| **Add participants from Private Panels**                                              | ✅ (via Private Panels)                          |
| **Auto-transcription**                                                                | ✅                                               |
| **Playlist creation**                                                                 | ✅                                               |
| [**Explore your data**](/dscout-ai/dscout-ai-studio/explore-your-data) (add-on)       | ✅                                               |
| [**AI summaries**](/dscout-ai/built-in-ai-features/ai-summaries) (add-on)             |                                                 |
| [**AI themes**](/dscout-ai/built-in-ai-features/ai-themes) (add-on)                   |                                                 |
| [**AI notable moments**](/dscout-ai/built-in-ai-features/ai-notable-moments) (add-on) |                                                 |

### Choose a recruitment method

Whichever study type you choose, it’s important to fill your study with the highest quality participants. To help, Dscout offers several options:

* **Recruit using a screener:** Build a screener directly in Dscout using targeting attributes and knockout questions to find only the right participants. You can keep your screener private and only send it to people you choose or make your screener public and recruit from Dscout’s on-hand pool of participants (called Scouts). For more information, see [Set up a screener](/recruit-participants/what-are-dscout-screeners/set-up-a-screener).
* **Bring your own participants:** Invite participants you’ve already screened and know would be a good fit for your study. These could be people you have on a mailing list, in which case you could generate a share link for your study to grant them access. Or, these might be people on a panel you maintain for ongoing research in Private Panels. Either way, if you already have people in mind to participate, you can invite them to your Dscout study.

{% hint style="info" %}
Running research on Dscout requires **activity credits**, and both study type and recruitment approach can affect how many activity credits you need. For more information, see [Activity credits](/account-management/organization-account-settings/activity-credits).
{% endhint %}

### Create a project

Once you’ve figured out which study type fits your needs and how you want to recruit for it, it’s time to get started. The next step is to create a project (if you don’t already have one!).

Think of projects as folders to keep your research organized. You might need multiple studies to get the insights you’re looking for, and you can keep them all together in a single project.

To create a project, click **New Project** in the top-right corner of the Dscout homepage.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4wSy8qqijlrMMbRePEJs/39583985396756)

Now, you’re taken to the blank project’s page where you can edit the project’s details, build studies and screeners, and invite collaborators.

{% hint style="success" %}
Give your project a descriptive title and quick description so any collaborators you invite have context around the project’s purpose. Don’t worry—your research participants won’t see either of these.
{% endhint %}

### Additional resources

You’ll find answers to nearly any of your Dscout-related questions here on our help center. But if you’re still unsure of where to get started, or if you need just a little bit of inspiration to get you going, here are a few other resources that might be able to help:

* [Dscout 101: Product Deep Dive Webinar](https://dscout.showpad.com/share/wVrbcF6A8yVKcvB30IFNQ).
* [Dscout’s People Nerds blog](https://www.dscout.com/people-nerds).
* [Dscout support](mailto:support@dscout.com).


# Navigate the Dscout platform

First things first, welcome to Dscout! There’s so much we can help you discover, but before we dive in, let’s cover the basics of navigating the platform.

### Homepage (Projects page)

When you first log in to Dscout, you’ll find yourself on the Dscout homepage. Here, you’ll see all your projects, including those you’ve created and those you’ve been invited to collaborate on.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/u3uc746NUxtup9oXcbjK/39583985424020)

| Section                                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sidebar navigation** (1)              | <p>The sidebar is your fastest way to get around the Dscout platform. Directly below the Dscout logo, you’ll see your Dscout account name. If your account has workspaces enabled, this serves as a drop-down where you can easily switch between workspaces.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> The contents of the sidebar may vary depending on your user role. If you don’t see something you think you should have access to, reach out to your Dscout account owner.</p></div><p>Below that, you’ll find quick links to:</p><ul><li>The projects page (or the homepage), where you can see all the projects you’re a part of or create a new project.</li><li>Private Panels, Dscout’s panel management tool. (Available only to accounts with the Private Panels add-on. For more information, see Private Panels.)</li><li>The question banks tab of account management, where you can view and edit saved questions.</li><li>Our product feedback form, the Dscout help center, and other support options.</li><li>News and other product updates you might have missed.</li></ul><p>When you favorite projects, they’ll also appear here for easy access. Just click the project name to head straight there.</p><p><br>The side navigation is also how you’ll access your profile and account settings. Just click your profile avatar to see the list of options.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> You can open the side navigation from anywhere in the platform by clicking the <strong>Open sidebar</strong> button in the top-left corner of the page.</p></div> |
| Projects **search** and **filters** (2) | Here, you can enter search terms to quickly find the project you’re looking for, or use the filters **All**, **Created by you**, **Created by others**, and **Completed** to view only the projects that fit into those categories.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| **New project** button (3)              | <p>Click this button to create a new Dscout project. You’ll then be taken to the blank project’s page where you edit the project’s details, build studies and screeners, and invite collaborators.</p><p><br>For more information, see <a href="https://github.com/briansaladino23/researcher-help/tree/main/getting-started/workspaces-and-projects/create-a-project-mission-or-screener.md">Create a Dscout project</a>.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| **Project** row (4)                     | <p>Projects are represented on the Dscout homepage in rows, with each project row giving you a preview of the studies and screeners in that project as well as the project’s creator and collaborators. To make sure you’re always seeing the most relevant research, this list is sorted with your most recently modified projects and studies first, followed by those most recently modified by your teammates.</p><p><br>Click a project row to go to that project. Or, click a specific study to go directly to that study. You can also click directly on the collaborators list to add additional collaborators and viewers.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

### Project details page

Navigating to a specific project brings you to the product details page. Here, you’ll see a comprehensive list of all the studies and screeners that make up the project.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/HCppYP0Jks42haW91y57/39584045734164)

| Section                                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project **title** (1)                     | The title of your project. Click anywhere in the title to edit.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| Project **description** (2)               | The description of your project. Click the **Edit** button to change the description.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| Project **stats** (3)                     | <p>A quick-glimpse overview of the research conducted across all studies in your project, including:</p><ul><li><strong>Total submissions:</strong> The total count of all submitted entries across usability tests, media surveys, and diary studies.</li><li><strong>Total participants:</strong> The total count of unique individuals who have actively contributed to a research study. This includes anyone who has completed a usability test or media survey, submitted at least one entry to a diary study, or completed an interview session.</li><li><strong>Interview sessions:</strong> The total count of all completed interview sessions.</li><li><strong>Playlists created:</strong> The total count of all playlists that have been generated in the project.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> These totals do not include rejected screener applicants or their screener submissions.</p></div> |
| Project **creator and collaborators** (4) | <p>The first name displayed here is the creator of the project (or the project lead, if assigned). The other names are project collaborators. Click here to open the project collaborators modal, where you can view the full list, add/delete collaborators, and more.</p><p><br>For more information, see <a href="/getting-started/collaborate-in-dscout/manage-project-collaborators">Manage project collaborators</a>.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Studies and screeners** tabs (5)        | Use these tabs to switch between viewing the **studies** in your project and the **screeners** in your project. Studies contain your research while screeners are how you recruit for that research.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| **Study and screener** tiles (6)          | Each study and screener in your project is represented by a tile, which displays the study status, study type, and study title. Click a tile to go to that study or screener.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| **Create study or screener** button (7)   | <p>Click this button to create a new study or screener (be sure you’re on the right tab for what you want to create!).</p><p><br>For more information creating studies or screeners, see:</p><ul><li><a href="/recruit-participants/what-are-dscout-screeners/set-up-a-screener">Set up a screener</a>.</li><li><a href="/usability-tests/create-a-usability-test">Create a usability test</a>.</li><li><a href="/media-surveys/create-a-media-survey">Create a media survey</a>.</li><li><a href="/intercept-studies/create-an-intercept-study">Create an intercept study</a>.</li><li><a href="/diary-studies/what-are-diary-studies-in-dscout/set-up-a-diary-study">Create a diary study</a>.</li><li><a href="/interview-studies/create-an-interview-study">Create an interview study</a>.</li></ul>                                                                                                                                                                                                |

Once you’ve gotten the hang of navigating these two pages, you’re well on your way to streamlining your research and uncovering exciting new insights with Dscout. And if you’re looking for a deeper dive, here are a few other articles to check out:

* [Dscout quickstart guide](/getting-started/dscout-quickstart-guide).
* [Workspaces in Dscout](/getting-started/workspaces-and-projects).


# User roles and permissions

Conducting good research is a team sport, and there are a few different roles each teammate might play. Whether you’re managing a Dscout account for your organization or in the thick of conducting interviews, here’s a comprehensive breakdown of what your role means for what you can do on the platform.

{% hint style="info" %}
**Note:** Roles and permissions work a little differently when conducting interview sessions in Dscout. For more information, see [User roles in interview sessions](/interview-studies/what-are-interview-studies-in-dscout/user-roles-in-interview-sessions).
{% endhint %}

### User roles

There are five possible roles a user might have in Dscout:

* **Account Owner:** The member of your organization responsible for managing your overall Dscout subscription, including plan renewal, new feature access, and more. There is only one Account Owner per Dscout account.
* **Admins:** Members of your organization who might do some research but mainly monitor user access, billing, and more.
* **Researchers:** Members of your organization who are in the thick of conducting research. These might be members of your research team, UX designers, or anyone else who wants to get feedback from real users.
* **Contributors:** Members of your organization who may occasionally conduct research but mostly want to be able to see the research others are conducting. Users may also be assigned this role if they only need access to certain Dscout tools. These users can build and launch usability tests, media surveys, intercept studies, and interview studies, but they only have read/comment access to screeners and diary studies.
* **Viewers:** Members of your organization (or external stakeholders) who don’t need to conduct research directly but may want to see what research is being conducted. These users cannot build or launch research in Dscout.

{% hint style="info" %}
**Note:** If you have any questions about specific roles in your Dscout account, or if you don’t see roles available when you believe they should be, contact your Dscout Account Manager.
{% endhint %}

### Permissions by role

To learn which users can perform specific actions, use the tables below.

#### Platform access

| Permission                      | Account Owner | Admin                                        | Researcher                                   | Contributor               | Viewer                                |
| ------------------------------- | ------------- | -------------------------------------------- | -------------------------------------------- | ------------------------- | ------------------------------------- |
| **Project access**              | All projects  | All projects                                 | Projects they’re added to                    | Projects they’re added to | Projects they’re added to (view-only) |
| **Account management settings** | Yes           | Yes                                          | Yes                                          | No                        | No                                    |
| **Billing information**         | Yes           | Yes                                          | Yes                                          | No                        | No                                    |
| **Add new users**               | Yes           | Yes (cannot add Account Owners or Admins)    | Yes (cannot add Account Owners or Admins)    | No                        | No                                    |
| **Manage user roles**           | Yes           | Yes (cannot manage Account Owners or Admins) | Yes (cannot manage Account Owners or Admins) | No                        | No                                    |

#### Screeners

| Permission                                | Account Owner | Admin | Researcher | Contributor | Viewer |
| ----------------------------------------- | ------------- | ----- | ---------- | ----------- | ------ |
| **Build and launch screeners**            | Yes           | Yes   | Yes        | No          | No     |
| **Comment on screeners**                  | Yes           | Yes   | Yes        | Yes         | Yes    |
| **Assign fit categories to participants** | Yes           | Yes   | Yes        | No          | No     |

#### Usability tests, media surveys, and intercept studies

| Permission                   | Account Owner | Admin | Researcher | Contributor | Viewer |
| ---------------------------- | ------------- | ----- | ---------- | ----------- | ------ |
| **Build and launch studies** | Yes           | Yes   | Yes        | Yes         | No     |
| **Comment on studies**       | Yes           | Yes   | Yes        | Yes         | Yes    |
| **Tag responses**            | Yes           | Yes   | Yes        | Yes         | No     |
| **Access Test mode**         | Yes           | Yes   | Yes        | Yes         | No     |

#### Diary studies

| Permission                                  | Account Owner | Admin | Researcher | Contributor | Viewer |
| ------------------------------------------- | ------------- | ----- | ---------- | ----------- | ------ |
| **Build and launch diary studies**          | Yes           | Yes   | Yes        | No          | No     |
| **Leave notes (comments) on diary studies** | Yes           | Yes   | Yes        | Yes         | Yes    |
| **Tag responses**                           | Yes           | Yes   | Yes        | Yes         | No     |

#### Interview studies

| Permission                                      | Account Owner | Admin | Researcher | Contributor | Viewer |
| ----------------------------------------------- | ------------- | ----- | ---------- | ----------- | ------ |
| **Build and launch interview studies**          | Yes           | Yes   | Yes        | Yes         | No     |
| **Moderate interview sessions**                 | Yes           | Yes   | Yes        | Yes         | No     |
| **Leave notes (comments) on interview studies** | Yes           | Yes   | Yes        | Yes         | No     |

#### Dscout AI Studio

{% hint style="info" %}
**Note:** All access to Dscout AI Studio requires the Dscout AI add-on. For more information, see [Dscout AI](/dscout-ai/what-is-dscout-ai).
{% endhint %}

| Feature                  | Account Owner | Admin | Researcher | Contributor | Viewer                                                                      |
| ------------------------ | ------------- | ----- | ---------- | ----------- | --------------------------------------------------------------------------- |
| **Explore your data**    | Yes           | Yes   | Yes        | Yes         | No                                                                          |
| **Draft your study**     | Yes           | Yes   | Yes        | Yes         | No                                                                          |
| **AI moderated studies** | Yes           | Yes   | Yes        | Yes         | View access (same as usability tests, media surveys, and intercept studies) |
| **Dscout MCP**           | Yes           | Yes   | Yes        | Yes         | Read-only tools                                                             |

### Add new users

Account Owners, Admins, and Researchers can all add new users to your organization’s Dscout account. If you’re in one of these roles, you’ll add new users from the **Account management** page.

{% hint style="success" %}
If someone already has a Dscout account and just needs access to your project, see [Manage project collaborators](/getting-started/collaborate-in-dscout/manage-project-collaborators).
{% endhint %}

{% stepper %}
{% step %}
Click the name of your Dscout account in the sidebar navigation.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/crSAC7jkVznbeTRMde6H/39771432973332)
{% endstep %}

{% step %}
Click the **Settings** icon. The **Account management** page is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/As6BqTpselxxGXzC5NRw/39771447008916)
{% endstep %}

{% step %}
Select the **Users** tab. The list of users across your account is displayed.
{% endstep %}

{% step %}
Click **Add a user** in the top left corner of the page.
{% endstep %}

{% step %}
Enter the new user’s **First name**, **Last name**, and **Email**.
{% endstep %}

{% step %}
Select a **Role** to assign to the user.

{% hint style="info" %}
Only Account Owners can designate someone as an Admin.
{% endhint %}
{% endstep %}

{% step %}
(If applicable) Select which **Workspaces** the new user should have access to.
{% endstep %}

{% step %}
Click **Next**.
{% endstep %}

{% step %}
Select the **Projects** the new user should have access to.

{% hint style="info" %}
Admins are added to all projects by default.
{% endhint %}
{% endstep %}

{% step %}
Click **Add user**.
{% endstep %}
{% endstepper %}

Now, an invitation is sent to the email you entered, instructing the user to create their Dscout login. After creating their account, they’ll have access to the projects you selected. To change a user’s role, return to this page and select a new role from the **Change role** drop-down in that user’s row:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/gyi1Rixo2FlGE9OrkHUG/39771432986516)

To remove a user, click the **Remove user (trash)** icon in that user's row, then click **Yes** in the confirmation modal:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/E6iCzx08Rl2r4gel3KMG/46708407405716)

### Flex seats

On some Dscout plans, you're able to adjust which users occupy certain roles on an as-needed basis. This allows you to customize your team's ability to conduct research on a cadence that makes the most sense for you. To change role types, follow the steps under Add new users to access the **Users** page, then select the desired role type for your users from the **Change role** drop-down. And to learn more, below are some frequently asked questions around how flex seats work.

<details>

<summary>How quickly do seats change owners?</summary>

When updating user roles, changes take effect immediately! At most, users currently signed in to Dscout may need to refresh their browser to see the changes reflected.

</details>

<details>

<summary>Can I change seats at any time?</summary>

Yes, as long as you have seats available. For example, if you need to assign someone a **Researcher** seat, one must be available on your account. This may require switching an existing **Researcher** to a lower role to free up their seat.

</details>

<details>

<summary>Are there best practices for changing seats?</summary>

If you've exceeded your account's seat limits, we recommend downgrading those who don't need full access to the **Viewer** role to free up seats for other users. Viewers retain access to the same projects just with fewer permissions. So in short: downgrade user roles first, then upgrade those as needed.

</details>

<details>

<summary>Will users lose data when seats are re-assigned?</summary>

No! We never want to remove your data, even after your research is finished. Downgrading users to the **Viewer** role will not remove their data, though they may be able to do less with it (refer to the table above for more information). However, keep in mind that data *is* deleted if a user's account is deleted entirely.

</details>


# Using the Dscout sandbox

To become familiar with Dscout, your Account Manager might set you up with a sandbox to test things out. Use this guide to understand how you can use the Dscout sandbox to learn the ropes of the platform.

{% hint style="success" %}
Interested in getting started with Dscout? Reach out to <sales@dscout.com> for more information!
{% endhint %}

### What can I do in the sandbox?

To begin building research after creating your account (or logging in), click "My Sandbox Project," which takes you inside the test environment. From here, you’ll be able to create as many test studies as you like. Not sure what study type is right for you? Check out our overview of each study type [here](/getting-started/dscout-quickstart-guide)!

{% hint style="info" %}
**Note:** While you can build a screener in a sandbox project, you will not be able to launch to Dscout's Scout Panel or test out the participant experience.
{% endhint %}

In each tool, you can build and customize your project, just like you would with an actual study.

In **usability tests** and **media surveys**, this means creating a one-sitting study using prompt types such as card sorting, tasks, and talk-out-loud questions.

![Screenshot 2024-07-29 at 2.54.18 PM.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/s2JVUPnSo12OM3HxUpVy/28919061322516)

In **diary studies**, this means creating your own questions and activities. [Question types](/diary-studies/what-are-diary-studies-in-dscout/question-types-in-diary-studies) allow you to ask for responses with photos, videos, text and more, and [activities](/diary-studies/what-are-diary-studies-in-dscout/understanding-studies-activities-and-entries-for-researchers) allow you to ask participants different sets of questions.

![Screenshot 2024-07-29 at 2.27.50 PM.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rgriEkk9PhhvQ8dvTYD8/28918946574484)

In **interview studies**, you can set up and test a 1:1 video call with a colleague. This is a great opportunity to experiment with our scheduling and stimuli features. More details on what you can do with Dscout live interviews are [here](/interview-studies/what-are-interview-studies-in-dscout).

![1.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/nWxaAaPf1Z1GPM4YiG2O/28918902558356)

After creating a study, you can test the full participant experience by clicking the "Test" option—check out the articles below for more on test mode in each study type:

* [Test a usability test](/usability-tests/create-a-usability-test/test-a-usability-test).
* [Test a media survey](/media-surveys/create-a-media-survey/test-a-media-survey).
* [Test a diary study](/diary-studies/what-are-diary-studies-in-dscout/test-mode-in-diary-studies).
* [Test an interview study](/interview-studies/create-an-interview-study/test-an-interview-study).

### Can I invite others to build with me?

Of course! Not only can you invite people to participate in your project as a “Scout,” (check out the "test mode" guidance in the section above!), but you also can invite them to help you build your research. To do so, click the **+ Add** button on your project home page, then enter the email address or addresses of the colleagues you'd like to invite. (Learn more about adding collaborators [here](/getting-started/collaborate-in-dscout/manage-project-collaborators).)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/WmiPqCeyRlRY0nKNykzN/41598572047252)

### Next Steps

Interested in getting set up with a Dscout subscription? Reach out to [sales@dscout.com](mainto:sales@dscout.com) or your Account Manager regarding next steps.

The sandbox is designed to be easy to use and test, but if any questions arise, we’re happy to help. Feel free to search our Help Center for an answer, or email <support@dscout.com> and we’ll assist however we can.


# Dscout subscriptions

Dscout offers full annual subscriptions that give your team the flexibility to run more in-context research, with less friction. We can configure a plan that’s right for you based on the number of anticipated users in your organization, the number of studies you plan to run, and the level of support you’d like from us.

To discuss our subscription offerings, [book a call](https://dscout.com/pricing#form) with our Sales Team. For questions related to your current Dscout subscription, get in touch with your Dscout Account Owner or your Dscout Research Advisor.


# Workspaces and projects

Use workspaces and projects to organize research, manage access, and keep studies grouped logically. Start here for setup, navigation, and project maintenance.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Creating and navigating Dscout workspaces</td><td><a href="/getting-started/workspaces-and-projects/creating-and-navigating-dscout-workspaces">Creating and navigating Dscout workspaces</a></td></tr><tr><td>Create a project study or screener</td><td><a href="https://github.com/briansaladino23/researcher-help/tree/main/getting-started/workspaces-and-projects/create-a-project-mission-or-screener.md">https://github.com/briansaladino23/researcher-help/tree/main/getting-started/workspaces-and-projects/create-a-project-mission-or-screener.md</a></td></tr><tr><td>Project review checklist</td><td><a href="/getting-started/workspaces-and-projects/project-review-checklist">Project review checklist</a></td></tr><tr><td>Mark a project as complete</td><td><a href="/getting-started/workspaces-and-projects/mark-a-project-as-complete">Mark a project as complete</a></td></tr></tbody></table>


# Creating and navigating Dscout workspaces

Workspaces serve as distinct spaces within an account where projects, team members, and budgets are housed. Using workspaces, you can create multiple Dscout environments for different teams of users dedicated to a particular area of research or aligned with a cost center. Workspaces can either be public, seen by anyone on the account, or private, seen by selected members only.

Being a member of a workspace does not grant access to all projects inside that workspace. To ensure your teammates have access to the projects they need, see Manage project collaborators.

## Create a workspace

Account owners and administrators can create and delete workspaces. If this option is not available to you, then you do not have permissions to add a workspace. Reach out to your Dscout account manager to learn more about setting up a workspace in your account.

{% stepper %}
{% step %}
Click your Dscout account name in the sidebar navigation. A list of your existing workspaces is displayed.
{% endstep %}

{% step %}
Click **Create new workspace**. The create new workspace modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JXNabjGOmK1aopQtBgWi/39583985487636)
{% endstep %}

{% step %}
Enter the following:

1. **General Information:** Name your workspace and decide if you would like to add a description– for example the project, area of research, or even team/department this workspace has been created for.
2. **Privacy:** choose whether you would like your workspace to be '*public'* or '*private'*.
   * If your workspace is set to 'public' anyone in the account is able to see the team the workspace belongs to, their description, and members who belong to it.
   * If your workspace is set to 'private', only people who have been added to that workspace as members can see the contents of the workspace.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/zDthlsPQb8WQskimDQf0/23398097420820)
{% endstep %}

{% step %}
Add members to your workspace.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/PxHJNCQI5D2PvhjUlIKj/23398097428884)
{% endstep %}

{% step %}
Allocate funds to this workspace for step 3 of 3. For more information, see [Balances](#balances).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6sbTTkAvHhvpM3EcwRGo/23398090293140)
{% endstep %}
{% endstepper %}

### Visibility

* Account owners and admins are added to all workspaces and all projects by default. Only account owners, admins, and Dscout staff can add members to a workspace.
* Researchers, managers, and members are only able to see balances for workspaces they have been added to.
* Contributors and viewers are not able to see any workspace balances.
* For both 'public' and 'private' workspaces, collaborators must still be added to projects to see their studies and data. For more information, see [Manage project collaborators](/getting-started/collaborate-in-dscout/manage-project-collaborators).

### Balances

*Please note: All balances are related to the current subscription term you are in. They do not reflect usage or balances from previous terms.*

![Screenshot 2024-02-02 at 10.56.08 AM.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/f3cON0hSMNvdxtozwZYt/23398090307604)

* **Who can edit balances**
  * Only account owners, account admins, and Dscout staff can edit balances within a workspace. Please reach out to your account manager with any questions regarding workspace balances.
* **Support hours, Credits/Completes and Incentives**
  * **Allocated:** Shows the number of support hours, credits/completes, and incentives that have been allocated to that workspace for the subscription period. (total allocated located in the denominator below each usage bar on the left)
  * **Used:** Shows you the number of support hours, credits/completes, and incentives that have been used out of the total allocated amount. (total used located in the numerator below each usage bar on the left)
  * **Remaining:** Total number of support hours, credits/completes, and incentives that are remaining and available to use. *Remaining = Allocated - Used* (Total remaining located to the right of the category (e.g. support hours, credits/completes, or incentives) in bold)
  * **Available for allocation:** Support hours, credits/completes, and incentives that belong to the account but are not yet allocated to a particular workspace. When updating allocations, this shows you what is available for you to pull from or return to, and can be re-allocated to another workspace if not used.
* **Updating allocations**
  * This is where you go to make adjustments to your budget. You can adjust your balances using what is available in the *‘Available for allocation’* field or return hours/credits/incentive funds back to the available account pool for another workspace to use.

#### Update your workspace balances

Account owners, admins, and Dscout staff can set up workplace balances. If you do not have permissions to and need to set up a workplace balance, please reach out to your Dscout account manager.

**To manage workspace balances:**

{% stepper %}
{% step %}
Click your Dscout account name in the sidebar navigation. A list of your existing workspaces is displayed.
{% endstep %}

{% step %}
Click the **Settings** icon for the account you want to manage. The workspace settings modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/oEgwznYZNnhmoz4XLfYV/39583985491092)
{% endstep %}

{% step %}
On the **Balances** tab, click **Update allocations**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/9p2ZTy7sv8il7Afd2aOq/23398090322836)
{% endstep %}

{% step %}
Adjust the workspace's balances as needed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/q7AxYsbxw3kzDhcFPndN/23398090327316)

You can adjust your balance using what’s available in the *'Available for allocation'* field or return hours/credits/incentive dollars back to the available account pool for another workspace to use.
{% endstep %}
{% endstepper %}

#### Move balances between workspaces

In some cases you may want to move budget between workspaces. If nothing is available on the account for allocation but you want to transfer funds from one workspace to another.

* You first need to deduct from the workspace you want to take funds from. Open up the balance tab in the settings of the workspace you want to deduct from. *(In the example below, we are deducting from the workspace: Quiet Lab.)*

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/f3cON0hSMNvdxtozwZYt/23398090307604)
* Go to their *'Update allocations'* modal.

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/YoqY9hiUubCsntIpOXYK/23398097495700)
* Deduct the amount of support hours/activity credits/incentives you want to transfer from their balance. Then confirm your change. *(In the example below we are deducting 10 activity credits, and $100 in incentives from the workspace: Quiet Lab.)*

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4KAXf29Z6YUlmWFwTIDS/23398090342548)
* Navigate to the workspace you want to give funds to and open up the *'Balances'* tab in the settings of that workspace. *(In the example below, we will be adding to the workspace: Loud Friends.)*

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cR8T21UtKzJHRmQxxKZS/23398097527444)
* Go to the second workspace's *'Update allocations'* modal and add the amount of support hours/activity credits/incentives you want to add from the first workspace’s balance. Then confirm your change. *(In the example below we are adding 10 activity credits, and $100 in incentives to the workspace: Loud Friends.)*

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/BQlb4zW0hG46ZPko9GNo/23398097540628)

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ggrpLXpz0FCcPhjDsq7m/23398090381076)
* You have successfully reallocated funds from one workspace to another!

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/DHt7KmbGjIUoINxaFhWl/23398097592852)

#### Navigate between multiple workspaces

If you are a member of more than one workspace, it’s important that you create every project in the correct workspace. This way the research in every project is associated with the correct workspace’s balance and usage.

If a project is created in the wrong workspace, reach out to your Dscout account manager or research advisor and they can assist with moving it.

### Workspace Leads

Naming a researcher “workspace lead” grants them admin permissions on a specific workspace.

Workspace leads can:

* See all research within the workspace
* Edit team name, description, privacy settings
* Add/remove members
* Promote other members within the workspace to workspace lead
* Add/remove budget from their workspace
* Be workspace lead of multiple workspaces
* Receive an email when research is launched in their workspace

Workspace leads cannot:

* Create a new workspace
* Edit the details, members, or budget of a workspace they are not a lead on
* Change account-level settings
* Occupy a contributor or viewer seat

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ACt2bugBUIJjuZMq9E1J/28778247647636)


# Create a project, study, or screener

Whether you’re creating a new study, a screener to help recruit for that study, or a project to keep it all organized, here’s a quick guide to get you started.

## Create a project

Think of projects as folders to keep your research organized. You might need multiple studies or studies to get the insights you’re looking for, and you can keep them all together in a single project.

To create a project, click **New Project** in the top-right corner of the Dscout homepage.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4wSy8qqijlrMMbRePEJs/39583985396756)

Now, you’re taken to the blank project’s page where you can edit the project’s details, build studies and screeners, and invite collaborators.

{% hint style="success" %}
**Tip:** Give your project a descriptive title and quick description so any collaborators you invite have context around the project’s purpose. Don’t worry—your research participants won’t see either of these.
{% endhint %}

## Create a study

Studies are the heart of conducting research in Dscout. They’re how you build, manage, and field moderated and unmoderated studies. Once you’ve created a project, you can start creating studies.

**To create a study:**

{% stepper %}
{% step %}
Navigate to the project where you want your study to live.
{% endstep %}

{% step %}
Click the **Create study** button in the top-right corner of the page. The **Create something new** modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/xqr8cEQs9d38k302ynmk/39583985648916)
{% endstep %}

{% step %}
Select a study type from the following options:

* **Usability test:** Great for quickly validating and iterating with heat maps, task prompts, and more.
* **Media survey:** Great for capturing deep survey data with photos, videos, and more.
* **Diary study:** Great for exploring habits and behaviors over time through multiple activities.
* **Interviews:** Great for having moderated sessions with participants with automated transcripts, notes, and more.
* **Intercept study:** Great for gathering in-the-moment feedback from users of live websites.
* **AI moderated study (beta):** Great for gathering interview-style responses at scale.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FpcEujx6iCUF9TyVVPo51%2FScreenshot%202026-08-03%20at%201.06.55%E2%80%AFPM.png?alt=media&amp;token=ca029831-52ac-4ba3-85c0-133628a3c955" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Follow the prompts to set up your selected study.
{% endstep %}
{% endstepper %}

For more study type-specific help, check out the following articles:

* [Create a usability test](/usability-tests/create-a-usability-test).
* [Create a media survey](/media-surveys/create-a-media-survey).
* [Create a diary study](/diary-studies/what-are-diary-studies-in-dscout/set-up-a-diary-study).
* [Create an interview study](/interview-studies/create-an-interview-study).
* [Create an intercept study](/intercept-studies/create-an-intercept-study).
* [Create an AI moderated study](/dscout-ai/dscout-ai-studio/ai-moderated-studies).

## Create a screener

Screeners are how you recruit participants to join your studies. You can create a public screener to recruit directly from Dscout’s pool of participants (known as Scouts) or a private screener which you can then share with whoever you want using a dedicated share link.

{% stepper %}
{% step %}
Navigate to the project where you want your screener to live.
{% endstep %}

{% step %}
Click the **Screeners** tab at the top of your project.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5jY4b3PEPStYwj05zUYc/39583985492756)
{% endstep %}

{% step %}
Click the **Create screener** button in the top-right corner of the page.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/qzkAo30k27M4RarSQivD/39583985494548)
{% endstep %}

{% step %}
Follow the prompts to set up your screener.
{% endstep %}
{% endstepper %}

For more information on creating a screener, see [Set up a screener](/recruit-participants/what-are-dscout-screeners/set-up-a-screener).


# Project review checklist

Before submitting your project for review, use this checklist to make sure you're on the right track.

Make sure to draft both your study *and* your screener before submitting your Dscout project for review. This gives Dscout research advisors the necessary ability to review your entire project.

## Questions to ask yourself about your screener:

* **Title:** Did you add an attention-grabbing title to interest applicants?
* **Teaser**: Does your screener have an attention-catching name, and does your teaser clearly communicate what your project is about? If scouts will need to take a picture/video or be in a specific place while applying, do you give them a heads-up?
* **Timeline**: Do you accurately indicate the study's duration, type of study, and expected launch date?
* **Compensation:** The more time and effort required of scouts, the more they'll expect to be paid. (And only scouts who completely finish your project get compensated.)
* **Targeting Attributes:** Add any desired [targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes) to hone in on your intended audience (these pre-screened questions can reduce the number of questions you need to add to your screener).
* **Structure**: Starting your screener with 1 or 2 [knockout questions](/recruit-participants/dscout-scout-panel/knockout-questions) in the Qualify tab will save you time by removing ineligible scouts from the applications you receive. (You'll automatically see each applicant's age, gender, and city, so no need to ask for these.)
* **Media**: If you ask scouts for a video (and if you ask for any videos in your study, you should), can they reasonably answer your prompt in 30 or 60 seconds?
* **Open vs Closed Questions**: Do you include at least one open ended question so you can see how well scouts explain themselves? Do your closed questions include a "none of the above" option?
* **Question Settings**: Check that you applied any needed [skip logic](/study-basics/design-a-study/skip-logic-in-screeners), apply the 140 character limit to open-ended questions when you want scouts to answer in a few words or less, and check all scale questions to ensure the scale minimum and maximum align with your prompt.

## Questions to ask yourself about your study and its activities:

* **Study Overview:** Does your overview mention your study's due date and your project's compensation amount?
* **Activity Instructions**: Do your instructions clearly tell scouts what they're supposed to capture for you?
* **Structure**: How is your study structured? Do you have multiple activities? Do any of your activities require multiple entries (and if so, does it make sense for them to?) Or, if you used a study template, did you customize the language to meet your project's needs?
* **Media**: Do(es) your media prompt(s) ask scouts to capture the specific experience you want to see most?
* **Open vs. Closed-ended Questions**: Closed questions are easy to filter and analyze; open questions provide more depth but take longer to review. Do you have the right combination to get the results you're looking for?
* **Scouts' Perspective:** Have you double checked your project's design by launching test of your study and inviting yourself to it?


# Mark a project as complete

When all research in a project has been completed, you can mark it as complete to close it.

**When a project is marked as complete:**

* All studies and screeners within the project are closed.
* The project is moved to the **Completed** view of your Dscout account and cannot be moved back.
* Studies and screeners within the project can no longer be duplicated or moved out of the project.
* If automatic project deletion is enabled, the project is queued for deletion according to your organization’s settings. For more information, see [Project data deletion](/account-management/organization-account-settings/project-data-deletion).

{% stepper %}
{% step %}
On the **Projects** page, click the three-dot icon on the project you want to complete.
{% endstep %}

{% step %}
Select **Complete project**. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5WzCx6nDFHoeD0SUC0pE/41597991022612)
{% endstep %}

{% step %}
Click **Complete project** to confirm.
{% endstep %}
{% endstepper %}

Now, any open studies or screeners in your project are closed and the project is moved to the **Completed** view of your Dscout account.

**To view completed projects**, click **Completed** in the top right corner of the Projects page:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/n6M46ugXokeUWyn4ci5w/41597991023636)

{% hint style="info" %}
Projects will only remain in your **Completed** view in accordance with your organization’s project data deletion protocol. For more information, see [Project data deletion](/account-management/organization-account-settings/project-data-deletion).
{% endhint %}


# Research basics

Use these guides to plan research that is accessible, inclusive, and appropriate for your audience. Start here for core practices, consent guidance, and international research considerations.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Accessibility</td><td><a href="/getting-started/research-basics/accessibility">Accessibility</a></td></tr><tr><td>Inclusive research guidelines</td><td><a href="/getting-started/research-basics/inclusive-research-guidelines">Inclusive research guidelines</a></td></tr><tr><td>Custom informed consent</td><td><a href="/getting-started/research-basics/custom-informed-consent">Custom informed consent</a></td></tr><tr><td>Can I do international research with Dscout</td><td><a href="/getting-started/research-basics/can-i-do-international-research-with-dscout">International research with Dscout</a></td></tr></tbody></table>


# Accessibility

If you are a researcher and you have a specific accessibility need that is not supported by the Dscout Platform, please send an email to <legal@dscout.com> describing your accessibility need and/or the accommodation requested.


# Inclusive research guidelines

Research has the power to make the world a better place. For this to happen, researchers have a responsibility to do more inclusive research.

We’ve long hoped the tool we’ve built at Dscout can facilitate empathy-inspiring, context-revealing work. But who we empathize with, how effectively we empathize, what context we reveal, and how we arrive at that context can be the difference between research that is genuinely in service to others, or that leaves a large swath of users out.

We drafted these guidelines to promote an inclusive environment where all scouts feel safe, respected, valued, and free to be who they are. They’re a starting point, a collection of best practices from a number of excellent sources who have been advocating in this space for some time.

We at Dscout acknowledge that we are entering an active conversation that has been happening for decades, and are continuously working to listen and learn how to better advocate for and facilitate more inclusive research. We encourage our community of researchers to do the same.

## Embrace research participants as stakeholders and collaborators

Remember that research should always be in service to your participants. Non-extractive research requires bidirectional respect. Build a trusting relationship with your participants through reliable communications, clear expectations and fair incentives. ([read more](https://dscout.com/people-nerds/ux-that-serves))

* For example, be mindful of instances when economic insecurity could be a barrier to participation. Always pay incentives promptly and choose incentive amounts fairly for the time and effort required. If your research requires a participant to make a purchase, consider sending a purchase stipend upfront or very promptly after purchase.

## Use language with care

When working with a social identity group you’re unfamiliar with, pre-research is an important step to build understanding and fluency. If you’re not sure of the right terminology to use, allow participants to self-identify and/or do the due diligence to understand the preferred language used by the individuals who are most impacted. Here are a few examples to consider:

* If you're asking for gender, provide options for gender (man, woman, nonbinary, prefer to self-identify) rather than giving options for sex (male and female). ([read more](https://careerfoundry.com/en/blog/ux-design/design-for-every-gender/))
* It’s a good idea to use person-first language to honor a participant’s full humanity (for example, “person with Paraplegia” is person-first language while “Paraplegic” is not). ([read more](https://noti.st/curioresearch/ucoOHl/inclusive-research#sI0iO0W))
* Embrace anti-racist language in study design by, for example, capitalizing the B in Black when discussing identity or replacing the use of “master” with “main” or “global”. ([read more](https://buffer.com/resources/inclusive-language-tech/))

{% hint style="info" %}
**Dscout note:** We reviewed our demographic profile questions in 2021 and updated them to be more inclusive. We will continue to revisit these terms.
{% endhint %}

| Which of the following best describes you? Select all that apply.                                                                                                                                                                                                                                             | Which of the following best describes you?                                                                                     |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| <ul><li>American Indian or Alaska Native</li><li>Asian</li><li>Black or African American</li><li>Hispanic or Latinx</li><li>Native Hawaiian or Other Pacific Islander</li><li>Middle Eastern or North African</li><li>White</li><li>Prefer to self identify (Tap to Type)</li><li>Prefer not to say</li></ul> | <ul><li>Woman</li><li>Non-Binary</li><li>Man</li><li>Prefer not to say</li><li>Prefer to self-identify (tap to type)</li></ul> |

## Allow for self identification

The language around identity is constantly evolving. Allow space for expression in self-identification rather than presuming the identity of your participants.

* For example, some people with deafness consider this a language barrier, not a disability [(read more)](https://dscout.com/people-nerds/lauren-isaacson). If physical or cognitive ability is relevant to your research or recruitment, consider asking “Would you describe yourself as a person with a disability? No / I’m not sure / Yes (tap to type)”. ([read more](https://noti.st/curioresearch/ucoOHl/inclusive-research#sI0iO0W))

{% hint style="info" %}
**Dscout note:** Our customizable tap to type functionality in single and multiple select questions gives scouts a way to self-describe if the listed choices don’t fully or best describe their reality. Our Open-Ended Responses View pulls most-used words from open ended questions into a word bubble, which can be used to help visualize scouts’ language and preferred identification when asked in an open-ended format.
{% endhint %}

## Take special care to avoid microaggressions and microinvalidations

Microaggressions are brief indignities that communicate hostile, derogatory, or negative insults to a person or group. Microinvalidations exclude, negate, or nullify the experiential reality of certain groups. Remember that intentional and unintentional microaggressions and microinvalidations are equally valid and harmful. ([read more](https://uxpamagazine.org/workplace-culture/?))

* For example, if you’re asking participants to share a social identity (whether race, gender identity, etc), be careful with how you phrase categories. Other and Custom can imply that these options were “outside of something” or left out. “Prefer to Self Identify” and “Add Your Own” can be more inclusive and empowering. ([read more](https://dscout.com/people-nerds/4-design-principles-for-gender-identity-inclusion-and-how-to-get-them-implemented)).
* Similarly, when asking questions about identity, multiple-select questions can be more appropriate than single-select which can be limiting and erase elements of a participant’s identity.

{% hint style="info" %}
**Dscout note:** Scouts have the ability to self-identify their gender, provide their pronouns (including a "tap to type" option), and select multiple ethnicities (if applicable) via their Profile.
{% endhint %}

## Be mindful of your method

Consider the needs of your participants as a key input in your choice of methods and always use WCAG 2.0 compliant research tools. Web Content Accessibility Guidelines are a set of recommendations for making content accessible to people with disabilities including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. ([read more](https://noti.st/curioresearch/ucoOHl/inclusive-research#sI0iO0W))

{% hint style="info" %}
**Dscout note:** Dscout's iOS and Android mobile apps, desktop interview sessions, and desktop Diary activities are WCAG 2.0 AA compliant when it comes to the Scout experience (excluding Dscout's Stimuli feature which does not yet support text captions to accompany visual stimuli). We are in the process of continuing to certify other desktop functionality including web screeners and our marketing website (dscout.com).
{% endhint %}

## Recruit on behavior, not identity

When recruiting according to identity, reconsider why identity qualifies a participant for your research. Often, identity classifications simply serve as shortcuts for assumptions about behavioral characteristics.

* For example, If you’re recruiting participants who shop for mens’ pants, recruit people who buy mens’ pants, not people who identify as men.

{% hint style="info" %}
**Dscout note:** Dscout Research Advisors will help to revise questions or communications that could trigger harmful experiences for Scouts. Dscout asks researchers to act with care when recruiting Scouts on the basis of race, gender identity, sexual orientation, ability and religion. Avoid automatically terminating Scouts on the basis of identity.
{% endhint %}

## When writing questions, consider experiences other than your own

Consider how someone with a different life experience might receive your questions and take care to use accessible language. The burden of understanding should be on the researcher not the participant ([read more](https://pdfs.semanticscholar.org/bdd0/5271d897283c6c90dc7ee5522956b05d8b0f.pdf)). Avoid idioms, jargon, acronyms, and metaphors that may be confusing to participants and create barriers for effective communication ([read more](https://buffer.com/resources/inclusive-language-tech/)). Seek out feedback from teammates or formally test your research design through a paid pilot with a few participants.

{% hint style="info" %}
**Dscout note:** Dscout lets you test your studies so you can move through them from a participant's point of view before launching. Invite yourself and other members of your team to test for inclusive questions, wording, and framing.
{% endhint %}

## Recognize unconscious bias and check your assumptions

Research indicates we are drawn toward people who look like us. When selecting participants, recognize and resist this bias and instead, work to recruit a diverse group of participants. As always, bias is an important consideration in research design as well. ([read more)](https://dscout.com/people-nerds/senongo-akpem)

{% hint style="info" %}
**Dscout note:** Check your demographic representation before finalizing your recruit and inviting scouts to a paid study. Use the Closed-Ended Responses View within your screener to see the demographic breakdown of your selected scouts.
{% endhint %}

## Warn participants about potential re-traumatizing experiences

Consider what data you need and how to reduce harm to your participant. If your research could require painful reflection or difficult lines of questioning, be fully transparent in communicating this requirement upfront so participants have the opportunity to decline participation before dedicating any time. Consider designing your research in a flexible way that empowers participants to speak to the experiences they’re comfortable with. Prioritize consent by letting participants know they don’t need to answer questions that may make them feel uncomfortable or upset. Recognize that this might be a person’s first time sharing their story. ([read more)](https://www.onlinemswprograms.com/resources/social-issues/how-to-be-mindful-re-traumatization/)

{% hint style="info" %}
**Dscout note:** Use study instructions and screener teasers to clearly state what will be required of Scouts. If Scouts have the flexibility to opt out of specific questions, be sure to set that expectation within the instructions or question prompt. You can also use checkpoint questions for sensitive communications throughout a study script.
{% endhint %}

## Allow space and time for interview accommodations

Provide clear instructions and schedule with plenty of notice so participants have time to prepare. Consider introducing yourself ahead of the session to give participants the opportunity to request any accommodations they may need.

* For example, you could send the following message such as this: "We're excited to learn from your experiences during our interview on \[DATE]. My name is \[NAME], and I'll be your moderator for this session. It's important that we create an accessible and comfortable virtual space for our conversation, so please let us know if there are any accommodations that we can make ahead of the call."

This resource is just a starting point. We highly recommend clicking through to the links found throughout. These guidelines will evolve as we continue to learn and listen. If you see something harmful or incorrect in the guidelines above, or if you have resources you’d like to share, please reach out to <support@dscout.com>.

## Further Reading

* [Diversity & Inclusion in Design: Why Do They Matter?](https://www.aiga.org/diversity-and-inclusion-in-design-why-do-they-matter) by Antionette Carroll
* [Mismatch: How Inclusion Shapes Design](https://www.youtube.com/watch?v=SYu6wnZhrBU) by Kat Homes
* [Inclusive Research](https://noti.st/curioresearch/ucoOHl/inclusive-research#sI0iO0W) presentation by Lauren Isaacson
* [How white is your UX practice?: inclusion and diversity in critical UX research](https://pdfs.semanticscholar.org/bdd0/5271d897283c6c90dc7ee5522956b05d8b0f.pdf) by Karine Larose and Simon Barron
* [How to begin designing for diversity](https://thecreativeindependent.com/guides/how-to-begin-designing-for-diversity/) by Boyuan Gao and Jahan Mantin
* [How Technology Perpetuates Racism by Design](https://www.technologyreview.com/2020/06/03/1002589/technology-perpetuates-racism-by-design-simulmatics-charlton-mcilwain) by Charlton McIlwain
* [Workplace Culture + Microaggressions in Tech](https://uxpamagazine.org/workplace-culture/?) by Shanae Ullman

## Further Reading from Dscout

* [Inclusive and Accessible UX: A Starter Syllabus](https://dscout.com/people-nerds/inclusive-and-accessible-ux-a-starter-syllabus) by Tony Ho Tran
* [4 Design Principles for Gender-Identity Inclusion (and How to Get Them Implemented)](https://dscout.com/people-nerds/4-design-principles-for-gender-identity-inclusion-and-how-to-get-them-implemented) by Jess Mons and Lindsey Brinkworth
* [Why (and How) to Pay Attention to Accessibility in Design](https://dscout.com/people-nerds/lauren-isaacson) interview with Lauren Isaacson by Tony Ho Tran
* [How We Empathize in UX Matters](https://dscout.com/people-nerds/how-we-empathize-in-ux) interview with Alba Villamil by Tony Ho Tran
* [Design in Three Dimensions](https://dscout.com/people-nerds/inclusive-design-jutta-trevianus) interview with Jutta Treviranus by Carrie Niell
* [Good Design is Cross-Cultural](https://dscout.com/people-nerds/senongo-akpem) interview with Senongo Akpem by Tony Ho Tran
* [4 Thoughtful Principles for Service-Minded UXR](https://dscout.com/people-nerds/ux-that-serves) interview with Taranamol Kaur, Nate Mahoney, and Aditi Rao by Tony Ho Tran
* [How to Redesign for Justice](https://dscout.com/people-nerds/how-to-redesign-for-justice) interview with Antionette Carroll


# Custom informed consent

<table><thead><tr><th>Plan</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Core</strong></td><td>false</td></tr><tr><td><strong>Plus</strong></td><td>true</td></tr><tr><td><strong>Select</strong></td><td>true</td></tr><tr><td><strong>Enterprise</strong></td><td>true</td></tr></tbody></table>

Before you can add custom informed consent to individual studies, the documentation must be added to your organization’s Dscout account. You’ll work with your Dscout account manager or research advisor to get the necessary documents approved and uploaded.

{% hint style="info" %}
**Note:** Any required consent forms must be uploaded to Dscout before you launch your study, and this process can take 3–5 days to complete. Keep this in mind when planning your research.
{% endhint %}

## Upload custom informed consent

**To upload custom informed consent, provide a copy to your Dscout account manager or research advisor. This copy of your informed consent must:**

* Be in an editable format. For example, a .docx file. **PDFs are not accepted.**
* Offer full transparency to what you are requesting of participants and how you will use their personal information.
* Include a signature block where participants can e-sign.
* Include the following language:\
  \
  *Any terms you agree to between you and \[researcher’s organization’s name] as part of this Study will supplement, but will not supersede, the Dscout Scout Terms and Conditions and Scout Privacy Policy, both available at* [*dscout.com/legal/scout-terms*](http://dscout.com/legal/scout-terms)*, to which you have previously agreed and remain subject.*

{% hint style="success" %}
**Tip:** If you need help drafting an informed consent, see this [user research agreement template](https://uxdesign.cc/user-research-participation-agreement-dd1c573c03c3) for guidance. Dscout is not able to offer help directly as informed consent is a legal document between you and your participants.
{% endhint %}

Once your account team has the document, Dscout’s Legal team will review it within 3–5 business days and notify you of any changes that must be made. Once the document is finalized, it will be uploaded to your Dscout account where you can add it to the necessary studies.

For information on adding your consent forms to individual studies, see the following articles:

* [Add informed consent to a media survey](/media-surveys/create-a-media-survey/add-informed-consent-to-a-media-survey).
* [Add informed consent to a usability test](/usability-tests/create-a-usability-test/add-informed-consent-to-a-usability-test).
* [Add informed consent to an intercept study](/intercept-studies/create-an-intercept-study/add-informed-consent-to-an-intercept-study).
* [Add informed consent to a diary study](/diary-studies/manage-a-diary-study/add-informed-consent-to-a-diary-study).
* [Add informed consent to an interview study](/interview-studies/create-an-interview-study/add-informed-consent-to-an-interview-study).

## Verify participant consent

**Participants can’t accept studies without signing your informed consent documents. So, if you see a response from a participant, rest assured that they have given their consent to participate.**

When participants sign informed consent documents, they provide us with personal information which is our obligation to keep secure. **So, we do not share any participant-signed documents back with you.**

Dscout securely stores and maintains the informed consent documents indefinitely. If you have reason to believe that a participant has violated any terms as described in your informed consent documents, we will work with you to address the issue. Reach out to your Dscout account manager or research advisor with any concerns.


# International research with Dscout

Dscout lets you conduct international research so you can hear directly from the people who matter most to your work.

The Dscout app works for participants in most countries as long as they're using a device that meets our [minimum device requirements](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196) and have a network connection. And in some cases, you'll be able to screen from Dscout's own scout pool to meet or supplement an international recruit.

Dscout's primary support team is US-based, English speaking, and available from 9-5 CST. Reach out to <sales@dscout.com> if you have questions about doing international research.

Just keep in mind that you, a colleague, or a hired translator will need to be able to write instructions, questions, read replies, and offer support in whatever language you'll be conducting research in. And as you'd imagine, recruiting and managing scouts who speak different languages and live in different times zones requires careful planning to ensure your expectations are met.

## Available countries

The countries in which you can run Dscout studies depend on how you recruit participants.

**Bring your own participants:** If you recruit and invite participants yourself, the Dscout app works in most countries, as long as each participant's device meets our [minimum device requirements](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196) and has a network connection.

**Dscout's Scout Panel:** When recruiting from Dscout's proprietary panel, you can target participants in:

* United States
* United Kingdom
* International (participants located outside the United States and United Kingdom)

{% hint style="info" %}
**Note:** Additional countries may be available for recruitment using the Dscout Scout Panel in coordination with your Dscout Research Advisor. These countries include: Australia, Brazil, Canada, France, Germany, India, Italy, Japan, New Zealand, South Africa, South Korea, and Spain. Contact your Research Advisor for help recruiting from these countries.
{% endhint %}

**Partner Panels:** To reach participants through Dscout's Partner Panels, see [Partner Panels](/recruit-participants/partner-panels) for the full list of available countries.

## Dscout languages

In addition to English, the Dscout app is localized for participants in:

* German (Deutsche)
* Spanish (Español)
* French (Français)
* Japanese (日本語)
* Simplified Chinese (中文)
* Korean (한국어)
* Brazilian Portuguese (Português)
* Italian (Italiano)

{% hint style="info" %}
**Note:** Additional languages are available when conducting AI moderated studies. For more information, see [AI moderated studies](/dscout-ai/dscout-ai-studio/ai-moderated-studies).
{% endhint %}

This means that if your participants have their phones set to one of the above languages, then all the hard-coded text in the Dscout app will automatically be displayed in your participants' native language! (If they have their phone set to a language other than those listed above, Dscout will default to English.)

In the example below, you'll see that all hard-coded text (like button copy) is in Spanish, but the dynamic text is still in English. To have the dynamic text be in Spanish too, the researchers in charge of this project would just need to write titles, instructions, and questions in Spanish.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/UD1YzFln9bu6zXLh4i7i/360048843772)

To have the static, hard-coded text in the invite emails and in-app push notifications that you send your study participants set to a specific language, just select the one you'd like to use from the dropdown menu in the Dscout study builder by expanding the "Specs" menu, then adjusting the language field. Just remember that if you want the dynamic, body text of your emails to ALSO be in a different language, you have to actually write in that language.

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/udOFT9DJv3lGg4C8orXW/360048973431" alt="" width="563">

{% hint style="info" %}
**Note:** Hard-coded web content in desktop diary studies and diary webpages is translated. At this time, hard-coded web content in desktop interview sessions is not translated.
{% endhint %}


# Collaborate in Dscout

Use these guides to work with teammates inside projects and studies. Start here for collaborator access, comments, and mentions.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Manage project collaborators</td><td><a href="/getting-started/collaborate-in-dscout/manage-project-collaborators">Manage project collaborators</a></td></tr><tr><td>Builder comments</td><td><a href="/getting-started/collaborate-in-dscout/builder-comments">Builder comments</a></td></tr><tr><td>Mentions in Dscout</td><td><a href="/getting-started/collaborate-in-dscout/mentions-in-dscout">Mentions in Dscout</a></td></tr></tbody></table>


# Manage project collaborators

Research doesn’t happen in a silo—and neither does working in Dscout. Add collaborators to your project so your team can recruit participants, build studies, and analyze results together.

{% hint style="info" %}
Some accounts restrict user management permissions to Account Owners and Admins. If you're unable to add collaborators (viewers or otherwise) for any reason, contact your Dscout Account Owner or one of your Dscout Admins for help.
{% endhint %}

## Add collaborators to a project

Once you’ve created a project, invite a few of your colleagues so you can work on your research together.

{% stepper %}
{% step %}
Navigate to the project where you want to invite collaborators.
{% endstep %}

{% step %}
Click the list of collaborators in the top-right corner of the page. The **Add project collaborators** modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/wnZTXcsxOuOmtL4LgfBt/39583985507476)
{% endstep %}

{% step %}
Enter your collaborator’s **name** or **email address** in the search bar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/3lYeEdyYbtkAmyq9RZdD/39583985512212)

{% hint style="info" %}
Members of your Dscout account will appear as you type. To invite someone else, enter their entire email address, then click **Select user**. Keep in mind that these users will be granted **Viewer** access to the project. For more information on user roles, see [User roles in Dscout](/getting-started/dscout-quickstart-guide/user-roles-and-permissions).
{% endhint %}
{% endstep %}

{% step %}
Select the people you want to invite. Make note of their user roles on the right of the modal to understand what permissions they’ll have in your project.
{% endstep %}

{% step %}
Click the **Add to project** button.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6qasUuXupibr1CYMVC8s/39584045806868)
{% endstep %}
{% endstepper %}

Now you’ve got some company in your project! Email invitations will be sent to your selected users and you’ll see them listed in the **Add project collaborators** modal. Revisit this modal at any time to add more collaborators.

## Resend a collaborator’s invitation

It’s easy for our inboxes to become cluttered. If you’ve invited a collaborator but they can’t find the invitation, you can share the link with them manually.

{% stepper %}
{% step %}
Click the list of collaborators in the top-right corner of your project. The **Add project collaborators** modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/wnZTXcsxOuOmtL4LgfBt/39583985507476)
{% endstep %}

{% step %}
Find the relevant user in the list.
{% endstep %}

{% step %}
In that user’s row, click **Copy** in the **Project link** column. The link is copied to your clipboard.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/NCKPdVw29MQ358fT6IUE/39583985516052)
{% endstep %}

{% step %}
Send the link directly to your collaborator.
{% endstep %}
{% endstepper %}

When they visit the link, your collaborator will be prompted to log in to Dscout and then brought directly to your project.

## Delete collaborators from a project

If a collaborator no longer needs access to your project, you can remove them.

{% stepper %}
{% step %}
Click the list of collaborators in the top-right corner of your project. The **Add project collaborators** modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/wnZTXcsxOuOmtL4LgfBt/39583985507476)
{% endstep %}

{% step %}
Find the relevant user in the list.
{% endstep %}

{% step %}
In that user’s row, click the **Delete** icon.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/T3lnNAr74gh93K5Re5ys/39584045811092)
{% endstep %}
{% endstepper %}

Now, that collaborator is removed from your project and will no longer have access. If you need to re-add them, follow the steps above.


# Builder comments

Comments let you leave feedback directly on a screener or study. You can attach comments to specific questions, mention your collaborators directly, and mark comments as requiring a resolution before the study can be launched.

You can access a screener or study’s comments by clicking the **Comments (speech bubble)** icon at the top of the builder:

{% hint style="info" %}
In diary studies, click **Comments** (no icon) at the top of the builder.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aGUik9x4ry5ByDsruADX/48535144379540)

If a specific question has comments, you’ll see a yellow icon with the number of comments on the question itself. Click this icon to view the question’s comments:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ctXZRN9bhdOJ0dxsFfwe/48535144384404)

## Add a comment

When leaving comments, you can leave them on the study generally or attach them to specific questions. You can also tag collaborators to ensure they see your notes. Tagged collaborators receive an email notification letting them know you mentioned them.

{% stepper %}
{% step %}
Click the **Comments (speech bubble)** icon at the top of the builder. All unresolved comments are displayed.

{% hint style="info" %}
In diary studies, click **Comments** (no icon) at the top of the builder.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aGUik9x4ry5ByDsruADX/48535144379540)
{% endstep %}

{% step %}
Click **+ New comment** at the bottom of the comments sidebar. A text box is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ZlA31JhCrB07q838kOMo/48535144393364)
{% endstep %}

{% step %}
Type your comment in the text box.
{% endstep %}

{% step %}
(Optional) Select **Must be resolved to launch** if your comment requires action before the screener or study may be launched.

{% hint style="info" %}
If the screener or study has already been launched, this setting will be disabled.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/q603zPBH3NhNLMHnLCJf/48535096615188)
{% endstep %}

{% step %}
(Optional) Type **@** followed by a collaborator’s name to mention them in the comment.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1q4WAzBlZQ9MJ2I0spRs/48535096619156)
{% endstep %}

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

Now, your comment is added to the study. If you selected **Must be resolved to launch**, the screener or study cannot be launched until the comment is resolved. (For more information, see [Resolve a comment](#h_01KPXH5DCH12QWA73BTVY124YG).) If you mentioned a collaborator, they’ll receive an email notification letting them know.

To add a comment to a specific question, hover over the question and click the **Comments (speech bubble)** icon:

{% hint style="success" %}
In diary studies, you can highlight specific question text and comment directly on it.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ctXZRN9bhdOJ0dxsFfwe/48535144384404)

## Resolve a comment

Once a comment has been addressed, you can resolve it. Some questions may be marked as **Must be resolved to launch**. Those questions *must* be marked as “resolved” directly in the builder before the screener or study can be launched.

{% stepper %}
{% step %}
Locate the comment in your screener or study.
{% endstep %}

{% step %}
Click the **checkmark** icon in the top right corner of the comment.

{% hint style="info" %}
Only the original comment in a thread contains this checkmark icon. If you don’t see it, make sure you’re looking at the top comment, not a reply. In diary studies, you'll see the word **Resolve** instead of an icon.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ZQs8p7ObrfP6v0suOITr/48535096624276)
{% endstep %}
{% endstepper %}

Now, the comment is marked as resolved. You can view any previously resolved comments by applying the **Resolved** filter in the comments sidebar. For more information, see [Filter comments](#filter-comments).

## Reply to a comment

If you’ve been mentioned in a comment (or feel like chiming in anyway!), you can reply to start a thread.

{% hint style="info" %}
Notifications are only sent if you mention a collaborator directly using **@** followed by the collaborator’s name. They will not receive a notification for replies to their comments alone.
{% endhint %}

{% stepper %}
{% step %}
Locate the comment you want to reply to.
{% endstep %}

{% step %}
Click **Reply**. A text box is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7YkPEZo3uGwz6Sj6eqdi/48535096628372)
{% endstep %}

{% step %}
Type your response.
{% endstep %}

{% step %}
(Optional) Type **@** followed by a collaborator’s name to mention them in the comment.
{% endstep %}

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

Now, your reply is posted. Anyone you mentioned will receive an email notification. You can edit or delete your replies on unresolved comments, too. For more information, see [Edit a comment](#edit-a-comment) or [Delete a comment](#delete-a-comment).

## Filter comments

When viewing comments, you may wish to filter them to find those relevant to you. Comments have the following filter options:

* **Unresolved:** Displays only comments that have not been resolved. This filter is applied by default.
* **Mentions:** Displays only comments that you have been mentioned in.
* **Must be resolved:** Displays only comments that require attention prior to launching the screener or study.
* **Resolved:** Displays only comments that have already been resolved.

Comment filters can be accessed by clicking the drop-down at the top of the comments sidebar:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Gvbgu05J3X0fDczkdWI3/48535144404628)

## Edit a comment

If you want to modify a comment you’ve already left on a screener or study, you can do so. You can edit the comment itself, add collaborator mentions, and change whether a comment must be resolved or not prior to launch.

{% hint style="info" %}
Resolved comments cannot be edited. Additionally, you can only edit comments you’ve left, not comments left by your collaborators.
{% endhint %}

{% stepper %}
{% step %}
Locate the comment in your screener or study.
{% endstep %}

{% step %}
Click the three-dot icon in the top right corner of the comment.
{% endstep %}

{% step %}
Click **Edit**. A text box is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/I5J24f3xxc0xvqhZAGbp/48535144414612)
{% endstep %}

{% step %}
Make the required edits.
{% endstep %}

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

Now, the edits to your comment are saved. Any new collaborators you’ve mentioned will receive an email notification.

## Delete a comment

If a comment is no longer needed, you can delete it.

{% hint style="info" %}
Resolved comments cannot be deleted, nor can comments with replies. Additionally, you can only delete comments you’ve left, not comments left by your collaborators.
{% endhint %}

{% stepper %}
{% step %}
Locate the comment in your screener or study.
{% endstep %}

{% step %}
Click the three-dot icon in the top right corner of the comment.
{% endstep %}

{% step %}
Click **Delete**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/kzqE5l35aeaqrghIdVLv/48535144416660)
{% endstep %}
{% endstepper %}

Now, your comment is deleted.


# Mentions in Dscout

Mentions can be used to tag in your colleagues or Dscout Research Advisor team in notes + comments to share interesting data, start a conversation, or collaborate on your research design.

{% hint style="info" %}
**Don't see the ability to @ mention a colleague?** At this time, Mentions are only available for subscription accounts. Chat with your Account Manager to learn more!
{% endhint %}

## Mentioning a project collaborator

Use @ mentions in Dscout to tag your colleagues in screener, entry, or interview session notes.

1. Click into an individual application, entry, or interview session.
2. Click into the “Notes” tab on the righthand sidebar.
3. Begin typing “@” and your collaborator’s first name, last name, or username. As you type, a dropdown list will appear with matching collaborators to select from. Collaborators are mentioned by their username.
4. To mention all project collaborators in a note, type “@collaborators” or “@collab” in the Notes field.

As a reminder, **notes are only visible to other researchers, not to scouts**. No scouts will ever see notes or mentions between researchers!

### Diary studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/0iWdB4F0B8EklZssOads/360048982452)

### Screeners, usability tests, and media surveys

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/KBu2I4dUCdmUDm3aYfil/21741859679252)

### Interview studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1NguwdLGJOVt0IeVRIhB/21741864957588)

## Mentioning a Dscout Research Advisor

When you [submit a screener or study for review](/study-basics/design-a-study/optional-pre-launch-review-for-screeners-and-studies), your Dscout Research Advisor will collaborate with you via comments + mentions. Utilize @ mentions to call your Dscout Research Advisor's attention to anything you'd like their input on.

1. [Create a comment](/getting-started/collaborate-in-dscout/builder-comments) in the Builder section of your study or screener
2. Type “@” followed by the name of your Research Advisor
3. Select their name to notify them of your comment

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7nW7jK5JXteDTGR7iRlV/21741864963476)

## Receiving notification of mentions

Whenever you’re mentioned, you’ll receive an email notification. Email notifications include the note text and a direct link into the relevant application, entry or session in Dscout.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/AqFvvgSNS7xk7yCKefef/360049112071)

## Changing your username

When you create your account, Dscout will automatically create a username for you. It’ll be something like *firstnamelastname*—it may also have a number at the end. This username is only used for other researchers to mention you in notes—it’s **not** used for logging in (you’ll still log in with your email address).

If you’d like to change your username, navigate to your Dscout Profile settings by clicking your profile picture in the top-right corner, then selecting “Profile.”

Write your desired username in the Username field, then click “Update Profile” to save. You can change your username to any name that is not taken. Usernames must be at least 3 characters and can only contain letters and numbers.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/EFVxqsNDL3GCYhRgeEmB/360048982472)


# Question types

Learn about the question types and question-building features available in Dscout studies.

Use the links below to go deeper on each topic.

* [Ranking questions](/study-basics/question-types/ranking-questions)
* [Task questions](/study-basics/question-types/task-questions)
* [Card sort questions](/study-basics/question-types/card-sort-questions)
* [Screen recording guide for researchers](/study-basics/question-types/screen-recording-guide-for-researchers)
* [Question banks](/study-basics/question-types/question-banks)
* [Question groups](/study-basics/question-types/question-groups)
* [Multi variate testing](/study-basics/question-types/multi-variate-testing)
* [Using question quotas](/study-basics/question-types/using-question-quotas)
* [Question stimuli](/study-basics/question-types/question-stimuli)
* [Tree testing questions](/study-basics/question-types/tree-testing-questions)


# Ranking questions

When included in a screener, single-session study, or diary study, ranking questions ask scouts to compare a list of answer options to each other by placing them in order of preference. Scouts will assign some or all of the answer options a number, depending on whether you've asked them to rank all choices or defined a custom rank limit. In your question prompt, **be sure to instruct scouts on what the numbers mean** *(e.g. Rank the following pizza toppings from best **(1)** to worst **(6)**).*

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cLUUTXLs5jjgIkA69fPd/360085488852)

## Creating a ranking question

To create a ranking question, select "Ranking" from the question dropdown menu:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/94JxUZNHopy1MUh7dI0a/30874375706644)

Once created, you can decide whether or not you’d like scouts to rank *all* of the answer options listed, or you can create a custom limit to allow scouts to rank only *some* of your answer options.

* **When to use Rank All**: Use Rank All when scouts have enough experience with all of your answer options to assign a thoughtful rating to each *(e.g. Rank your favorite colors from most favorite (1) to least favorite (6)).*
* **When to use Custom Limit:** Use Custom Limit when you’d like scouts to rank their top answer options *(e.g. Rank your top three favorite pizza toppings from most favorite (1) to least favorite (3)).*

***Pro tip:*** Try to limit the number of rank choices to between 6 and 10 items. Asking scouts to rank too many items in relation to one another can be overwhelming, and in a long list of items, the middle rankings tend to be less strong or reliable.

**Screeners & single-session studies:**

"Rank all" is the default setting. To customize the minimum/maximum number of choices, enable "Rank only some choices" and adjust the settings.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1qRXtW5BA7o37acezoCu/30874375718164)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/K5WHJ4UQKx7gaqEGCL6F/30874375724820)

**Diary studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Bz6rbU9TPhCW6JoWx2AF/21717532375828) ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/h9EaIkTW57Yupyf9REhB/21717532383252)

## Customizing your ranking question

You can further customize your ranking question with the following options.

**Screeners & single-session studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/wTWl9Z1fs6mAo1CkPp44/30874347090324)

**Diary studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/bsIhEPoYAj300LNt54ZG/21717556109972)

“**Randomize rank choices**” to present rank choice answer options in a random order to scouts.

“**Include ‘Other’ Option**” to allow scouts to fill in their own answer choice for ranking.

For **Rank All** questions, toggle on **“Scouts can mark rank options as N/A”** to allow scouts to mark any rank choice answer options that are not relevant or familiar to them as “not applicable.” (This option is not available for “Custom Limit” ranking questions.)

## Analyzing Ranking Question Results

In the “Closed-Ended Responses” view, you can see a visualization of your ranking question data as a distribution chart or as a table. A score (based on average ranking) is calculated for each answer option, allowing you to quickly evaluate the most preferred answer option.

(To access the “Closed-Ended Responses” view, use the “Entries” menu dropdown in the header, or click the bar chart icon in the top left corner of the Entries view.)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JxoX6cauN9eNOIbZq9hR/360089909192)

## **Overall Rank and Score**

Overall rank is based on the score calculation. Score is a weighted average that is calculated as follows, where:

*w* = weight of ranked position\
\&#xNAN;*x* = response count for answer choice

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dJSdpaOrrhP7tDu1Dow1/360084996932)

Weights are applied in reverse. In other words, the scout’s most preferred choice (ranked as #1) has the largest weight, and their least preferred choice (ranked in the last position) has a weight of 1. For example, if a ranking question had 5 possible rank assignments:

* The #1 choice has a weight of 5
* The #2 choice has a weight 4
* The #3 choice has a weight of 3
* The #4 choice has a weight of 2
* The #5 choice has a weight of 1

If you choose to toggle on the “Scouts can mark rank options as N/A” option for a Rank All ranking question, any N/A responses will not factor into the average ranking.

The overall rank is based on the weighted average score, meaning the answer choice with the highest score is “1” in the Overall column, second highest is “2”, etc.

## **Viewing Ranking Question Responses in Scout Entries**

When viewing ranking question responses in individual scout entries or applications, the scout’s choices will be listed in order of assigned preference.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rAEZ4FPA3LP5AYQsLqRN/360085118791)


# Task questions

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

Task questions ask participants to complete an action using a live website, prototype, or app. Maybe you want to see how easily users can find a specific page or how intuitive your newly designed search functionality is. With task questions, you can find out directly from your participants.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5ZJV1RO9auDqDc2GrtWj/37450804811284)

When building a task question, you can add as much (or as little!) guidance as you want depending on what you’re trying to learn. You can also add URLs that will take participants directly to the website or prototype where you want them to complete the task.

Task question usage varies depending on your study’s device type:

| Desktop studies                                                                                                                  | Mobile studie                                                                                                                                                                                                   |
| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Up to 15 task questions with no duration limit.</li><li>Capture face, screen, and audio during task questions.</li></ul> | <ul><li>Up to 15 task questions with a total recording time of 40 minutes. After 40 minutes, recording ends—even if the participant hasn’t finished the study.</li><li>Capture screen and audio only.</li></ul> |

{% hint style="info" %}
Keep the duration of your test in mind when adding task questions. Participants can feel fatigued in just 15 minutes during unmoderated testing. Staying focused on your research goals will help your participants but it will also help you when it comes time to analyze.
{% endhint %}

## Task question settings

When adding a task question to your study, you’ll customize your question in the center of the builder:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/iRp0AzhNrhrOBj4UbDYi/41981606650772)

Here’s a breakdown of each option:

| Setting                            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Task**                           | <p>The prompt or instructions participants see as part of this task. Here, enter guidance they should follow or any context they should know before beginning the task. For example, if they should complete the task using your company’s app, you should tell them that here.<br><br>You can format your text in the following ways:<br><br>- <em><code>bold</code></em> = <strong>bold</strong><br>- <em><code>italic</code></em> = <em>italic</em><br>- <code><[https://examplelink.com>](https://help.dscout.com/study-basics/question-types/https:/examplelink.com>)</code> = <a href="https://examplelink.com/"><https://examplelink.com></a><br>- <a href="https://examplelink.com"><code>Sample link</code></a> = <a href="https://examplelink.com/">Sample link</a><br><br>However, only include links here that are supplementary. To link participants to a specific page or prototype related to the task, enter that under <strong>Task URL</strong>.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> For inspiration writing task questions, see <a href="https://dscout.com/people-nerds/usability-for-newbies-task-writing-pro">Become a Task Writing Pro</a> from Dscout’s People Nerds.</p></div>                           |
| **Task URL** (optional)            | <p>A link to the website or prototype where participants should complete this task. This URL will open automatically when participants reach this task and will automatically close when they finish the task. (To stop displaying the URL after the task question, see <strong>Close task URL</strong> in the table below.)</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> If you're using a Figma Make prototype, first <a href="https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app">publish</a> your prototype in Figma Make. Then, add the provided URL as a <strong>Website</strong> to your task question. Heat maps are not generated for Figma Make prototypes.<br></p></div><p>For more details on configuring a Figma prototype in Dscout, see <a href="/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study">Add a Figma prototype to a study</a>.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> Try managing your task URLs from at the study level rather than on a question-by-question basis. For more information, see <a href="#manage-task-urls">Task URLs</a>.</p></div> |
| **Set success URL** (website only) | <p>The URL participants should land on when successfully completing the task. Dscout will report success for this task during analysis based on whether participants visit the URL entered here.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> Use an asterisk (<em>) to create a wildcard URL if the place where participants land upon completion can vary. For example, <strong><https://www.sneakers.com/running/></strong></em> will consider any URL beginning with <strong><https://www.sneakers.com/running/></strong> a success regardless of what else is in the URL.</p></div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| **Task flow** (prototype only)     | <p>Defines where participants should start and end the task in your Figma prototype. This is useful if you are using the same prototype for multiple tasks because it lets you override the default start screen set by Figma.<br><br>Hover over the following and click <strong>Edit</strong> to make your selections:<br><br><strong>Starting screen:</strong> Where participants will be directed when the task begins.<br><br><strong>Success screen (optional):</strong> Where you expect participants to end upon successful completion. Dscout will report success for this task during analysis based on whether participants land on the screen chosen here.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

Task questions also offer options related to follow-ups, task URLs, and privacy. You’ll access these in the right sidebar:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/hGQfcPSbPrITfo7GLj7U/41981606654100)

Here’s a breakdown of each option:

| Setting                                   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Self-reported completion** (optional)   | <p>Adds an additional follow-up question to your study immediately after the task asking participants if they successfully completed the task.<br><br>When enabled, participants will see a <strong>Yes</strong> or <strong>No</strong> question asking if they were able to complete the task. In analysis, you’ll see a percentage completion rate.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Single Ease Question (SEQ)** (optional) | <p>Adds an additional follow-up question to your study immediately after the task asking participants how easy or difficult they found the task.<br><br>When enabled, participants will see a scale question asking them how they felt about the task, with options ranging from <strong>1 - Very difficult</strong> to <strong>7 - Very easy</strong>. In analysis, you’ll see an effort rating distribution for this task.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **SEQ Difficulty** (optional)             | <p>Adds an additional follow-up question to your study immediately after the Single Ease follow-up asking participants to explain why they found the task difficult.<br><br>When enabled, participants who rate task difficulty 1, 2, 3, or 4 will see an open-ended typed response question asking them to elaborate.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| **Close task URL** (optional)             | <p>Stops displaying the provided task URL after participants complete this task question. <strong>By default, URLs remain open after participants complete a task.</strong><br><br>When enabled, the following behavior applies for each device and recording type:</p><ul><li><strong>Desktop:</strong> After the task is complete, <em>all</em> non-Dscout tabs are closed.</li><li><strong>Mobile (in-app recording):</strong> After the task is complete, the Experience tab where the URL was accessible closes so participants can’t revisit it.</li><li><strong>Mobile (external recording):</strong> A banner is displayed asking participants to exit the linked URL or prototype.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Close task URL is enabled by default on task questions added to multi-variate sets. For more information, see <a href="/study-basics/question-types/multi-variate-testing">Multi-variate testing</a>.</p></div> |
| **Privacy blur** (optional)               | <p>Blurs the participant’s screen during the task. This protects participants’ personally identifiable information (PII) during studies.<br><br>When enabled, participant audio is recorded during the task, but their screen will not be visible to you during analysis.<br><br>For more information, see <a href="/study-basics/testing-prototypes/privacy-blur">Privacy blur</a>.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |

## Add a task question to a study

You’ll add task questions on the **Usability test/Study** tab of your study.

{% stepper %}
{% step %}
Navigate to the **Usability test/Study** tab of your study.
{% endstep %}

{% step %}
Click **+ Add** in the center of the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/IwFB8yAzZJ3GIVOsWpFa/37450774951956)
{% endstep %}

{% step %}
Under **Usability**, select **Task**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/UzZyeA1WMi9qFZqPNBO9/37450801448852)
{% endstep %}

{% step %}
Enter the **Task** prompt or instructions.
{% endstep %}

{% step %}
(Optional) Click **Add** beside **Task URL** to add a website or prototype. The applicable fields will display. For help completing these fields, see [Task question settings](#h_01JV2PPCB1PY0YQMVSQE50SCCT).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cemy59SfyQn9r862TlqN/37450774953620)
{% endstep %}

{% step %}
Enable power follow-ups, close task URL, or privacy blur in the right sidebar. For more information on each, see [Task question settings](#task-question-settings).

{% hint style="success" %}
**Tip:** Remember to enable **Close task URL** if you want the website or prototype to close after this task question.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/hGQfcPSbPrITfo7GLj7U/41981606654100)
{% endstep %}

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

Now, you’ve successfully added a task question to your study. When participants reach this question, they’ll see the provided instructions for the task. And if you’ve included a URL or prototype, it will open for participants automatically when they begin the task.

## Manage task URLs

Your study might use a number of task URLs, some of which might apply to multiple task questions. While you can manage URLs from within each task question, you can also manage them at the study level. Click the **Task URLs** button at the top of the builder to access all URLs included in your study:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/nU736aKSxpeu0X0g0531/37450778260756)

Here, you can add, refresh, and delete URLs as needed:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/enXGYin3rK5KxtOtMvpG/41981606655380)

## Analyze a task question

From the **Responses** tab of a study, you can access specific metrics for each task question in your study:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aHAkb5IbpbjYskPP5k0L/37450804840596)

Here, you’ll find the following details:

| Metric                       | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Success**                  | Percentage of participants who reached your designated success URL or prototype success screen. (Only visible if a **Success URL** or **Success screen** is set when building your study.)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Self-reported completion** | Percentage of participants who indicated they successfully completed the task. (Only visible if the **Self-reported completion** follow-up question is enabled when building your study.)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| **Average time on task**     | <p>Average response time for the task. Here, you can also hover over the box plot to see the following statistics:</p><ul><li><strong>Min:</strong> The shortest amount of time it took for a participant to complete the task.</li><li><strong>Q1:</strong> The lower quartile of response times. 25% of participants took less time than this to complete the task.</li><li><strong>Median:</strong> The exact mid-point of response times for the task.</li><li><strong>Q3:</strong> The upper quartile of response times. 75% of participants took less time than this to complete the task.</li><li><strong>Max:</strong> The longest amount of time it took for a participant to complete the task.</li><li><strong>Mean:</strong> The average amount of time it took participants to complete the task.</li><li><strong>Outliers:</strong> Data points significantly above or below the rest of responses.</li></ul> |
| **Average ease rating**      | Average of how participants rated the effort required by the task. (Only visible if the **Single-Ease Question** follow-up is enabled when building your study.)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |

To view details from individual responses, navigate to the **Participants** view while on the **Responses** tab of your study.


# Card sort questions

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

Card sort questions ask participants to organize a set of cards into categories. This data helps you understand how people mentally group and relate concepts, which makes it valuable for information architecture research, navigation testing, and content organization studies.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/btLhJm2m9LfBQVN5ur6g/47423062919316)

When adding a card sort question, you have three options to choose from:

* **Closed:** Participants sort cards into researcher-defined categories only. Best for validating an existing categorical structure.
* **Open:** Participants create their own categories from scratch. Best for discovering how people naturally organize items. (Desktop studies only.)
* **Hybrid card sort:** Researchers provide starting categories, but participants can add their own. Best for iterative refinement when some structure exists but you want to surface gaps. (Desktop studies only.)

Regardless of your choice, participants must sort all cards before submitting their response.

## Card sort question settings

When adding a card sort question to your study, you’ll customize your question in the center of the builder:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/tkTsEA87vfTL40eK9GDy/47423062924308)

Here's a breakdown of each option:

| Setting        | Description                                                                                                                                                                                                                                                                                                                                                                                 |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Prompt**     | <p>The instructions shown to participants before they begin the card sort.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> No need to include instructions on navigating the card sort itself—we'll instruct them automatically.</p></div>                                                                             |
| **Cards**      | <p>The individual items participants will sort.<br><br>Each question can have a maximum of 100 cards. Each card has a maximum character limit of 50.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> For mobile studies, we recommend a maximum of 15 cards and eight categories.</p></div>                            |
| **Categories** | <p>The groups participants sort cards into. The following limits apply to your selected type of card sort:<br><br>- <strong>Closed:</strong> 2–30 categories.<br>- <strong>Open:</strong> No categories (participants will create their own with a maximum of 100 categories).<br>- <strong>Hybrid:</strong> 1–30 categories.<br><br>Each category has a maximum character limit of 50.</p> |

You'll access additional settings for card sort questions in the right sidebar:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/HZ74i8eVBgAhxAGtirdS/47423062929044)

Here's a breakdown of each option:

| Setting                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Card sort type**                                                    | <p>The type of card sort you want participants to complete. Choose from the following options:</p><ul><li><strong>Closed:</strong> Participants sort cards into researcher-defined categories only. Best for validating an existing categorical structure.</li><li><strong>Open:</strong> Participants create their own categories from scratch. Best for discovering how people naturally organize items. (Desktop studies only.)</li><li><strong>Hybrid card sort:</strong> Researchers provide starting categories, but participants can add their own. Best for iterative refinement when some structure exists but you want to surface gaps. (Desktop studies only.)</li></ul> |
| **Randomize card order**                                              | When enabled, cards are presented in a random order to each participant.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| **Randomize your category order** (closed and hybrid card sorts only) | When enabled, categories are presented in a random order to each participant.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |

## Add a card sort question to a study

You’ll add card sort questions on the **Usability test/Media survey/Study** tab of your study.

{% stepper %}
{% step %}
Navigate to the **Usability test/Media survey/Study** tab of your study.
{% endstep %}

{% step %}
Click **+ Add** in the center of the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/AQa1rFek9InfYgmMaWTp/47423062932884)
{% endstep %}

{% step %}
Under **Standard**, select **Card sort**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/3xCxEJ6Z9SY43Hz25GWO/47423126725780)
{% endstep %}

{% step %}
Enter the **Prompt** (instructions) you want to display to participants before they begin the card sort.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ixU1e3yKskCuoJWo3yPk/47423062938132)
{% endstep %}

{% step %}
Select your **card sort type** in the right sidebar. You can choose **Closed**, **Open**, or **Hybrid**. See the table above for more information.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6n8ivSLK1xZ9mEXLefai/47423062941204)
{% endstep %}

{% step %}
Add your **Cards**.
{% endstep %}

{% step %}
(Closed and hybrid only) Add your **Categories**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/3TA8beF9eJOMc5U4HWFw/47423126734228)
{% endstep %}

{% step %}
(Optional) Enable randomization options in the right sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/hFFePCVbuNV6HUuuakpr/47423126734996)
{% endstep %}

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

Now, you've successfully added a card sort question to your study. When participants reach this question, they'll see your instructions. Then, we'll instruct them on how to complete the card sort activity.

## Analyze a card sort question

From the **Responses** tab of your study, you can view all responses to a card sort question at once or view how each individual participant responded.

{% hint style="info" %}
**Note:** Card sort questions are not currently supported by Dscout AI, including AI analysis features.
{% endhint %}

## Questions view

From the **Questions** view, you'll see how everyone in your study responded to a card sort question.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/EbiDYeiixPDulqqgB1tS/47423126736276)

Here, you can choose from three views: **Agreement matrix**, **Cards**, and **Categories**.

### Agreement matrix

Selecting **Agreement matrix** shows every card against every category. Each cell displays the count or percentage of participants who sorted that card into that category. Use this to quickly spot consensus (high agreement) and disagreement across your participant group:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/AW7asu7Ev3pWMKguDn1e/47423062947988)

### Cards view

Selecting **Cards** lets you focus on one card at a time. For each card, you can see which categories it was sorted into, how many participants placed it there, and an agreement rating. Rows can be sorted by count, percentage, or agreement rating:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/AW7asu7Ev3pWMKguDn1e/47423062947988)

### Categories view

Selecting **Categories** shows one category at a time. This lets you see which cards ended up in each category, along with counts and agreement ratings, which is particularly useful for open and hybrid sorts where categories were created by participants:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/WfoCIHT6q2bzyNMPvpCO/47423062952084)

#### Merge categories (open and hybrid only)

In open and hybrid card sorts, categories created by participants are auto-merged if they have (case-insensitive) identical names. Merged categories are indicated with the following icon (two lines joining into an arrow):

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/OojbBipoRrn0hN9rQfCU/47423062962452)

However, you can also manually merge categories or unmerge categories.

**To manually merge categories:**

{% stepper %}
{% step %}
Select multiple categories on the **Categories** view.
{% endstep %}

{% step %}
Click **Merge categories**. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/q3eZFCrStDzohklFZ57r/47423126747924)
{% endstep %}

{% step %}
Verify you want to merge the categories displayed.
{% endstep %}

{% step %}
(Optional) Enter a **Merged category name**.
{% endstep %}

{% step %}
Click **Merge x categories**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4IkFTuU0xCExhRl0UvfC/47423126751380)
{% endstep %}
{% endstepper %}

**To unmerge categories:**

{% stepper %}
{% step %}
Click the Edit (pencil) icon beside a category. The category's details are displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/pu13WQeqL6ttn328IlHU/47423126753556)
{% endstep %}

{% step %}
Click the **X** beside any categories you want to unmerge.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/E0BqVOEAJAJJ3YRRR08u/47423062973972)
{% endstep %}

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

#### Rename categories

From the **Categories** view, you can also rename categories for easier analysis.

**To rename categories:**

{% stepper %}
{% step %}
Click the Edit (pencil) icon beside a category. The category's details are displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/pu13WQeqL6ttn328IlHU/47423126753556)
{% endstep %}

{% step %}
Enter a new **Category name**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/9hWX9ZnPEUe13KgntRjc/47423126758420)
{% endstep %}

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

## Participants view

From the **Participants** view, you'll see how individual participants in your study responded to a card sort question.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/apa6KNQAL877fEVzQLqe/47423126760980)


# Screen recording guide for researchers

When you include a screen recording prompt in a study, scouts and participants will need to be familiar with how to screen record on their device in order to accomplish your prompt. Check out the guidance + tutorials illustrated below to get a better sense of what your participants will experience when encountering a screen recording question:

### Mobile screen recording walkthrough

If you're looking to prompt scouts to record their entire mobile screen and walk you through an experience in a mobile app outside of Dscout, we recommend using the *Screen Recording - App* question type. Native OS screen recording technology is used to record screen activity, and scouts are shown a tutorial on how to screen record (below). This tutorial will also verify that each scout's audio is setup correctly prior to recording.

{% tabs %}
{% tab title="Android" %}
![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/RZhLjVbdvvTLRjlfewRs/34987400530580)
{% endtab %}

{% tab title="iOS" %}
![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/lkcZdxZ5q6jg3z5aMKFY/34987400537876)
{% endtab %}
{% endtabs %}

### Desktop screen recording walkthrough

Screen recording prompts can also be utilized in desktop diary studies + desktop media surveys. Check out the walkthroughs below for a full description of what your participants will see during these prompts, based on the question type you utilize, ("link" vs. "no link").

{% tabs %}
{% tab title="Link" %}
Participants will first see a full page view of the prompt, a "Go to Website" button (which will route them to the link you've programmed), and guidance for best practices while screensharing.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5hb49zsrX10kFgztRIQb/26602172620180)

After tapping "Go to Website," participants will be taken to the link provided in the prompt; the Dscout Chrome extension widget will appear, containing a red "Start Recording" button.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aBJevZWI4boNgDDReUOL/26602168812820)

After tapping "Start Recording," Chrome's or Edge's native screensharing prompt will appear. Participants must select their screen preview in order for the "Share" button to activate (before and after illustrated below):

![Screenshot 2024-05-14 at 2.02.30 PM.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/G5kEYf4IrXbYbd4VDEbp/26602172639636) ![Screenshot 2024-05-14 at 2.02.38 PM.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6Oe6oDpmTnZnIoONJV8d/26602168829204)

After tapping "Share," a countdown will begin, after which the Dscout extension widget will minimize the prompt (this can be expanded if needed!); participants will end their screen recording by tapping the red "stop" icon.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/hEDtIVLFHA9PZAMyoH3v/26602168837268)
{% endtab %}

{% tab title="No link" %}
If you've chosen to not provide a link to participants in a screen recording prompt, participants will be taken to a full page view containing screen recording best practices, and will see the Dscout browser extension appear in the top right corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QKmB8XKdNwNcI9EFdajD/26602172670356)

After tapping "Got it!" in the extension widget, scouts will then see your prompt, along with the red "Start Recording" button.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ytN0suudYpUMnoGXnFx2/26602172679060)

After tapping "Start Recording," Chrome's or Edge's native screensharing prompt will appear. Participants must select their screen preview in order for the "Share" button to activate (before and after illustrated below):

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/K6vsNyTdvsqVMoFchMdx/26602168865300) ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dxsYQxD494uFd29agLNj/26602172696340)

After tapping "Share," a countdown will begin, after which the Dscout extension widget will minimize the prompt (this can be expanded if needed!); participants will end their screen recording by tapping the red "stop" icon.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/hEDtIVLFHA9PZAMyoH3v/26602168837268)
{% endtab %}
{% endtabs %}


# Question banks

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

{% hint style="info" %}
**Note:** Question banks are only available on **Plus**, **Select**, and **Enterprise** plans.
{% endhint %}

Saving frequently used questions for future use can speed up your research and ensure consistency across projects. Question banks let you do just that, offering a place where you and your collaborators can save questions and access questions saved by others.

{% hint style="success" %}
To kick off your question bank, check out [**this spreadsheet**](https://docs.google.com/spreadsheets/d/1F9a5MWMPQnt8o4D3D4nHJ-UwuxM06-D4C88sb8s4-DM/edit?usp=sharing) of over 500 sample questions on our People Nerds blog.
{% endhint %}

## View and edit banked questions

You can access all your banked questions (as well as those saved by others in your Dscout account) from the **Question banks** settings page. Here, you can add, edit, and clone questions.

{% hint style="info" %}
Unless you are an account owner, administrator, or workspace lead, you can only edit your own questions. However, you can still add questions saved by other users to your studies.
{% endhint %}

**To access your question bank:**

{% stepper %}
{% step %}
In the sidebar navigation, click your Dscout account name. A drop-down opens displaying the accounts you belong to.
{% endstep %}

{% step %}
Click the **Settings** icon beside the account where you want to view the question bank. The **Account management** page is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rEovxjbGFzeraHW3a9hc/39583985379732)
{% endstep %}

{% step %}
Select the **Question banks** tab. The list of banked questions across your projects is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JNtoneecWb2VyoZOktGm/39583985608724)
{% endstep %}

{% step %}
Click the question you want to edit.
{% endstep %}

{% step %}
Make the necessary changes. You can edit things like the question title, prompt, save location, and more.
{% endstep %}

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

To locate specific questions, use the search bar or the filter options at the top of the page to narrow down your view.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/qfi8YM02KcVvGG71eHEq/39583985600020)

{% hint style="info" %}
Use the heart icon to mark questions you use even more often than others in your question bank as favorites. You can then filter your view to find your favorites faster.
{% endhint %}

## Bank a question

You can add new questions to your question bank from the **Question banks** settings page itself or while building a screener or study.

{% hint style="info" %}
Contributors can’t bank their own questions, but they can add questions banked by others to their studies.
{% endhint %}

To bank a question from the Question banks settings page:

{% stepper %}
{% step %}
In the sidebar navigation, click your Dscout account name. A drop-down opens displaying the accounts you belong to.
{% endstep %}

{% step %}
Click the **Settings** icon beside the account where you want to view the question bank. The **Account management** page is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rEovxjbGFzeraHW3a9hc/39583985379732)
{% endstep %}

{% step %}
Select the **Question banks** tab. The list of banked questions across your projects is displayed.
{% endstep %}

{% step %}
Click **+ Add new question**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/qfi8YM02KcVvGG71eHEq/39583985600020)
{% endstep %}

{% step %}
Select what type of question you want to add. The settings for the selected question type is displayed.
{% endstep %}

{% step %}
Enter a **Title**.
{% endstep %}

{% step %}
(If applicable) Select a **Save to** location. You can either save the question to a specific workspace or make it available to everyone in your Dscout account. If your account doesn’t have workspaces, the question will automatically be saved at the account level. For more information on workspaces, see [Creating and navigating Dscout workspaces](/getting-started/workspaces-and-projects/creating-and-navigating-dscout-workspaces).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/XhoCkrU2CB3cGYKeOp9w/39583985602708)
{% endstep %}

{% step %}
Complete the required fields and settings for your question.
{% endstep %}

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

Now, your question is added to your question bank and will be visible to your collaborators. To edit the question, simply click it in the question list, make your changes, and click **Save**.

If you’re building a screener or study and decide you want to save one of your questions to your question bank, you can do that directly from the builder.

To bank a question while building a screener or study:

{% hint style="info" %}
Questions banked from a screener or study will retain most of their settings. For example, a question with multi-select enabled will be saved with this setting enabled. However, task URLs are not saved when banking task questions.
{% endhint %}

{% stepper %}
{% step %}
In the builder, add the question you want to save to your study.
{% endstep %}

{% step %}
Click the ellipses at the top right of the question.
{% endstep %}

{% step %}
Click **Save question**. The **Save as new question** dialog appears.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/iayGDwk2D1sQIZvJzore/39583985604372)
{% endstep %}

{% step %}
Enter a **Title**.
{% endstep %}

{% step %}
(If applicable) Select a **Save to** location. You can either save the question to a specific workspace or make it available to everyone in your Dscout account. If your account doesn’t have workspaces, the question will automatically be saved at the account level.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ICGHxN3NvTZcA96a9eUS/39584045910420)
{% endstep %}

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

Now, your question is added to your question bank. You can view it from the **Question banks** settings page or add it to other screeners or studies using the steps below.

## Add a banked question to a study or screener

Once you’ve added a question (or a few!) to your question bank, you can add them to your studies or screeners directly from the builder. However, you’ll only be able to add questions that are supported by your screener or study type. For example, you’ll only be able to add saved Task questions to usability tests.

{% hint style="info" %}
Banked questions maintain the settings they had enabled when originally saved. Be sure to double-check the settings of each question once you’ve added it to your study.
{% endhint %}

{% stepper %}
{% step %}
In the builder, click **+Add** (or **+Add a screener question**) in the sidebar or beneath your last question. Or, click the + icon between existing questions.
{% endstep %}

{% step %}
Click **Add from question bank**. The **Question bank** dialog appears, displaying all of your saved questions (as well as a few sample questions courtesy of Dscout).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/kq4oQloOZY40kTUySAxl/39583985623700)
{% endstep %}

{% step %}
Select a question(s).
{% endstep %}

{% step %}
Click **Add question to study/screener**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/yJhr5TtFRZ3Xbx8JqU8k/39584045912852)
{% endstep %}
{% endstepper %}

Now, your selected question(s) are added to your study or screener exactly as you’d previously saved them.

## Clone a banked question

If you have several questions that involve a similar prompt or settings, you can create saved versions of each iteration quickly by cloning a question you already have saved. Then, you can make the adjustments needed right in your question bank rather than recreating and saving each question individually.

{% stepper %}
{% step %}
In the sidebar navigation, click your Dscout account name. A drop-down opens displaying the accounts you belong to.
{% endstep %}

{% step %}
Click the **Settings** icon beside the account where you want to view the question bank. The **Account management** page is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rEovxjbGFzeraHW3a9hc/39583985379732)
{% endstep %}

{% step %}
Select the **Question banks** tab. The list of banked questions across your projects is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JNtoneecWb2VyoZOktGm/39583985608724)
{% endstep %}

{% step %}
Find the question you want to clone.
{% endstep %}

{% step %}
Click the **Clone** icon.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/sJ2yWI44uw63fzehdtAH/39584045915156)
{% endstep %}
{% endstepper %}

Now, a copy of the question is created and you’re able to edit the settings as needed. When you’re done, click **Save** to save this new version of the question.

## Delete a banked question

You can delete unneeded questions from your question bank from the **Question banks** settings itself or while building a screener or study.

{% hint style="info" %}
Account owners and administrators can delete any question. Workspace leads can delete questions from the workspaces they lead. All other users can only delete the questions they have saved themselves.
{% endhint %}

To delete a banked question from the Question banks settings page:

{% stepper %}
{% step %}
In the sidebar navigation, click your Dscout account name. A drop-down opens displaying the accounts you belong to.
{% endstep %}

{% step %}
Click the **Settings** icon beside the account where you want to view the question bank. The **Account management** page is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rEovxjbGFzeraHW3a9hc/39583985379732)
{% endstep %}

{% step %}
Select the **Question banks** tab. The list of banked questions across your projects is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JNtoneecWb2VyoZOktGm/39583985608724)
{% endstep %}

{% step %}
Find the question you want to delete.
{% endstep %}

{% step %}
Click the **Delete** icon. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Ry6rFnaWiKlQaaUuheTJ/39583985623316)
{% endstep %}

{% step %}
Select **Yes, I want to delete this question** and click **Delete question** to confirm.
{% endstep %}
{% endstepper %}

To delete a banked question while building a screener or study:

{% stepper %}
{% step %}
In the builder, click **+Add** (or **+Add a screener question**) in the sidebar or beneath your last question.
{% endstep %}

{% step %}
Click **Add from question bank**. The **Question bank** dialog is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/kq4oQloOZY40kTUySAxl/39583985623700)
{% endstep %}

{% step %}
Click the ellipses at the top right of the question.
{% endstep %}

{% step %}
Select **Delete**. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dXOaVBrNIGT02ORcelzD/39584045920788)
{% endstep %}

{% step %}
Select **Yes, I want to delete this question** and click **Delete question** to confirm.
{% endstep %}
{% endstepper %}

Now, the question is no longer saved in the question bank. However, the question will still be present in any screeners or studies where it’s already in use, so be sure to delete the question from those too if necessary.


# Question groups

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

Question groups let you visually group related questions together in the builder. This helps you keep things organized, but it also gives you the option to randomize the order in which participants see the questions, helping to reduce participant bias. Questions in a question group appear no differently to participants, so only you will know they’ve been grouped together.

## Question group settings

You’ll access question group settings in the right sidebar of the builder:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QUmzEwpDl637SDzp1Zlh/40656787047060)

Here’s a breakdown:

| Setting                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Randomize questions** | <p>When enabled, participants will see all questions contained within the question group in a random order.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Skip logic and piping logic are not available when randomization is enabled, nor can a question group be used as a skip logic destination. All existing logic will be removed when this setting is enabled.</p></div><p>If some of your questions rely on each other, you can use multi-variate testing to keep related questions together while presenting each concept in a random order. For more information, see <a href="/study-basics/question-types/multi-variate-testing">Multi-variate testing</a>.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>This setting cannot be changed post-launch.</p></div> |

## Add a question group to a study

You’ll add question groups on the **Usability test**, **Media survey**, or **Study** tab of your study. Once you’ve added a group, you can then add new questions within it or drag and drop existing questions to be part of it.

{% stepper %}
{% step %}
Navigate to the **Usability test/Media survey/Study** tab of your study.
{% endstep %}

{% step %}
Click **+ Add** in the center of the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/IwFB8yAzZJ3GIVOsWpFa/37450774951956)
{% endstep %}

{% step %}
Under **More**, select **Add question group**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/HvPm165QzUQayPgaFODA/40656787054100)
{% endstep %}

{% step %}
Now, a new question group is added to your study. Click **+ Add** within the group to add a new question to it. Or, drag and drop an existing question into the group. You can also click the group name (“Untitled question group” by default) to rename it.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/skvZk5Ten6GYrQp2UmMm/40656787057428)
{% endstep %}
{% endstepper %}

{% hint style="info" %}
You can apply skip logic and piping logic to questions within a question group just as you normally would (so long as randomization is not enabled).
{% endhint %}

## Ungroup questions

If you no longer want a question to be part of a question group, you can move it out of the group.

{% hint style="success" %}
**Tip:** To quickly ungroup a question, simply drag and drop it to a new location in the builder.
{% endhint %}

{% stepper %}
{% step %}
Navigate to the question group where you want to ungroup a question.
{% endstep %}

{% step %}
Click the three-dot icon in the top right corner of the question.
{% endstep %}

{% step %}
Select **Move out of group**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/piBjX6I00QJVEmQCwtFI/40656796943252)
{% endstep %}
{% endstepper %}

Now, the question is moved out of the group and placed directly below it. You can drag and drop the question to relocate it elsewhere in your study.

## Analyze a question group

You can analyze questions in a question group just as you normally would that individual question type. However, you’ll see these questions grouped together on the **Responses** tab for easy access (or to easily collapse them until you need to view them again!):

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aZWKLY9LUPc6bVIbHugN/47543385675412)

Questions are displayed in the order they appear in the builder by default. If you’ve enabled randomization, you can view the questions in the order they were presented to each participant by navigating to individual responses from the **Participants** view:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/NwZoVhrAZXd8Ckuegv4J/47543385676948)


# Multi variate testing

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

Multi-variate testing lets you randomize the order in which participants see prototypes, concepts, or designs in your study. If every participant sees Concept A and then sees Concept B right after, it’s easy for a bias to form across your responses. Multi-variate testing solves that by showing up to three variants in a random order to each participant.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Td8bBzQzy8ejmSsE7cYA/40411372171028)

Each multi-variate question can hold up to three variants, but you can add as many multi-variate questions as you need to a study. You can also choose to show each participant only one variant from each multi-variate question while ensuring an even distribution across all participants.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/iTdY3ZZFCyQggHvrnfTW/40411406130452)

{% hint style="info" %}
**Note:** Even distribution is dependent on the number of participants who complete your study. For example, if you invite ten participants but have three variants to test, one variant will have an additional response. If a participant begins a study but abandons it, Dscout will automatically prioritize showing their variant or their variant order to another participant.
{% endhint %}

## Multi-variate settings

When adding a multi-variate question to your study, you can choose whether participants see all variants or if they only see one variant at random:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/so7JQkevRbfAKLQsBXY1/40411406131476)

| Setting           | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Randomization** | <p>Determines whether a given participant is shown one or all variants in the multi-variate question. Choose from the following options:</p><ul><li><strong>Show all (default):</strong> Participants will see all variants in this question presented in a random order.</li><li><strong>Show one:</strong> Participants will only see one variant in this question at random.</li></ul><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Warning:</strong> This setting cannot be changed post-launch.</p></div> |

You can also choose to randomize the questions within a variant itself. To access this setting, click the variant you want to randomize:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/grosRpYz86EaUfm6VhxN/40411372177812)

| Setting                                      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Randomize questions (variant-level only)** | <p>When enabled, participants will see all questions contained within this variant in a random order.<br></p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Randomization applies to all questions within a single variant. If your questions rely on a specific prototype that is part of that variant, you may want to leave randomization disabled as we cannot ensure that question will be displayed before any others.</p></div><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Warning:</strong> This setting cannot be changed post-launch.</p></div> |

## Add a multi-variate question to a study

You’ll add multi-variate questions on the **Usability test**, **Media survey**, or **Study** tab of your study. Once you’ve added a question, you can then add new variants (and their associated questions) within it.

{% stepper %}
{% step %}
Navigate to the **Usability test/Media survey/Study** tab of your study.
{% endstep %}

{% step %}
Click **+ Add** in the center of the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/IwFB8yAzZJ3GIVOsWpFa/37450774951956)
{% endstep %}

{% step %}
Under **More**, select **Multi-variate**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/h1VhdYBdFLPP9GxRtRmS/40411406134676)
{% endstep %}

{% step %}
(If applicable) Select **Show one** to only display one variant to each participant at random. By default, **Show all** is selected. For more information, see [Multi-variate settings](#h_01K31R69HBQ531VFH3ZWT1K2K8).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/so7JQkevRbfAKLQsBXY1/40411406131476)

{% hint style="info" %}
**Note:** You cannot change this setting once you’ve launched your study, so make this decision carefully.
{% endhint %}
{% endstep %}

{% step %}
Click a variant to expand it, then click **+ Add question** to add that variant’s relevant questions. Here, you can also enable randomization within this variant. For more information, see [Multi-variate settings](#multi-variate-settings).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/brT28qyFVCxYtZvewTTH/40411372182292)

{% hint style="info" %}
**Note:** Task questions with associated task URLs will have **Close task URL** enabled by default inside of variants. For more information, see [Task questions](/study-basics/question-types/task-questions).
{% endhint %}
{% endstep %}
{% endstepper %}

By default, a multi-variate question begins with two variants, but you can test up to three in each question. Click **+ Add variant** to add another variant.

You can rename your multi-variate question and variants to study-specific names by clicking on them. This will make analysis easier, helping you find insights faster.

{% hint style="success" %}
**Tip:** You can drag and drop variants between multi-variate questions or drag and drop them into question groups. You can also drag and drop entire question groups into a multi-variate question as a new variant. Keep in mind that each question can only hold up to three variants.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Kmfh1SmGg4vvVHyp6YTp/40411406138132)

{% hint style="info" %}
**Note:** You can preview your multi-variate question just as you can the rest of your study. However, to test the randomization first-hand, you must do so using Test mode. Test mode is only available for usability tests and media surveys. For more information, see [Test a usability test](/usability-tests/create-a-usability-test/test-a-usability-test) or [Test a media survey](/media-surveys/create-a-media-survey/test-a-media-survey).
{% endhint %}

## Piping and skip logic in multi-variate questions

Because multi-variant questions are automatically randomized, there are some restrictions on how and when you can use piping and skip logic.

### Piping logic

Piping logic lets you recall answers from previous questions as participants progress through a study. In multi-variate questions, you can use piping logic to:

* Recall answers from questions that precede the multi-variate question.
* Recall answers between two questions within the same multi-variate question (unless the questions within that variant are randomized).

Because your variants will all be presented in different orders to each participant, you can’t recall answers across variants. For more information, see [Piping logic](/study-basics/design-a-study/piping-recall-logic).

### Skip logic

Skip logic lets you send participants to specific questions based on their answer choices. In multi-variate questions, you can use skip logic to:

* Skip participants directly to a multi-variate question (not a specific variant).
* Skip participants to the end of a variant, moving them on to the next question outside of the multi-variate question. (Only available when **Show one** variant is enabled.)
* Skip participants from one question to another within the same variant. (Only available if **Randomization** is disabled.)

If questions within a variant are randomized, skip logic is disabled for that variant. For more information, see [Skip logic](/study-basics/design-a-study/skip-logic-in-screeners).

## Analyze a multi-variate question

You can analyze questions in a multi-variate block just as you normally would that individual question type. However, from the **Questions** view, you’ll see these questions grouped together on the **Responses** tab for easy access:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/mbaDLc1pEV0OxaPSTUFv/47543346142612)

### Analyze variants by participant

By default, variants and their questions are displayed in the order they appear in the builder. However, you can view everything in the order it was presented to each participant by navigating to individual responses from the **Participants** view:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/L80QFmyU90RscARxLuBH/47543346143124)

### Variant tags

Dscout automatically creates tags to help you easily filter between participants who saw specific variants or who saw variants in a specific order. To access these, click the **Filter** icon in the top right corner of the **Responses** tab. Then, select **Tags**. You'll see tags for each variant nested beneath the name of your multi-variate question:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6Eghdm3llikGUAcfgHFp/47543346144660)


# Using question quotas

**Quotas can be set on both single-select and multi-select questions**. This feature is available in screeners, usability tests, and media surveys.

**You have the option to set either “equal to” or “at most/at least” quotas.** For “equal to” quotas, you’ll indicate the exact number of responses you’d like for a given choice. Use on single-select questions when you’d like to ensure a specific number of responses for either one choice, or for multiple choices. If a participant's selection is above your set quota for that question, they'll be excused as a potential participant, saving you time.

Use “at most/at least” when your recruit criteria is more flexible, but you want to ensure that at least a few participants pick a certain choice, or that too many participants don’t pick another choice.

* When using “equal to” quotas, any response option that does have a quota will accept submissions that select that option until the quota is met and then the selection will become a knockout for participants. Any response option that does not have a quota set will be an automatic knockout.
* When using “at most/at least” quotas, responses will either be reserved until at least a minimum number of a specific response is collected, or it will ensure that no more than a certain amount of responses are collected for a given condition. You can use just “at least” or “at most”, or use both in the same question.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/37BxIvW1mTueZgEr4G0U/33671395021332)


# Question stimuli

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr><tr><td><strong>Diary studies</strong></td><td>true</td></tr></tbody></table>

You can add stimuli to questions in screeners and unmoderated studies to get participant feedback on visual assets, concepts, and more. You can also randomize your stimuli to help prevent bias.

{% hint style="info" %}
**Note:** This article covers stimuli in unmoderated studies. For information on adding stimuli to an interview study, see [Add stimuli to an interview study](/interview-studies/create-an-interview-study/add-stimuli-to-an-interview-study).
{% endhint %}

## Stimuli limitations

When working with stimuli in Dscout, some limitations apply:

* Up to 5 pieces of stimuli can be added to a single question.
* Supported file types include .jpg and .png. (**GIF files are not supported**.)
* Recommended maximum file size is **1 MB**.
* **(Mobile)** Recommended file dimensions are 1080 x 1920 with a portrait aspect ratio.
* **(Desktop)** Recommended minimum width of 1300 pixels. (Lower resolutions may appear pixelated to participants.)
* **Participants must view** ***all*** **images** attached to a question before they can provide a response or advance to the next question.
* **Stimuli cannot be added to card sort, tree testing, screen recording, or task questions.**
* **Stimuli cannot be added to AI moderated studies.**

## Add stimuli to a question

You’ll add stimuli at the question level. Once you’ve uploaded a piece of stimuli, you can attach it to additional questions in the builder without having to re-upload it.

{% hint style="info" %}
**Tip:** Once you’ve added a piece of stim, you can assign it to additional questions without re-uploading.
{% endhint %}

{% stepper %}
{% step %}
Click the question in the builder. The question’s settings are displayed.
{% endstep %}

{% step %}
Click **Add** or **+ Add stimuli**. The add stimuli modal is displayed.

**Screeners, usability tests, media surveys, intercept studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/USjb8FPKHNNMkfIMwHv1/48967002556692)

**Diary studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/nnQleQlEywJLGCHd29Z1/48967002563732)
{% endstep %}

{% step %}
Drag and drop files to upload them. Or, click to browse for files on your device. Uploaded files are displayed on the right of the modal.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/LK4Q1WljFqKhkMHJdQJR/48967002566036)

{% hint style="info" %}
**Tip:** Files you’ve already uploaded are displayed on the right of the modal. You can select existing files here without re-uploading them.
{% endhint %}
{% endstep %}

{% step %}
Choose images to attach to your selected question. Use the checkboxes to the left of your stimuli. Your selections populate the question’s five allowed pieces of stimuli at the top of the modal.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/LAUByqOGgbUvoDYEkxqs/48967002569364)

{% hint style="info" %}
**Tip:** Click **Untitled image** to give your uploaded stimuli a participant-facing name. Participants will never see stimuli file names.
{% endhint %}
{% endstep %}

{% step %}
Click **Insert images**. Once you’ve finalized your selection.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/62gBlG3LOs653yaLIVyn/48966979660948)
{% endstep %}
{% endstepper %}

Now, the selected stimuli are added to the question. When participants reach this point in your study, they’ll have to view all pieces of stimuli before they can provide a response or proceed to the next question in your study.

You can preview any stimuli by clicking on it in the builder:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ZTJuojvU6O9A60L4QMVI/48966979662484)

To edit a question’s stimuli, simply return to the **add stimuli** modal from the builder.

## Display or hide stimuli titles to participants

Depending on your research needs, you may not want your participants to see the titles you give your stimuli. Titles are displayed by default, however you can control this from the builder using the **Hide titles** and **Show image titles to Scouts** toggles:

**Screeners, usability tests, media surveys, intercept studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/a5UOHEt3cB8r4vFNCNGY/48967002579092)

**Diary studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7J6w5oyTj9krfCqDzDWF/48967002581524)

## Randomize stimuli

To avoid bias, you can randomize stimuli at the question level. This presents any stimuli attached to that question to each participant in a random order. During analysis, you’ll be able to see the order in which each participant saw your stimuli from the **Participants** view.

{% hint style="warning" %}
**Warning:** Changing this setting on a launched screener or study will create a new version of the associated question during analysis. For more information, see [Edit a launched screener or study](/study-basics/edit-close-or-relaunch-studies/edit-a-launched-screener-or-study).
{% endhint %}

{% stepper %}
{% step %}
Click the question in the builder. The question’s settings are displayed.
{% endstep %}

{% step %}
Set the **Stimuli randomization** toggle to **ON**.

**Screeners, usability tests, media surveys, intercept studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cRkjJl3TGCAXuA0TElF0/48966979670164)

**Diary studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/F4rPfUfqRocxwIv56UzW/48966979671572)

{% hint style="info" %}
**Note:** This setting is only displayed when two or more pieces of stim are added to a question.
{% endhint %}
{% endstep %}
{% endstepper %}

Now, the stimuli for that question will be displayed to participants in a random order. To display stimuli to participants in the order they appear in the builder, set this toggle to **OFF**.

{% hint style="info" %}
**Note:** Stimuli will not be randomized when previewing your study. However, stimuli will be randomized when viewing your study in test mode.
{% endhint %}

Questions with stimuli randomization enabled show a chip letting you know:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/xyDrHqwmEatSoCoYTX9T/48967002592532)

## Download stimuli

You can download stimuli that’s been added to your study directly from the builder. This is helpful if another researcher uploaded stimuli but you want to keep a copy handy for yourself.

{% stepper %}
{% step %}
Click **Add** or **+ Add stimuli** on any question in your study. The add stimuli modal is displayed.
{% endstep %}

{% step %}
Click the **Download** icon beside any piece of stim. Or, click **Download all** to download everything that’s been added to the study.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/WGKu4vhA1D3NjRczVac6/48966979675028)

Now, stimuli downloaded individually are automatically saved wherever your device stores downloaded files. If you download all stimuli at once, a progress bar is displayed at the top of the builder. When prompted, click **Download** to download a ZIP file of all your study’s stimuli.
{% endstep %}
{% endstepper %}


# Tree testing questions

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability test</strong></td><td>true</td></tr><tr><td><strong>Media survey</strong></td><td>true</td></tr></tbody></table>

Tree testing questions let you discover how participants would work through a navigational structure to complete a desired objective or task. Let’s say you run an online clothing store and want to make sure certain articles of clothing can be found where your users expect them to be. Or maybe you’re developing a new music app and are unsure about the information architecture. With tree testing questions, you can find exactly what works for your users.

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/jf8MbTSkYE26yWGlOBfF/47576599282964" alt="" width="375">

### Tree testing settings

When adding a tree testing question to your study, you’ll customize your question in the center of the builder:

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/SoLFVNpxJXIIan3dzG5r/47576540808212" alt="" width="563">

Here’s a breakdown of each option:

| Setting                         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Prompt**                      | <p>The prompt or instructions participants see as part of this question. Here, a clear objective you want participants to complete using your provided tree structure. For example, “Show me how you would go about finding rain boots for the upcoming season.” Or “You’ve recently changed jobs and want to update your address. Where would you go to do that?”<br></p><p>You can format your text in the following ways:<br><br>- <em><code>bold</code></em> = <strong>bold</strong><br>- <em><code>italic</code></em> = <em>italic</em><br>- <code><[https://examplelink.com>](https://help.dscout.com/study-basics/question-types/https:/examplelink.com>)</code> = <a href="https://examplelink.com/"><https://examplelink.com></a><br>- <a href="https://examplelink.com"><code>Sample link</code></a> = <a href="https://examplelink.com/">Sample link</a></p> |
| **Add success path** (optional) | <p>The path you hope participants will take when completing the provided task. Including a success path lets you validate whether any structure you already have in place is working or whether it might need adjusting to meet users’ expectations. For more information, see <a href="#add-a-success-path-to-a-tree-testing-question">Add a success path to a tree testing question</a>.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> If you have more than one possible success path in mind, you can select up to two.</p></div>                                                                                                                                                                                                                                                            |
| **Tree**                        | The individual items that make up your navigational hierarchy. Here, you can add parent nodes as well as child nodes to create the structure you want participants to navigate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |

### Add a tree testing question to a study

You’ll add tree testing questions on the **Usability test** or **Media survey** tab of your study.

{% stepper %}
{% step %}
Navigate to the **Usability test** or **Media survey** tab of your study.
{% endstep %}

{% step %}
Click **+ Add** in the center of the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/tUAS15nB5j4730XKmDMb/47576524663828)
{% endstep %}

{% step %}
Under **Standard**, select **Tree testing**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/a0ke1GpNBl607GJIDWhT/47576540812436)
{% endstep %}

{% step %}
Enter the **Prompt** (instructions).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/b6mrPWg7zLlSd3bAGNIZ/47576540816404)
{% endstep %}

{% step %}
Add nodes to build your **Tree**. Hover and click the **+** within a node to add child nodes. Your tree can have up to 300 nodes in total.

{% hint style="success" %}
**Tip:** Copy your tree structure from a spreadsheet and paste it into your question. For more information, see [Copy and paste a tree structure](#copy-and-paste-a-tree-structure).
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/2aIN3TJl6jmkoIuFQBaT/47576524667028)
{% endstep %}

{% step %}
**(Optional)** Add a success path to your question. For more information, see [Add a success path to a tree testing question](#add-a-success-path-to-a-tree-testing-question).
{% endstep %}

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

Now, your tree testing question is added to your study. When participants reach this question, they’ll see the provided instructions as well as a navigable version of your tree structure. They can move backward and forward within this structure before submitting their final response and moving on to the next question.

#### Copy and paste a tree structure

Instead of adding nodes to your tree manually, you can copy the structure from a spreadsheet and paste it into Dscout.

Spreadsheets must be in the following structure, with each node in its own cell and child nodes listed one column to the right of their parent node:

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Snlz3MPdIr5yVCdvTefi/47658677271828" alt="" width="375">

Pasting this example into Dscout results in the following tree structure:

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aKZG38ejdPngYJ4nCMRf/47729242802580" alt="" width="563">

#### Rearrange a tree structure

Once you've added your nodes, you can drag and drop them to rearrange your tree structure:

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/To5yn1pqOrzR1PX886Qi/47729242806420" alt="" width="375">

#### Add a success path to a tree testing question

If you have an ideal navigation path in mind, you can set that as a success path in Dscout to unlock additional insights during analysis. For example, with a set success path, you can view whether a participant took a direct route or an indirect route in their response.

{% stepper %}
{% step %}
After adding your tree structure, click **Add success path**. A success path modal is displayed with your entered tree structure.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ZMthVsSGyfVzD9gtoj1y/47576540825876)
{% endstep %}

{% step %}
Select the final node that indicates success if selected by the participant.

{% hint style="success" %}
**Tip:** If there are multiple possible success paths, you can **up to two nodes** in this modal. Your selected success paths are displayed to the left of the tree structure.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/BJrQ1JK73QNhY7J2bqze/47576540827668)
{% endstep %}

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

Now, your success path is set. You’ll be able to compare participant responses to this path during analysis.

### Edit a tree testing question

You can edit questions however you need prior to launching your study. However, if you want to edit a question after your study is launched, some changes will affect how your data appears in analysis. For example, removing a node from your tree entirely will split your data into two versions you'll need to analyze separately.

Here's a breakdown of which changes will and won't create a new version of your tree testing question's data:

| Won't cause versioning                                                                                                                                                                           | Will cause versioning                                                                                                                  |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Editing a node's label.</li><li>Adding, updating, or removing a success path.</li><li>Rearranging node positions under the same parent (without moving nodes to a new parent).</li></ul> | <ul><li>Adding a new node.</li><li>Removing a node.</li><li>Moving a node to a different parent/level in the tree structure.</li></ul> |

For more information on editing your study post-launch, see [Edit a launched screener or study](/study-basics/edit-close-or-relaunch-studies/edit-a-launched-screener-or-study).

### Analyze a tree testing question

From the **Responses** tab of your study, you can see how all of your participants completed the given objective overall or narrow your view to individual participant responses.

#### Questions view

The **Questions** view gives you an overview of all responses to a given tree testing question, including metrics on the directness of participant selections, average time on task, and more.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/66Ucke8odSHE0NoCO82T/47576540832276)

Here’s a breakdown of each metric:

| Metric                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Success rate** (questions with success path only)                  | <p>The percentage of participants who selected your designated success path.</p><p><br>If you have more than one possible success path, you’ll also see the percentage of participants who selected each individual path.</p>                                                                                                                                                                                                                                                                                                   |
| **Most common submission** (questions without success path only)     | The final node in your tree structure most commonly selected by participants.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| **Overall directness of success** (questions with success path only) | <p>The percentage of participants who selected your designated success path with no backward navigation in your tree structure.</p><p><br>If you have more than one possible success path, you’ll also see the percentage of participants who directly navigated to each individual path.</p>                                                                                                                                                                                                                                   |
| **Directness** (questions without success path only)                 | The percentage of participants who selected their path with no backward navigation in your tree structure.                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Average time on task**                                             | <p>The average response time for the task across participants.</p><p><br>If your question has a success path, you’ll also see the average response time of all participants who submitted this success path as their final response.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> If your question has multiple success paths, you’ll see an <strong>Overall average time on task</strong> as well as individual breakdowns for each success path.</p></div> |
| **Average clicks**                                                   | The average number of clicks made by participants before submitting their final responses.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Most common first click**                                          | <p>The node of your tree structure participants most often clicked first when completing the given task.</p><p><br>If your question has a success path, you’ll also see the node most commonly selected by participants who submitted this success path as their final response.</p>                                                                                                                                                                                                                                            |

You can also use the tabs below these metrics to open additional views. See the sections below for more information.

**Participant data**

Displays at-a-glance metrics for each participant’s response, including:

* **Success:** Whether the participant selected one of your designated success paths. This is only displayed if you selected a success path while building.
* **Time:** The amount of time the participant spent making their selection.
* **Clicks:** The number of clicks the participant took prior to submitting their selection.
* **First click:** The first node the participant selected while completing the task.
* **Submission:** The final node submitted by the participant.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/EuLXKIxI29qo8EHBDmco/47576540835604)

**Submitted nodes**

Displays a list of every selected node as well as the percentage of participants who selected it.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/fmmomcmrxcgpDYZqkYuH/47576524679828)

**Common paths**

Displays the most frequently selected paths as well as the percentage of participants that selected them.

**Start** in a path refers to the place participants begin the task, before making a selection. You'll see this in the path any time a participant navigated back to this starting point. ← indicates backward navigation.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/I1RcZOTIUvPbPP2Y38ol/47576524682260)

**Participant paths**

Displays the path selected by each individual participant.

**Start** in a path refers to the place participants begin the task, before making a selection. You'll see this in the path any time a participant navigated back to this starting point. ← indicates backward navigation.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/CQ6jOwgEcy27A82hB0ma/47576540845076)

**First click**

Displays every node that was selected first by at least one participant as well as the total number of participants who selected the node first.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/UJmaXZNUx76DaOFwilrk/47576540846740)

### Participants view

The **Participants** view gives you a closer look at individual participant responses to a tree testing question, including their submitted node, the path they took to get there, and more.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QEVIFWD83o2f4Iwok3Wq/47576524687892)

Here’s a breakdown of each metric:

| Metric             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Submitted node** | <p>The final node selected by the participant. Above the node, you’ll see a colored indicator stating whether their path to this selection was direct or indirect.</p><p><br>If your question includes a success path, you’ll see one of the following:</p><ul><li><strong>Direct success:</strong> The participant selected the correct node and only moved forward through your tree structure.</li><li><strong>Indirect success:</strong> The participant selected the correct node but moved forward and backward in your tree structure.</li><li><strong>Direct fail:</strong> The participant did not select the correct node and only moved forward through your tree structure.</li><li><strong>Indirect fail:</strong> The participant did not select the correct node and moved forward and backward in your tree structure.</li></ul><p>If your question does not include a success path, you’ll see one of the following:</p><ul><li><strong>Direct:</strong> The participant only moved forward through your tree structure before making their final selection.</li><li><strong>Indirect:</strong> The participant moved forward and backward through your tree structure before making their final selection.</li></ul> |
| **Path**           | <p>The series of nodes the participant clicked to get to their final submission. Arrows between nodes indicate where the participant moved forward or backward in your tree structure.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> <strong>Start</strong> in a path refers to the place participants begin the task, before making a selection. You'll see this in the path any time a participant navigated back to this starting point. ← indicates backward navigation.</p></div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| **Clicks**         | The number of clicks made by the participant before submitting their final response. Here, you’ll also find the average number of clicks across all participants in your study.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| **Time on task**   | The amount of time it took for the participant to submit their final response. Here, you’ll also find the average time on task across all participants in your study.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |


# Design a study

Learn about the tools and settings you can use to design a study in Dscout.

Use the links below to go deeper on each topic.

* [Screener and study templates](/study-basics/design-a-study/screener-and-study-templates)
* [Recommended study incentives](/study-basics/design-a-study/recommended-study-incentives)
* [Randomization options in Dscout](/study-basics/design-a-study/randomization-options-in-dscout)
* [Skip logic](/study-basics/design-a-study/skip-logic-in-screeners)
* [Skip logic in usability tests and media surveys](/study-basics/design-a-study/skip-logic-in-usability-tests-media-surveys-and-intercept-studies)
* [Skip logic in Dscout diary studies](/study-basics/design-a-study/skip-logic-in-diary-studies)
* [Must select logic](/study-basics/design-a-study/must-select-logic)
* [Piping recall logic](/study-basics/design-a-study/piping-recall-logic)
* [Optional pre launch review for screeners and studies](/study-basics/design-a-study/optional-pre-launch-review-for-screeners-and-studies)
* [Media limits](/study-basics/design-a-study/media-limits)


# Screener and study templates

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

{% hint style="info" %}
This article discusses templates for screeners, usability tests, media surveys, and intercept studies. For information on templates in diary studies, see [Diary study templates](/diary-studies/what-are-diary-studies-in-dscout/diary-templates-overview).
{% endhint %}

From question sets to incentives, research initiatives may share common elements. Instead of building screeners or studies from scratch every time, templates can help expedite the process. You can save existing studies as templates so you and your team can use them as a starting point for studies in the future.

## Save a screener or study as a template

If you have a screener, usability test, or media survey you want to reuse later or share with your team, you can save it as a template. Templates can then be accessed from the template library or when creating a new study.

{% hint style="info" %}
Only **Account owners**, **Admins**, and **Researchers** can save new templates. However, **Contributors** can use templates to create new screeners and studies. For more information, see [User roles and permissions](/getting-started/dscout-quickstart-guide/user-roles-and-permissions).
{% endhint %}

{% stepper %}
{% step %}
In the screener or study you want to save, click the **More actions** icon in the top right corner.
{% endstep %}

{% step %}
Select **Save as template**.

{% hint style="info" %}
A screener or study must be in **Drafting** mode in order to be saved as a template. You cannot save launched screeners or studies as templates.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/BkJGn0PzYzopkTSX37um/45260450050708)
{% endstep %}

{% step %}
Enter a **Template name**.
{% endstep %}

{% step %}
Enter a **Template description**.
{% endstep %}

{% step %}
(If applicable) Select a **Save to** location. You can either save the template to a specific workspace or make it available to everyone in your Dscout account. If your account doesn’t have workspaces, the template will automatically be saved at the account level. For more information on workspaces, see [Creating and navigating Dscout workspaces](/getting-started/workspaces-and-projects/creating-and-navigating-dscout-workspaces).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/IY7CCavzTbtDWLkPxsRz/45260446979988)
{% endstep %}

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

Now, the template is saved to your template library and will be available to you and your collaborators when creating new screeners or studies.

{% hint style="info" %}
You can also save a screener or study as a template from the project details page. Simply click the **Options** icon in the top right corner of the screener or study card then select **Save as template**.
{% endhint %}

## Create a screener or study from a template

Once a template has been saved in your Dscout account (either by yourself or one of your collaborators), you can use it to create a new screener or study. You can access all templates in the template library. Or, you can use a study template when creating a new study directly in your project.

**To use a template from the template library:**

{% stepper %}
{% step %}
In the sidebar navigation, click **Template library**. All templates in your Dscout account are displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/20AelpSr4WpzUyiSdKR2/45260450056596)
{% endstep %}

{% step %}
Locate the template you want to use to create your screener or study.
{% endstep %}

{% step %}
Click **Start from template** on the template’s card. The start from template modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/8H6GXOfv505qrSUKQMMk/45260450058644)
{% endstep %}

{% step %}
Select the **Project** where you want to create your new screener or study.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/73rfC6vJTlVC6Ua74GNn/45260450060692)
{% endstep %}

{% step %}
Select one of the following options:

* **Duplicate and modify study setup:** Copies the template’s questions but allows you to modify recruitment approach, device type, and recording options.
* **Duplicate:** Copies the template exactly as-is, including recruitment approach, device type, and recording options.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/mddUjGs2hbhD0poskIuA/45260450061588)
{% endstep %}
{% endstepper %}

If you choose to modify the study setup, you’ll be prompted to complete the initial setup flow. If you choose to duplicate the template as-is, you’ll be brought directly to the builder.

**To use a template from within a project:**

{% hint style="info" %}
To create a screener from a template, you must do so from the template library using the steps above.
{% endhint %}

{% stepper %}
{% step %}
Navigate to the **Studies** tab of your study.
{% endstep %}

{% step %}
Click **Create study**. The create something new modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/gPKjVc8U8eg8I16QSeYF/45260446991380)
{% endstep %}

{% step %}
Select **Templates** in the left sidebar. All study templates are displayed.
{% endstep %}

{% step %}
Hover over the template you want to use and click **Start from template**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Wvi9jgxTyJqCVhi64GwT/45260446994964)
{% endstep %}

{% step %}
Select one of the following options:

* **Duplicate and modify study setup:** Copies the template’s questions but allows you to modify recruitment approach, device type, and recording options.
* **Duplicate:** Copies the template exactly as-is, including recruitment approach, device type, and recording options.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/mddUjGs2hbhD0poskIuA/45260450061588)
{% endstep %}
{% endstepper %}

If you choose to modify the study setup, you’ll be prompted to complete the initial setup flow. If you choose to duplicate the template as-is, you’ll be brought directly to the builder.

## Edit a template

Template creators, Account Owners, and Admins can edit template names, descriptions, and save location directly from the template library.

{% hint style="info" %}
If you need to edit a template beyond just its name and description, use the template to create a new screener or study, make the necessary changes, and save this new screener or study as a new template.
{% endhint %}

{% stepper %}
{% step %}
In the sidebar navigation, click **Template library**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/20AelpSr4WpzUyiSdKR2/45260450056596)
{% endstep %}

{% step %}
Locate the template you want to edit.
{% endstep %}

{% step %}
Click the **Options** icon in the top right corner of the template’s card.
{% endstep %}

{% step %}
Select **Edit settings**. The template’s settings are displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7n0m5IxjZwisQEYii9sV/45260447000596)
{% endstep %}

{% step %}
Make the necessary edits.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7lEXXwsoV8Z1gv4I4f6P/45260447003156)
{% endstep %}

{% step %}
Click **Save template**.

Now, the template’s settings are updated. These changes will be reflected for all users who access the template going forward.
{% endstep %}
{% endstepper %}

## Delete a template

If you no longer need a template, you can delete it from the template library. Deleting a template has no effect on screeners or studies you’ve built using the template.

{% hint style="info" %}
Templates can only be deleted by the template creator or by an Account Owner or Admin. For more information, see [User roles and permissions](/getting-started/dscout-quickstart-guide/user-roles-and-permissions).
{% endhint %}

{% hint style="warning" %}
Deleting a template removes it for everyone in your Dscout account. Verify with your colleagues that a template is no longer needed before you delete it.
{% endhint %}

{% stepper %}
{% step %}
In the sidebar navigation, click **Template library**. All templates in your Dscout account are displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/20AelpSr4WpzUyiSdKR2/45260450056596)
{% endstep %}

{% step %}
Locate the template you want to delete.
{% endstep %}

{% step %}
Click the **Options** icon in the top right corner of the template’s card.
{% endstep %}

{% step %}
Select **Delete**. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Fq1oE6l2b4XYalWPKTV8/45260447004308)
{% endstep %}

{% step %}
Select **Yes I want to delete this template**, then click **Delete template** to confirm.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/MQgkiIOGDti6WpASJoqJ/45260447008916)
{% endstep %}
{% endstepper %}

Now, the template is deleted from your Dscout account. Screeners or studies that have been built using this template will not be affected, but the template will no longer be available for future use.


# Recommended study incentives

There are a lot of factors at play when designing research, and one of the most important questions you may ask yourself is: *How much should I pay participants?*

{% hint style="success" %}
In general, incentives should:

* **Be fair** for the effort you’re asking of participants.
* **Motivate** participants to be thoughtful and timely in their responses.
  {% endhint %}

Use this article to help determine what makes the most sense incentive-wise for your specific research.

## Incentive tips and considerations

Incentives should be part of the research conversation from the very beginning. The last thing you want to do is build out your study and then realize you don’t have the budget to entice participants. To help, here are some questions to consider:

* **What am I asking participants to do?** High-effort studies should offer higher rewards. But if your study is mostly multiple-choice questions or other behavioral commentary, you might keep it on the lower end.
* **Who am I recruiting?** If you need participants with very specific experience, like those recruited from our Partner Panels, it’ll be easier to recruit by offering a higher incentive. When you're looking for specialized roles like clinicians, engineers, or C-suite executives, expect to pay somewhere between $150 and $600 for just 15 to 30 minutes of their time.
* **When do I need the data?** If you’re on a tight turnaround, you can encourage timely completion with higher incentives (especially in diary studies).
* **How much would I expect to be paid for this study?** Take an objective look at your study and consider what it would take to get you to participate.

With these questions in mind, you’ll be well on your way to determining an incentive that is both fair and motivating for your participants.

## Baseline recommendations by study type

The sections below offer general starting points for determining incentives based on the kind of study you’re running. Usability tests, media surveys, diary studies, and interview studies all require a different level of commitment from participants, so refer to the section relevant to you for guidance.

Keep in mind that these incentives are only baselines—use your best judgment to adjust them as needed.

{% hint style="info" %}
**A note on niche recruits:** The following guidance does not apply when recruiting from our Partner Panels. Partner Panels offer access to niche, B2B recruits whose expertise is hard to source. Their schedules are tight, and the compensation you offer should reflect that. Budget accordingly.
{% endhint %}

### Usability tests

Most usability tests offer an incentive between $10 and $50. Use these specific guidelines to determine the right incentive for your study:

| Question type                                                                 | Baseline incentive |
| ----------------------------------------------------------------------------- | ------------------ |
| Every task question                                                           | $8                 |
| Every 3 talk-out-loud or open-ended questions (including card sort questions) | $5                 |
| Every 10 closed-ended questions                                               | $5                 |

### Media surveys

Most media surveys offer an incentive between $5 and $20. Use these specific guidelines to determine the right incentive for your study:

| Question type                                                | Baseline incentive |
| ------------------------------------------------------------ | ------------------ |
| Every 3 video questions                                      | $5                 |
| Every 3 open-ended questions (including card sort questions) | $5                 |
| Every 3 photo questions                                      | $3                 |
| Every 10 closed-ended questions                              | $5                 |

### Intercept studies

Intercept studies interrupt participants while they’re naturally completing another task. That’s by design so you can gather in-the-moment feedback, but you should also keep this in mind when determining an incentive. Your intercept should offer enough to make participants want to stop what they’re doing and complete the study.

**At a minimum, we recommend intercept studies offer $5 as an incentive.** Lower incentives risk lower engagement.

### Diary studies

Diary studies can sometimes span several days or even weeks, depending on what you’re researching. However, we don’t recommend basing incentives on the length of the study alone. Instead, it’s a good idea to pay on a per-activity and per-entry basis.

Most diary studies offer an incentive between $50 and $200. Use these specific guidelines to determine the right incentive for your study:

| Study component                                    | Baseline incentive |
| -------------------------------------------------- | ------------------ |
| Every activity                                     | $10                |
| Every additional entry (in a multi-entry activity) | $5                 |

So, let’s say your study has three activities, but the third activity requires two entries. The math for that would look like this:

* Activity 1: $10
* Activity 2: $10
* Activity 3: $15 ($10 for the activity and an additional $5 for the second entry)
* **Base study incentive:** $35

### Interview studies

Participating in interview studies involves the extra effort required to schedule a session and sit down for a one-on-one conversation. So, it’s a good idea to offer a slightly higher incentive for these studies. Consider the intended length of your sessions and go from there:

| Session length | Baseline incentive |
| -------------- | ------------------ |
| 30 minutes     | $50                |
| 60 minutes     | $75-100            |


# Randomization options in Dscout

Randomization can help minimize participant bias by ensuring that your concepts, questions, or even answer choices are not always presented in the same order. Dscout offers several ways to incorporate randomization into your studies. Use the sections below to find the best option (or options!) for your research.

## Multi-variate testing

Randomize up to three concepts, designs, or stimuli in one study with multi-variate testing. Maybe you’re testing different prototypes, each with several related follow-ups. With multi-variate testing, you can easily group questions by variant and then automatically randomize how participants see those variants.

Multi-variate testing also gives you the chance to show only one of your variants at random to each participant while ensuring even distribution across everyone you invite. Want to compare how users interact with two different versions of your website? Multi-variate testing can help.

For more information, see [Multi-variate testing](/study-basics/question-types/multi-variate-testing).

## Question groups

Question groups are similar to multi-variate testing—without the variants. If you have one set of related questions you want to keep together, you can add them to a question group. You then have the option to randomize all of the questions in that group when they’re presented to participants.

For more information, see [Question groups](/study-basics/question-types/question-groups).

## Randomized stimuli

If you're displaying images or other pieces of stimuli to participants, randomizing them can help prevent bias in your responses. You can enable randomized stimuli at the question level in certain study types, ensuring your participants see the attached files in a random order every time. For more information, see [Question stimuli](/study-basics/question-types/question-stimuli).

## Randomized answer choices

Sometimes, even the smallest bits of randomization can make a world of difference. So, Dscout lets you randomize the answer choices on many closed-ended question types. You’ll find this in obvious places like multiple choice questions, but you’ll also find it in places like card sorts where you can choose to randomize both the cards and the categories, ensuring no participant is influenced by the order in which you initially write your questions.


# Skip logic in screeners

With skip logic in screeners, you can jump participants to different questions based on their answers to a previous question.

In the example question below, the question workflow will work as follows:

* Participants who select "Always" or "Often" will be skipped to Q4
* Participants who select "Sometimes" will be skipped to Q7
* Participants who select "Rarely" or "Never" will move on to the next question (Q3)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/zkVXO5JTlt8v9bcRQqZc/21709631260180)

To add or edit skip logic, click the curved grey arrow next to the answer(s) to direct participants to the question they should see next:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/czg5cFNSpK8CRf3jK8ow/21709654645524)

{% hint style="info" %}
**Note:** Selecting "End" on Skip logic does not operate as a knockout question. Skip to End should be used when a participant, based on that response, does not need to answer the remaining questions in the study or screener. This means the participant qualifies and their application is considered complete if they're skipped to the end. In diary studies, usability tests, and media surveys, this is a way to build in "optional" questions.
{% endhint %}

Skip logic can be applied to any [question type](/recruit-participants/what-are-dscout-screeners/question-types-in-screeners).


# Skip logic in usability tests, media surveys, and intercept studies

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

With skip logic in studies, you can jump participants to different questions based on their answers to a previous question.

In the example question below, only participants who select "Outside of my bedroom" will see Question 2, the relevant open-ended question that comes next. Those who do not will skip to Question 3.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/xlwwOIkW8A328IS5W2FS/18354226977044)

If including skip logic to an answer option, click the skip logic icon next to the individual answer option to apply skip logic. If include skip logic at the question level, click the skip logic icon above the question prompt to direct participants to the question they should see next.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/iekIKK7p22OMEZn68kgb/18354194118932)

Skip logic can be applied to any question type in a usability tests or media survey, with the exception of Checkpoint questions. Multi-select questions can not include multiple skip-logic paths.


# Skip logic in diary studies

With skip logic, you can jump scouts to a particular question based on their response choice.

In the example question below, only scouts who choose "in the water" will see the relevant short response question that comes next.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/p05MqQE5OqV74EEmQZOp/360048963331)

When editing a question with skip logic, just click the grey arrow next to individual answers (or the question prompt!) to direct scouts to the question they should see next.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/mf8KrGaBxlYF7Smc4e4m/360048834572)

* Skip logic can be applied to all question types.
* Multiple select questions **can not** skip to different question paths (i.e., if option A skips to question 3, option B **can not** skip to question 5). This is because the platform won't know what to prioritize if a scout chooses multiple options that skip to different questions.
* Write all your questions first, *then* define your skip logic afterwards. Moving questions around after defining your skip logic will cause the skip logic to break (disappear), and you'll have to define it again. And we don't want that.
* You're **not** able to program skip logic on the last question in a study. To activate skip logic on a question you just created, move it up in the question script.


# Must select logic

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

**Must-select can be set on Multiple Select questions.** Use this logic to designate response choices participants must select to qualify.

All choices pre-populate as ‘May Select’, which means that participants may select that answer choice to continue. If participants must select an answer choice to continue, or if participants should be knocked out for selecting an answer choice, click on the arrow in the box next to that answer choice to change the applied logic. You can designate ‘Must Select’, ‘May Select’, and ‘Knockout’, and logic must be applied to all answer choices.

{% hint style="info" %}
**Note:** Knockout logic takes priority and will disqualify participants (in the example below, someone who chooses "French press" *and* "Drip coffee maker" will still be disqualified).
{% endhint %}

Per your selection, participants must choose at least one OR all must-select choices to qualify. Logic doesn’t need to be applied to all choices.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/o7Kol8ZV16faercMF1bL/13831521830804)


# Piping (recall) logic

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr><tr><td><strong>Diary studies</strong></td><td>false</td></tr></tbody></table>

Piping logic, also known as recall logic, lets you dynamically reference a participant’s answer from a previous question into a later question. This keeps your studies feeling custom, personalized, and engaging.

Maybe you’ve asked participants their favorite fruit. Later, instead of asking every participant generically, “Why is that your favorite fruit?” you can use piping logic to insert their indicated favorite directly into the question. For example, if one participant indicates strawberries are their favorite fruit, you can automatically ask them “Why are strawberries your favorite fruit?” thanks to piping logic.

{% hint style="info" %}
Piping logic in Dscout is different from branching studies. For information on how to send participants to certain questions depending on their answers, see [Skip logic](https://help.dscout.com/hc/en-us/articles/360038668491).
{% endhint %}

## Add piping logic to a question

You can add piping logic to any question type, including photo and video questions. However, you can only pipe responses *from* closed-ended question types:

* Multiple choice
* Ranking
* Scale
* Number

{% hint style="info" %}
You cannot recall answers from a question that already uses piping logic. For example, if Question 2 recalls a response from Question 1, you cannot recall a response from Question 2 in another question.
{% endhint %}

{% stepper %}
{% step %}
In your study, add your source question (the question you want to recall an answer from).
{% endstep %}

{% step %}
Add your destination question (the question where you want to recall responses from your source question).
{% endstep %}

{% step %}
In the prompt of your destination question, type an **@** symbol. A list of available questions is displayed.
{% endstep %}

{% step %}
Select your source question from the list.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/zUSF1AFHZBBEfkjqK3hk/39869997411220)
{% endstep %}

{% step %}
Type the rest of your question.
{% endstep %}

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

Now, when you launch your study, participants’ responses from your source question will automatically be placed where you’ve inserted piping logic into your destination question.

{% hint style="success" %}
“Other” responses can be recalled with piping logic. They’ll be added to your destination question exactly as entered by the participant. However, we do not recommend allowing for “None of the above” options in source questions as piping this response will likely not work in the context of your destination question.
{% endhint %}

## View piping logic in analysis

When viewing responses, you’ll see piping logic displayed in one of two ways.

Viewing responses at the question or activity level, you’ll see your source question mentioned in the prompt of your destination question:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/rSQdbHFLRKi4DHJgLQhz/47543333145748)

However, viewing responses at the participant level, you’ll see that participant’s piped response anywhere you’ve used piping logic:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ksonUmcxQoN8EUL6ed50/47543368336276)


# Optional pre launch review for screeners and studies

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

When building a screener, usability test, or media survey, you have the option of submitting them for review by a Dscout Research Advisor prior to launch. Having your screeners and studies reviewed before opening them to participants can help ensure you get the most effective responses and that your participants have the best experience.

{% hint style="info" %}
**Note:** Screeners should be just long enough to determine whether an applicant is a fit for your study. So, screeners that present applicants with more than 20 questions cannot be launched without being submitted for a pre-launch review.
{% endhint %}

Reviews can take up to two business days. However, we understand different projects call for different timelines, so these reviews are optional in many cases. If you don’t see the option to skip this review, it may not be available in your organization’s Dscout account. Contact your Dscout administrator or account manager for more information.

{% hint style="success" %}
**Tip:** If you choose to launch your screener or study without submitting it for review, refer to our our [Screener review checklist](https://help.dscout.com/hc/en-us/articles/13167502742548) and [Project review checklist](https://help.dscout.com/hc/en-us/articles/360038414832) to make sure you’ve covered all the essentials.
{% endhint %}

**To submit a screener or study for review:**

{% stepper %}
{% step %}
In the builder, click **Launch** in the top-right corner. A modal opens displaying your review options.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/RMl0TDDLqzxlovII3twB/39583985491988)
{% endstep %}

{% step %}
Select **Submit for review**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/gjXuu6PAZq9gtBWL2uHq/34944888567188)
{% endstep %}

{% step %}
Click **Continue.** A modal opens requesting a few more details about your screener or study.
{% endstep %}

{% step %}
Enter your intended **launch date**. This must be at least one business day from the date you’re submitting. And keep in mind that your selection here will not guarantee a faster review.
{% endstep %}

{% step %}
Enter a sentence or two into the provided text box. Let our Research Advisors know about your project goals or anything you want specific feedback on.

<div align="left"><img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/FaIh5v77vtYhTisliEln/34944851955604" alt=""></div>
{% endstep %}

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

Next, a Research Advisor will review your screener or study as soon as possible—within two business days at the very latest. You’ll receive an email once the review is complete and find the Research Advisor’s feedback via comments in the builder.

![Optional\_review\_04.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/l4yVDPBZAGvJQJs5oGj2/34944888569876)

Once you’ve resolved any issues, give your screener or study one last glance. Then, click **Launch** in the top-right corner of the builder to open it to participants.

![Optional\_review\_05.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/hhvyhFuSfMTUbuYm65SZ/34944888571540)

For information on selecting participants based on screener responses, see [Viewing applications and selecting participants](/recruit-participants/what-are-dscout-screeners/review-screener-responses).


# Media limits

Make your research resonate with real moments from real customers, using Dscout's expansive media collection capabilities.

The Dscout platform offers a robust suite of media question types for screeners, usability tests, media surveys, and diary activities. These include photos, videos, screen recordings, and task questions. Media limits vary across Dscout products.

## Screeners

* Participants can submit up to 1 photo and 1 video response.
* Videos (selfie, outward facing, or screen recording) can be a max of 1 minute.

  ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/bs2UzJqvy7NV8j5jVvcQ/13824896245780)
* As a best practice, we do not recommend the use of screen recordings in screeners as they are often more personal, and may be difficult for less tech-savvy participants.

## Media surveys

* Participants can submit *unlimited* photos. Each photo question in your study can collect a *single photo*. If you’d like to collect multiple photos, include a separate photo question for each photo upload. Participants cannot upload multiple photos to a single photo question.
* Media surveys can include up to 3 videos (selfie, outward facing, or screen recording) and can be a max of 2 minutes in length.

## Usability tests

### Desktop usability tests

* Desktop usability tests are continuously recorded, so there are no separate video or photo upload questions. Your study will capture the participant’s screen throughout the duration of the study. You can choose whether to record the participant’s face throughout the study.
* Alternatively, you may use the Talk Out Loud question type to approximate participants responding to a video prompt.
* Desktop usability tests can include up to 15 [task questions](/study-basics/question-types/task-questions).

### Mobile usability tests

* Mobile usability tests are continuously recorded, so there are no separate video or photo upload questions. Your study will capture the participant's screen throughout the duration of the study.
* Mobile usability tests will record for up to 40 minutes. Anything after 40 minutes will not be recorded, even if your participants are still completing the study.
* Mobile usability tests can include up to 15 [task questions](/study-basics/question-types/task-questions).

## Diary studies (mobile + desktop)

* Participants can submit up to 5 photos and 3 video responses per activity.\
  \
  **Note:** Participants can only upload one photo per photo prompt. Include a unique photo prompt for each photo you'd like participants to upload, up to 5.<br>
* Videos (selfie, outward facing, or screen recording) can be a max of 5 minutes.

If you have surpassed the media limitations in a specific Dscout product, you will see a validation pop-up. You must remove the excess media before submitting your screener or study for review (screeners, usability tests, and media surveys) or launching your study (diary studies).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/bs2UzJqvy7NV8j5jVvcQ/13824896245780)

**Pro tip!** Media limits enforce the number of photos/videos a participants can submit in an entry, but does not dictate the total number of media prompts you can include in your screener, usability test, media survey, or diary entry script.

Use skip logic to split participants into multiple tracks of questions – each of which can have a unique video & photo questions.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/sWwE3u7e4skZsQPTweWb/13824901033620)

In the example media survey above, participants A & B get skipped to different video prompts depending on their response to the multiple choice question. There are a total of six unique video prompts in this study, but since each participant only answers three videos in the course of completing their entry, this research design still fits within Dscout's media limits.


# Testing prototypes

Learn how to set up, prepare, and analyze prototype tests in Dscout.

Use the links below to go deeper on each topic.

* [Add a figma prototype to a study](/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study)
* [Prepare a figma file for a Dscout study](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study)
* [Analyze heat maps and click data](/study-basics/testing-prototypes/analyze-heat-maps-and-click-data)


# Add a Figma prototype to a study

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

When conducting studies, it can be useful to have participants interact directly with a website or prototype to get a sense for what they like or dislike, what design elements are working, or what could be improved.

To make sharing prototypes easier, you can embed links to prototypes directly in task questions. Then, when participants reach these points in your study, the prototype will open automatically.

{% hint style="info" %}
Before adding your Figma prototype, it’s important to optimize it for use by participants. For more information, see [Preparing your Figma file for testing](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study).
{% endhint %}

## Add a prototype to a study

You can add a Figma prototype to a study at the study level or through individual task questions. Either way, once you’ve added a prototype once, you can use it in multiple questions throughout your study.

{% hint style="warning" %}
Prototype files must be 100 MB or smaller to be used in studies.
{% endhint %}

**To add a prototype at the study level:**

{% stepper %}
{% step %}
On the **Usability test/Study** tab of your study, click the **Task URLs** button in the top right corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7jFsNflAtZzMOIZTg2iM/37450774946708)
{% endstep %}

{% step %}
Click **+ Add task URL**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/9MZiRZHsB3oKVlNdiEn4/41982317606804)
{% endstep %}

{% step %}
Select **Figma prototype**.

If you haven’t already, you’ll be prompted to connect Dscout to your Figma account. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration).

{% hint style="info" %}
If you're using a Figma Make prototype, first [publish](https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app) your prototype in Figma Make. Then, add the provided URL as a **Website**. Heat maps are not generated for Figma Make prototypes.
{% endhint %}
{% endstep %}

{% step %}
Enter the **URL** for your prototype. This should be the share link for your prototype, not the link to your overall Figma design file.

{% hint style="info" %}
We recommend setting your Figma share settings to **Anyone with the link** to ensure participants can access your prototype. For more helpful tips, see [Preparing your Figma file for testing](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study).
{% endhint %}
{% endstep %}

{% step %}
Click **Add**. Depending on the size of your prototype, the connection may take a minute or two. When the prototype is connected, you’ll see the name of your prototype and a chip indicating it is **Connected**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/trLZLXZu3ULdKitDX9cu/41982330982932)
{% endstep %}

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

Now, the prototype is added to your study and you can use it when adding new task questions. Simply click **Add** beside **Task URL**, then select from the list of **Previously added** prototypes. For more information, see [Task questions](/study-basics/question-types/task-questions).

**To add a prototype using a task question:**

{% stepper %}
{% step %}
On the **Usability test/Study** tab of your study, click **Add** in the center of the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/IwFB8yAzZJ3GIVOsWpFa/37450774951956)
{% endstep %}

{% step %}
Under **Usability**, select **Task**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/UzZyeA1WMi9qFZqPNBO9/37450801448852)
{% endstep %}

{% step %}
Enter the **Task** prompt or instructions.
{% endstep %}

{% step %}
Click **Add** beside **Task URL**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cemy59SfyQn9r862TlqN/37450774953620)
{% endstep %}

{% step %}
Select **Figma prototype**. (Or, select from the list of **Previously added** prototypes to use one that’s already in your study.) If you haven’t already, you’ll be prompted to connect Dscout to your Figma account. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration).

{% hint style="info" %}
If you're using a Figma Make prototype, first [publish](https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app) your prototype in Figma Make. Then, add the provided URL as a **Website**. Heat maps are not generated for Figma Make prototypes.
{% endhint %}
{% endstep %}

{% step %}
Enter the **URL** for your prototype. This should be the share link for your prototype, not the link to your overall Figma design file.

{% hint style="info" %}
We recommend setting your Figma share settings to **Anyone with the link** to ensure participants can access your prototype. For more helpful tips, see [Preparing your Figma file for testing](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study).
{% endhint %}
{% endstep %}

{% step %}
Click **Add**. Depending on the size of your prototype, the connection may take a minute or two. When the prototype is connected, you’ll see the prototype's name and connection status.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/trLZLXZu3ULdKitDX9cu/41982330982932)
{% endstep %}

{% step %}
Configure any other required settings for your task question. For more information, see [Task questions](/study-basics/question-types/task-questions).
{% endstep %}

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

Now, you’ve successfully added a prototype using a task question. The URL for this prototype will also be accessible in your entire study so you can add it to subsequent questions if needed.

Once you’ve added your prototype, you can also select a screen where you want participants to start as well as a screen that indicates successful completion of the requested task in your prototype.

## Prototype settings

### Starting screen

By default, prototypes will open on the starting frame set within your Figma file. However, you can customize the starting screen for each individual task question in your study. So, if you use one prototype for multiple tasks, you can have each of them start on a specific screen instead of all the way at the beginning of your prototype.

{% stepper %}
{% step %}
Navigate to the task question where you want to set a starting screen.
{% endstep %}

{% step %}
Under **Task flow**, hover over the image beneath **Starting screen** and click **Edit**. The **Select starting screen** modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/WhgMGsy2lfqOck2qyXXX/41982330984340)
{% endstep %}

{% step %}
Use your keyboard’s arrow keys to navigate through your prototype to find the screen you want. If you want to go back to the beginning at any point, click the **R** key.
{% endstep %}

{% step %}
Once you’ve found the screen where you want this task question to start, click **Save as starting screen**. Your selected screen will now display beneath **Starting screen** when editing your question.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/mBWZYVXGUIj15pyvA9Tr/37450801451924)
{% endstep %}

{% step %}
Click **Done** to save the task.
{% endstep %}
{% endstepper %}

Now, when participants reach this task question, the prototype will open on your designated starting screen rather than the default starting frame of your Figma file. This helps ensure participants all begin each task on the same page—literally.

### Success screen

In addition to setting a starting screen, you can also select a specific screen of your prototype that, when reached by a participant, indicates they were able to successfully complete what you asked them to do. You’ll be able to see which participants reached this success screen during analysis.

{% stepper %}
{% step %}
Navigate to the task question where you want to set a success screen.
{% endstep %}

{% step %}
Under **Task flow**, click **Add** beneath **Success screen**. The **Select success screen** modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Wv0HawgcV79vVLd3wtfc/41982330985876)
{% endstep %}

{% step %}
Use your keyboard’s arrow keys to navigate through your prototype to find the screen you want. If you want to go back to the beginning at any point, click the **R** key.
{% endstep %}

{% step %}
Once you’ve found the desired screen, click **Save as success screen**.

Your selected screen will now display beneath **Success screen** when editing your question.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/jkMNwSworT6Q4lgG6ZIr/37450774957588)
{% endstep %}

{% step %}
Click **Done** to save the task.
{% endstep %}
{% endstepper %}

Now, when participants reach the success screen during the task, this data will be included in their response and you’ll be able to see it during analysis.

### Scaling

Depending on what you're designs are emulating (an app or a website, for example), the size of your prototype may vary. With scaling options, you can determine how your prototype is displayed to participants. To access these settings, click the **Prototype settings (gear)** icon on your prototype. Then, select whether your prototype has a device frame or not:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7nLQfE46PF1S0xBvlEFn/41991323665812)

{% hint style="info" %}
For more information on scaling options, see Figma's [Play your prototype](https://help.figma.com/hc/en-us/articles/360040318013-Play-your-prototypes#h_01HER6XXFTAK565E14WGYEM4T4) article.
{% endhint %}

Selecting **Without a device frame** displays the following **Scaling** options:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dawizsNivTKFSY9c8Hjt/41991323669524)

| Setting                  | Description                                                                                                                                                                                                                                                              |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Actual size (100%)**   | Displays the prototype based on the full size of the design frame. Depending on the frame and the screen size, this may result in a cropped prototype.                                                                                                                   |
| **Fit width and height** | Shrinks the prototype so that both the width and the height fit within the viewer window. It will not scale up the prototype.                                                                                                                                            |
| **Responsive**           | Resizes and re-layouts the prototype with the participant based on applied constraints and auto layout settings. This lets you test designs at different window sizes for responsiveness. For Responsive behavior, constraints and auto layout must be applied in Figma. |
| **Fit width**            | Scales the prototype so it fills the width of the display.                                                                                                                                                                                                               |
| **Fit screen**           | Scales the prototype horizontally and vertically so that it fills the entire display. It will not overflow any content of the design.                                                                                                                                    |

Selecting **With a device frame** displays the following **Scaling** options:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ypXKXsRyZf2HcxFjI5TO/41991339746580)

| Setting                        | Description                                                                                                                                                                                                                                                              |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Responsive**                 | Resizes and re-layouts the prototype with the participant based on applied constraints and auto layout settings. This lets you test designs at different window sizes for responsiveness. For Responsive behavior, constraints and auto layout must be applied in Figma. |
| **Fit device on screen**       | Shrinks the device frame so that it fits within the participant's window.                                                                                                                                                                                                |
| **Zoom device to fill screen** | Scales the device so that it fills the entire display.                                                                                                                                                                                                                   |

### Advanced settings

Dscout offers additional prototype settings to control how your participants can interact with your designs. To access these settings, click the **Prototype settings (gear)** icon. Then, select whether your prototype has a device frame or not:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7nLQfE46PF1S0xBvlEFn/41991323665812)

The following options are displayed:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/RunW2FnliUE1HOmlWsL9/41991323680660)

| Setting                       | Description                                                                              |
| ----------------------------- | ---------------------------------------------------------------------------------------- |
| **Hide Figma UI**             | Turns off all Figma interface elements such as the bottom toolbar and navigation arrows. |
| **Hide Figma hints on click** | Hides visual cues that indicate which areas of your prototype are interactive.           |
| **Enable Figma shortcuts**    | Allow users to navigate your prototype using keyboard shortcuts.                         |

## Re-sync a prototype

To generate [heat maps](/study-basics/testing-prototypes/analyze-heat-maps-and-click-data), Dscout relies on the most recently synced version of your prototype. So, if you make updates in Figma you want reflected in the heat maps generated by Dscout, you’ll need to re-sync your prototype. **Re-syncing a prototype does not impact the participant experience in any way as they will always be directed to the most up-to-date version of the prototype linked in the study.**

{% hint style="info" %}
Prototypes are only synced if you have the Figma integration enabled. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration).
{% endhint %}

### To re-sync a prototype

{% hint style="warning" %}
Only re-sync a prototype if critical changes have been made *and* if no participants have completed the study using the old version of your prototype. Doing so can cause inconsistencies in your data during analysis.
{% endhint %}

{% stepper %}
{% step %}
On the **Usability test/Study** tab of your study, click **Task URLs**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7jFsNflAtZzMOIZTg2iM/37450774946708)
{% endstep %}

{% step %}
Click the re-sync button beside the prototype. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/r30I1wulQ3Nxchk0Hhk3/41982330986516)
{% endstep %}

{% step %}
Click **Re-sync Figma prototype** to confirm.
{% endstep %}
{% endstepper %}

Now, Dscout processes your prototype again, re-syncing with the latest version for use when generating heat maps and click event data.

{% hint style="info" %}
If you encounter any issues when adding a Figma prototype to a task question, check out our [Figma Troubleshooting Guide](/integrations/figma-integration/troubleshooting-a-figma-prototype) for help.
{% endhint %}


# Prepare a Figma file for a Dscout study

*This article outlines recommendations and best practices for preparing Figma files for **unmoderated studies**. While you may find some of this guidance helpful for testing Figma files in interview studies, some of the settings and recommendations outlined here will not apply.*

{% hint style="info" %}
**Note:** The guidance in this article applies to traditional Figma prototypes. It does not apply to prototypes created with Figma Make. To test a **Figma Make** **prototype** in Dscout, first [publish](https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app) the prototype in Figma Make. Then, add the provided URL as a **Website** in your task question.
{% endhint %}

When you link a Figma prototype in a Dscout study, all frames and pages within that file have to be loaded and processed. This might cause importing issues, or make your prototype slow to load and respond for your testers.

We highly recommend following these steps to create a dedicated and optimized testing file:

## Create a dedicated testing file

We highly recommend [duplicating](https://help.figma.com/hc/en-us/articles/360038511533) your prototype into a dedicated testing file to ensure successful loading and processing. Before adding your prototype link, exclude pages and frames that are not relevant to your test and avoid using sections unless needed for prototyping. This will create a lightweight file to improve load times and reduce errors.

{% hint style="info" %}
**Note:** 100 MB is the maximum supported file size.
{% endhint %}

You will also want to add a note to your duplicated test file stating that it is linked to a Dscout study to prevent changes from being made to the file.

## Naming your frames, layers, and components

Give your frames, layers, and components easy-to-identify names to get the most out of your prototype test. Analyzing click maps and click events is much easier with well-named layers.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1kkAkyeSm3SLaTyh45UL/32524108306452)

## Set a prototype flow starting point (required)

In order to add your prototype to Dscout, your prototype must have a flow starting point. Learn more about how to set a starting point here: [Figma - Flow starting points](https://help.figma.com/hc/en-us/articles/360039823894-Create-and-manage-prototype-flows#h_01HNZT1ATPZP0EAWCQH90CXE42).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ZMBrziEcEVajRCTJOUAn/32524108310932)

## Optimize your prototype

Avoid importing issues and slow loading for participants by optimizing your prototype design.

* Compress your images before uploading them to Figma. Images are not compressed automatically by Figma, and uncompressed images can lead to large file sizes.
* Convert vectors to JPG images
* Use Smart Animate sparingly
* Remove all pages from your file except for the page that contains the prototype you are using in your study
* Limit the size and number of frames to only include the frames that are necessary for the study

## Avoid overlapping layers and scroll frames

To capture click data for the entire screen, avoid overlapping layers and placing *scrolling* frames on top of other frames. Double-check that any scrolling frames are cropped to match the width of their content and do not overlap other components, frames, or layers on your screen. See the example below.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/t8NQYrb8IBDT27vXMUqV/32524108313364)

## Recommended prototype options

Before grabbing the link to your prototype to put into Dscout, double-check your prototype options.

* Adjust how you want participants to view your prototype:
  * For desktop, we recommend **Fit width**
  * For mobile, we recommend **Fit width and height**
* Additionally, we recommend turning on the option to **hide Figma UI**. This will prevent your participants from navigating to other flow starting points or paging through your screens via Figma’s navigation arrows.
* Depending on your prototype and study design, you may want to also modify the prototype options to **enable Figma shortcuts** and **show hints on click**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/RWxGMwlH1OmtEnjSxiiB/32524108317716)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/gnhia0b1jNBsuGdW7LvG/32524099247380)

## Mobile prototype tip - preview your mobile prototype

Always check your mobile prototype on your mobile device ***before*** launching your study. To do this:

* Click the “Share prototype” button in presentation mode
* Copy the prototype share link
* Paste the prototype share link into your mobile browser

Your mobile prototype will load for participants inside of a regular mobile browser window, so the browser's header and footer will still be visible. Checking the prototype on your device will help ensure that it’s behaving correctly with the browser UI present.

## Share link settings and permissions (required)

Before directing participants to a Figma prototype, make sure they can access it. We recommend setting your share permissions to **Anyone with the link can view** in Figma. However, Dscout does support password-protected Figma files in both mobile and desktop studies.

{% hint style="success" %}
**Tip:** When testing a password protected Figma file, be sure to include the password in the prompt of the related question in your study so users can access it when needed.
{% endhint %}

If you are inviting your own participants, double-check your share settings to ensure those you invite can access your prototype. If you plan to share privately, make sure your participants have all been invited to view it.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dsXNTTghu36NKSpfoLFx/32524099249556)

## Sharing your Figma prototype (required)

Now that your Figma file is ready, it is time to share your prototype with the correct settings. **It is important that you copy the prototype link in Figma, rather than the file link.**

{% stepper %}
{% step %}
From your design file, select **Present** in the toolbar.
{% endstep %}

{% step %}
Once you’re in the presentation view, click **Share prototype** in the toolbar.
{% endstep %}

{% step %}
From the Share prototype modal, confirm you have the correct access settings (Anyone with the link is recommended).
{% endstep %}

{% step %}
Update or confirm your prototype options.
{% endstep %}

{% step %}
From the Share prototype modal, click **Copy link** to copy the prototype’s URL.
{% endstep %}

{% step %}
You can now add the copied link to a task question in Dscout.
{% endstep %}
{% endstepper %}


# Privacy blur

Usability tests and intercept studies let you record participant screens throughout an entire study. But in some cases, you may ask your participants to do something that exposes PII (personally identifiable information). You can still get the insights you need while maintaining their privacy by enabling privacy blur. With privacy blur enabled, you’ll still be able to hear participants’ audio but their screen will be blurred in their final response.

{% hint style="info" %}
**Note:** Heat maps and click data are not affected by the Privacy blur setting. This setting only blurs the participant's screen during analysis. Any task data that would normally be collected will still be collected.
{% endhint %}

Privacy blur is available on the following question types:

* Task.
* Instructions (checkpoint).
* Talk out loud.

Here’s how questions with privacy blur look when analyzing study responses:

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FElgli3XP1so5ROES2wSC%2Fimage.png?alt=media&amp;token=8e735087-c00a-4dab-9c8e-b8b9469ffcc9" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** If you’ve chosen to record a participant’s camera and their screen, you’ll still be able to see their camera in their response. Only the participant’s screen will be blurred.
{% endhint %}

**To enable privacy blur on a question:**

{% stepper %}
{% step %}
In your study, add or navigate to the question you want to blur. You can enable privacy blur on task, instructions, or talk out loud questions.
{% endstep %}

{% step %}
Under **Question settings**, toggle **Privacy blur** on.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FstcBglVoJ6MGbVAwkS1N%2Fimage.png?alt=media&amp;token=079f3367-c0b2-43a9-9f35-7757df747778" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Tip:** Give your participants a heads up that a question will be blurred by including a note in the prompt. For example, *Note: The recording of your screen will be blurred for your privacy. Please navigate away from any sensitive information upon completing the task.* You can see this in the screenshot below.
{% endhint %}

Questions with privacy blur enabled will include a **Privacy blur** chip in the builder:

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FqLEpxgUFvIExkJdZEjV6%2Fimage.png?alt=media&amp;token=c21182c0-1c1c-4383-b13c-9c2feb4bb5fb" alt=""><figcaption></figcaption></figure>


# Analyze heat maps and click data

Desktop usability tests and intercept studies can generate heat maps and click data based on participant submissions to task questions.

{% hint style="info" %}
**Note:** Heat maps are only generated when using a traditional Figma prototype (not a website or Figma Make prototype). However, basic click data can be collected when using a website URL. For more information on task question settings, see [Task questions](/study-basics/question-types/task-questions).
{% endhint %}

## Requirements to generate heat maps

* Heat maps only work with Figma prototype URLs.
* Heat maps are only available for [**task questions**](/study-basics/question-types/task-questions).
* Once a Figma prototype has been introduced to participants through a task question, all **subsequent tasks** where participants have access to the prototype will generate heat maps as long as at least one participant interacts with the prototype during the duration of that task.
* You must [connect your Figma account](/integrations/figma-integration/set-up-the-figma-integration) to Dscout to see heat maps.

## Viewing heat maps

If the above criteria are met, heat maps will be available **in the analysis for that task.** To view a heat map, select the **Heat maps** tab in your task analysis.

Here, you'll find thumbnails of each frame visited by your participants. If a frame was not visited by any participants during the duration of the study, it will not be included in the heat map.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/WSMVjetNZ4dkJxp7benj/47543344547732)

Clicking on a thumbnail will open up a modal that shows a heat map representing the density of clicks from all participants.

* Red = more clicks
* Lighter blue = fewer clicks

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/64u3WA6j54rOqZBISGlp/47543344549012)

## Navigating the heat map

Once you open a thumbnail to view the heat map, you can zoom in on the heat map and scroll to focus your view.

On the left sidebar, you can select a different heat map frame to view.

You can hover over an area of the heat map or on a click area in the **Click areas** sidebar to see the following details on the heat map: the click area outlined in blue, the click area title (Figma layer that was clicked), and the number of clicks across participants for that click area. The order of the click groups is determined by the Figma design file. Learn more about Click areas below.

You can filter the data being displayed in the heat map using the Filters icon. If filters are applied, the heat map will show the filtered participant view with an updated participant count (for example, 15/24 participants).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/lyOrBjc60faMLAVVt35N/47543351388948)

### Click areas

Clicking on an area of a heat map or on a click area in the sidebar will bring that area into focus. In this selected state:

* The click area (in the right sidebar) will expand to show all participants who clicked in that area.
  * Clicking on a participant within a click area opens their session recording in a new tab at the moment of this click.
* The Heat map also highlights the click area(s). You can hover over the click areas to further explore the number of clicks by participant for that click area.

To exit the Click area focused view, click anywhere on the heat map, the “x” button on the click area label, or select a new click area in the sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/orfSkqYy5nRoZTQcnlHa/47543344553492)

### Viewing click data in the Clicks tab

If you select a participant in the Click areas sidebar, you will be navigated to the participant’s full video session at the moment of that click. A **Clicks** tab will appear in the right sidebar with all of the click events from that prototype for that participant. The **Clicks** tab will show the timing of each click and the name of the Figma design element that was clicked. If you did not connect a Figma account prior to launching the study, the clicks will be labeled “clicks,” and no specific element will be shown.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/CuRvnccuogc1UI5juDzf/21550925039764)

## Exporting your Heat maps

Heat map thumbnails can be exported as a PNG file using the export button on each thumbnail.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aTgC4Zu3xJw9MITf9xa7/47543344555028)

You can also export click data and task data from your usability test. For more information, see [Export usability test data](/usability-tests/analyze-a-usability-test/export-usability-test-data).


# Edit, close, or relaunch studies

Manage launched and closed studies from one place.

Use the links below to go deeper on each topic.

* [Edit a launched screener or study](/study-basics/edit-close-or-relaunch-studies/edit-a-launched-screener-or-study)
* [Close a study](/study-basics/edit-close-or-relaunch-studies/close-a-study)
* [Relaunch a closed screener or study](/study-basics/edit-close-or-relaunch-studies/relaunch-a-closed-screener-or-study)


# Edit a launched screener or study

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr></tbody></table>

Sometimes, you might want to see how a screener or study performs with actual participants before opening it to a larger group. Getting responses from only a few people can help gauge whether your questions are clear, whether responses are proving insightful, or whether you need to make any adjustments. Consider this a sort of “soft launch,” a way to perfect your research before receiving the bulk of your data.

{% hint style="info" %}
Usability tests and media surveys also offer test mode, which lets you gather sample data that is then deleted when you launch your study. For more information, see [Test a usability test study](/usability-tests/create-a-usability-test/test-a-usability-test) or [Test a media survey](/media-surveys/create-a-media-survey/test-a-media-survey).
{% endhint %}

Once you’ve received one or two responses, you can then make modifications to your research, adjust your participant limit to match your target n-size, and publish your changes to new participants.

{% hint style="warning" %}
While you can edit a screener or study regardless of your initial participant limit, making edits will split your data when viewing responses. This can make analysis difficult if you edit a study after receiving a large number of responses you want to view all at once.
{% endhint %}

## What can be edited post-launch?

There are a few restrictions to what can be edited post-launch. Refer to the sections below to learn more about what can and can’t be changed in screeners and studies.

{% hint style="warning" %}
Consider how crucial an edit is to your study before you make it and only proceed if the edit is necessary. Keep in mind that edits may split your response data. If you want to keep all responses in a single view, consider duplicating your study and re-launching instead of editing your launched study.
{% endhint %}

### Screeners

Here’s a breakdown of what can and can’t be edited after launching a screener:

| Can be edited                                                                                                                                                                                                | Can't be edited                                            |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
| <ul><li>Hero image.</li><li>Screener description.</li><li>Screener teaser.</li><li>Targeting attributes.</li><li>Question prompts, question settings (unless otherwise noted), and answer choices.</li></ul> | <ul><li>Incentive.</li><li>Recruitment approach.</li></ul> |

### Studies

Here’s a breakdown of what can and can’t be edited after launching a usability test, media survey, or intercept study:

| Can be edited                                                                                                                                                                                                             | Can't be edited                                                                                                                     |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Hero image.</li><li>Study description.</li><li>Study teaser.</li><li>Targeting attributes.</li><li>Screener and study question prompts, question settings (unless otherwise noted), and answer choices.</li></ul> | <ul><li>Incentive.</li><li>Recruitment approach.</li><li>Informed consent.</li><li>Device type.</li><li>Recording option.</li></ul> |

## Edit a launched or closed screener

When finding participants for a study, sometimes your recruitment criteria will change. Maybe you need to broaden your search or narrow it down. Regardless, you can edit a launched screener to make the necessary changes. You can also make edits to a closed screener and then relaunch it.

{% hint style="info" %}
Edits made to a screener are only visible to participants who access the screener after the edits are published. Edits are not visible to participants who’ve already applied or who are in-progress. To pause recruitment, close your screener, make your edits, then relaunch.
{% endhint %}

{% stepper %}
{% step %}
Open your screener in Dscout.
{% endstep %}

{% step %}
Click **Edit** in the top-right corner. A modal appears displaying a few reminders.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5Idm0fNo5R1Vtqrtd4jO/47543330922644)
{% endstep %}

{% step %}
Click **Edit screener** in the modal. This enables Editing mode for your screener, as indicated in the top-left corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/yDKakbxqfZRFS9Lb04s0/47543330924436)
{% endstep %}

{% step %}
Edit your screener as needed. You can make edits on the **Overview** and **Screener** tabs.
{% endstep %}

{% step %}
Click **Launch** in the top-right corner. Or click **Publish** if you’re editing an open screener. A confirmation modal will appear.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/kqBAmZ4UpaNQTDPjSecM/47543330925460)
{% endstep %}

{% step %}
Click **Publish** in the modal to verify.
{% endstep %}
{% endstepper %}

Now, your edits are live and will apply to new applicants who begin your screener from this point forward. If you wish to discard edits at any time instead of publishing, click **Exit** or **X** in the top-right corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/urTJ93ppzW0N9ypxN2an/47543315819284)

If you want to collaborate on edits with others in your organization, you can leave the screener in editing mode. Simply navigate away from the screener without publishing or discarding your edits. Others will see the screener is in **Editing mode** from the **Projects** page. Once all edits have been made, follow the steps above to publish them to your participants.

{% hint style="info" %}
If a screener reaches its participant limit while in editing mode, you’ll need to relaunch it and invite more participants for them to see any changes you make.
{% endhint %}

## Edit a launched study

Whether you’re running a usability test, media survey, or intercept study, you can make edits after it’s launched. You can also make edits to a closed study and then relaunch it.

{% hint style="info" %}
Edits made to a study are only visible to participants who access the study after the edits are published. Edits are not visible to participants who’ve already completed the study or who are in-progress. To pause recruitment, close your study, make your edits, then relaunch.
{% endhint %}

{% stepper %}
{% step %}
Open your study in Dscout.
{% endstep %}

{% step %}
Click **Edit** in the top-right corner. A modal appears displaying a few reminders.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/qIgvUsV1rNJQVhcV0UWw/47543330931604)
{% endstep %}

{% step %}
Click **Edit study** in the modal. This enables Editing mode for your study, as indicated in the top-left corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/HoPtOLh0jDI7EXuIFHUg/47543315823124)
{% endstep %}

{% step %}
Edit your study as needed. You can make edits on the **Overview**, **Screener/Intercept**, and **Media survey/Usability test/Study** tabs.
{% endstep %}

{% step %}
Click **Publish** in the top-right corner. Or click **Launch** if you’re editing a closed study. A confirmation modal will appear.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cD02Rt3qE0KHU3YHOOWK/47543330936596)
{% endstep %}

{% step %}
Click **Publish** in the modal to verify.
{% endstep %}
{% endstepper %}

Now, your edits are live and will apply to new participants who begin your study from this point forward. If you wish to discard edits at any time instead of publishing, click **Exit** in the top-right corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Ra3nk0ZZ6nBPP6gK31p6/47543315828244)

If you want to collaborate on edits with others in your organization, you can leave the study in editing mode. Simply navigate away from the study without publishing or discarding your edits. Others will see the study is in **Editing mode** from the **Projects** page. Once all edits have been made, follow the steps above to publish them to your participants.

{% hint style="info" %}
If a study reaches its participant limit while in editing mode, you’ll need to relaunch it and invite more participants for them to see any changes you make.
{% endhint %}

## Analyze an edited screener or study

Editing a screener or study after it’s launched affects how you’ll analyze data and responses. You won’t lose any data by editing your study after launch, but how that data is displayed in Dscout will change.

### Questions view

From the **Questions** view, you’ll see the most recent version of your study by default. This version reflects the most recent edits you’ve made to your screener or study as well as the responses received after those edits were published.

To view responses to previous versions of your data, use the **See version** drop-down at the top of the page.

{% hint style="info" %}
Version selections do not persist across views. Make sure to select the version you want to see when working between the **Questions** view and the **Participants** view.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/VxAvBIQhw9lptJir9idd/47543330945172)

### Participants view

From the **Participants** view, you’ll see all participants listed by default, regardless of which version of the study they saw. And opening an individual participant’s responses displays the questions exactly as that participant saw them.

However, you can filter this list of participants by version using the **See version** drop-down at the top of the page. Selecting a version here will display only the participants who saw that version of your study.

{% hint style="info" %}
Version selections do not persist across views. Make sure to select the version you want to see when working between the **Questions** view and the **Participants** view.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/HvugumphDzx00fDJ5lfL/47543330946196)

You can also view all responses by exporting your screener or study data. Then, you can combine responses from all versions of a single question to aid in analysis. For more information, see [How can I export my data?](/study-basics/analyze-studies/how-can-i-export-my-data)


# Move a screener or study

Projects help you keep your research organized, and sometimes you might need to move a screener or study to a project other than the one where you created it. Maybe you used a screener to find participants for a study that lives in another project—you can move either the screener or the study to the other project so you don't have to rebuild anything.

{% hint style="info" %}
**Note:** Any role except `Viewer` can move screeners and studies, however you can only move screeners and studies between projects you have access to.
{% endhint %}

**To move a screener or study to another project:**

{% stepper %}
{% step %}
Open the project that contains the screener or study you want to move.
{% endstep %}

{% step %}
On the screener or study card, click the **three-dot (options)** icon. Then, click **Move**. A modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FGA0sbLTUcymHKGwoUYjy%2FMove_studies%20(1).jpg?alt=media&amp;token=3fcf9122-1362-4e41-94c9-02912415bedf" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select a destination project from the drop-down. Then, click **Move study/screener**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FRXljUyOVIXw8S5N5ng2u%2FMove_studies.jpg?alt=media&amp;token=5a4b2e7d-0340-49b6-b4f0-cc7e4544afc0" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** Only projects you have access to are displayed. You cannot move a screener or study to a project you're not a part of.
{% endhint %}
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Tip:** You can also move a screener or study from inside the builder. Open the **More actions** (**...**) menu in the header, then select **Move**.
{% endhint %}

### Frequently asked questions (FAQ)

<details>

<summary>Can I move a screener or study regardless of launch state?</summary>

Yes, you can move screeners or studies in `Draft`, `Launched`, or `Closed` states. However, you cannot move screeners or studies out of projects that have been marked `Completed`.

</details>

<details>

<summary>Can I move a screener or study out of a Completed project?</summary>

No, you cannot move screeners or studies out of archived projects or projects marked as `Completed`. You should ensure you've moved anything you need out of a project prior to marking it complete.

</details>


# Close a study

Congrats on completing your study! Closing your study brings you one step closer to deep-diving into your data.

{% hint style="warning" %}
Closing a study is permanent and cannot be undone.
{% endhint %}

## Closing a diary or live interview study

{% stepper %}
{% step %}
Navigate to any page within your study.
{% endstep %}

{% step %}
Click **Close study** in the green bar which appears at the top of your study. A confirmation modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/HW2awQTg7rqBbsnkuDUJ/32118441751828)
{% endstep %}

{% step %}
Click **Close study** to confirm.

{% hint style="warning" %}
**Reminder that studies cannot be re-opened after you've closed them.**
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QKjHgGaCRjRcyYqrtvRp/29192587441812)
{% endstep %}
{% endstepper %}

Once your study is closed, the green bar at the top of your study will turn purple, signifying that your study is currently closed. Additionally, all participants in the Manage page will have a purple “Closed” box next to their name.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Thvc5YMGX6NisO4USlM8/32118480751636)

When you close a study, participants can no longer be invited or submit entries. From the participant's point-of-view, the study will move from being prominently displayed in their “In Progress” tab to their “Closed Studies” page. Don’t worry—you can still message your participants when you close your study.

{% hint style="warning" %}
If you accidentally close your study, please reach out to your Research Advisor or Dscout Support via the support widget (tap the "?" in the top right corner of your study) as soon as possible.
{% endhint %}

## Closing other study types

For information on closign other study types, see the following articles:

* [Close a usability test](/usability-tests/manage-a-usability-test/close-a-usability-test).
* [Close a media survey](/media-surveys/manage-a-media-survey/close-a-media-survey).
* [Close an intercept study](/intercept-studies/manage-an-intercept-study/close-an-intercept-study).

{% hint style="warning" %}
These study types cannot be reopened after they have been closed, and Dscout Staff cannot reopen a closed study for you. If you have accidentally closed your study, you will need to duplicate and relaunch the study.
{% endhint %}


# Relaunch a closed screener or study

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr></tbody></table>

When your participant limit has been reached, your screener, usability test, or media survey will automatically close. It’s also possible to close your screener or study manually. For example, maybe you noticed an error or simply weren’t getting responses you found helpful and decided to hold off on recruiting more participants. Whatever the case, you can relaunch your closed screener or study to reopen it to participants.

{% hint style="info" %}
**Note:** Screeners and studies can only be relaunched within two weeks of being closed. If a screener or study has been closed longer than two weeks, create a duplicate instead.
{% endhint %}

You might relaunch a screener or study if:

* You want to increase your participant limit (n-size).
* You want to increase any quotas you have applied to individual questions.
* You’ve made other edits to your screener or study and want to resume recruitment.

{% hint style="success" %}
**Tip:** Relaunching a screener or study requires you to first enter Editing mode. While in Editing mode, you can make changes to your questions and more. For more information, see Edit a launched screener or study.
{% endhint %}

{% stepper %}
{% step %}
Navigate to the screener or study you want to relaunch.
{% endstep %}

{% step %}
Click **Edit** in the top-right corner. A modal appears displaying a few reminders.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dXZ7q5llUEfP70R9M16N/36685946941204)
{% endstep %}

{% step %}
Click **Edit screener/study** in the modal. This enables Editing mode.
{% endstep %}

{% step %}
(Optional) Make any necessary edits. If your participant limit has been reached, you’ll at least need to increase this value before you can relaunch.
{% endstep %}

{% step %}
Click **Launch** in the top-right corner. A confirmation modal appears.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/bs1uNW8mWGI3C8FWHWX9/36685946942100)

Click **Launch** in the modal to verify.
{% endstep %}
{% endstepper %}

Now, your screener or study will once again be available to participants. New responses will appear alongside any you’ve already collected on the **Responses** tab. You can close your screener or study again at any time by clicking **Close** in the top-right corner.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/z7BlGdAHOFPzo5O4JdgQ/36685946942996)


# Analyze studies

Analyze responses, organize findings, and export your study data.

Use the links below to go deeper on each topic.

* [Reporting excluding and re including data](/study-basics/analyze-studies/reporting-excluding-and-re-including-data)
* [Analyzing data the Dscout way](/study-basics/analyze-studies/analyzing-data-the-dscout-way)
* [Create and manage tags](/study-basics/analyze-studies/create-and-manage-tags)
* [How can I export my data](/study-basics/analyze-studies/how-can-i-export-my-data)


# Reporting, excluding, and re-including data

Dscout supports two features that allow users to clean their data by reporting an issue and excluding submissions from their final analysis dataset in screeners, usability tests, media surveys, diary studies, and interview studies.

## Overview

Researchers can flag and/or exclude submissions and entries that fall into these categories:

* Dishonest content
* Inappropriate content
* Low effort
* Instructions not followed
* Suspected gen AI use
* Duplicate account
* Duplicate entries
* Technical errors
* Off-topic entries

Below we've included some examples for each of the flag types:

* Dishonest content: inconsistent answers within a submission, inability to provide proof of ownership for studies about specific products or items.
* Inappropriate content: rude or disrespectful language + media.
* Low effort: nonsensical answers or responses that suggest minimal to no effort was given.
* Suspected gen AI use: media that contains suspected (or obvious) AI-generated content, written responses that you suspect may have been generated using AI.
* Duplicate account: finding two instances of the same person in your study.

## Reporting an issue

When reviewing submissions and interviews, you can report quality concerns regarding the data received.

* To report an issue in **diary studies** and **interview studies**: select an individual entry or interview > click on the flag icon in the upper right hand corner.
* To report an issue in **screeners**, **usability tests**, **media surveys**, and **intercept studies**: select an individual application or submission from the **Participants** view of the **Responses** tab > tap the three dots in the top right corner next to the participant’s name > select **Report an issue**.

After tapping to report an issue, you will be prompted to select the main reason for reporting the issue:

* Select **Participant** for end-user quality concerns (inappropriate, dishonest, low effort, etc.)
* Select **Technical** when you suspect or observed a technical issue which resulted in issues with the final submission or interview

After selecting the main reason, you’ll be required to select a reason and provide comments regarding the issue observed.

{% hint style="info" %}
When flagging an interview session, please provide any specifics you’re able to regarding the time in the session the problem occurred. This ensures our Support team is able to efficiently identify the issue reported.
{% endhint %}

Our Support team reviews all flags and takes action as needed; any context you can provide about your flag in the comment field helps ensure our team takes the appropriate action. This may include following up with the participant to share feedback or communication regarding corrective actions; feel free to reach out to our Support team (<support@dscout.com>) if you ever have any questions or concerns!

### Report an issue: Screeners

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5uJdQjzZgpVtLwJaONlz/47543295928980)

### Report an issue: Diary studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/eJed6kttGUuJf9N6a7o6/33923658207636)

### Report an issue: Interview studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Udrc3ukVDY6mHlOpls6c/33923642548884)

### Report an issue: Usability tests, media surveys, intercept studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/tHRZ3eZ2uQKIEUmjwxmB/47543295936276)

### Requesting refunds and backfilling data

When reporting an issue in usability tests and media surveys, you’ll see a few resolution options available to you for data cleaning, refund, and backfilling purposes. See screenshot and additional guidance below:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/SoGnvvjqIqUyQkBW95kl/33923658226580)

**Exclude from my dataset**

The entry will be excluded from your dataset, but will not be refunded or backfilled. You may reinclude data as needed when you select this option.

**Request refund**

Within 7 days of an entry’s submission date, you can optionally choose to request a refund for the participant’s incentive when reporting an issue to Dscout. When you select this option, the entry will be excluded from your dataset; please note that this cannot be undone, and will withhold the study incentive from the participant. This is available only within 7 days of the participant submitting their entry to the study, as incentives are automatically processed within 8 days of the submission date. At the top of the reporting menu, you will see the status of the participant’s payment alongside their payout date.

**Request refund and recruit additional participant**

Within 7 days of entry’s submission date, you may also choose to backfill the participant’s data as well as requesting a refund by selecting this option to maintain your original submission goal. If your study is still launched, your study openings will automatically increase by one; if your study is closed, the system will automatically reopen, increase your openings by one, and automatically close after the new submission is received.

{% hint style="info" %}
This option is only available for “Auto-recruit from the Dscout panel” usability tests and media surveys.
{% endhint %}

## Excluding data

If you want to hide entries or submissions from your data set for analysis or data cleaning purposes, you can do so by using the exclude data feature. You may choose to use this feature in conjunction with the “report an issue” feature or on its own, depending on your reason for excluding the data. Excluded data will not appear in any of the Entry views (such as the Entries grid, Closed-ended Responses page, or Open-ended responses page) and will not appear in any exports from the study.

{% hint style="info" %}
It is not currently possible to exclude data in screeners. We recommend using the “assign fit” feature to categorize the application into the Low Quality or Bad Fit categories. You'll still have access to these applications if needed, and will have the option to reassign a Bad Fit back to Good Fit, Possible Fit, or Eligible.
{% endhint %}

* To exclude data in **diary studies** and **interview studies**: select an entry or interview > click on the exclude data icon in the upper right hand corner (next to the flag icon) > confirm that the entry should be excluded.
* To exclude data in **usability tests**, **media surveys**, and **intercept studies**: select an individual submission (**Responses** tab) > tap the three dots in the top right corner next to the participant’s name > select **Exclude entry from data set**.

### Excluding data: Diary studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/XF6PtSwFyB8f0iEHEdeB/33923642563860)

### Excluding data: Interview studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/YYLU0Q45WJ6X7ecZOt2I/33923642566420)

### Excluding data: Usability tests, media surveys, intercept studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5LmSwkDEKZO14AHgzSgb/47543295937940)

## Re-including data

Excluded data will not be deleted from the platform and researchers will be able to re-include any entries or interviews that may have been excluded accidentally.

{% hint style="info" %}
(Note: If you have requested a refund for a submission in a usability test or media survey, you will not be able to access the data or re-include it in your data set.)
{% endhint %}

* To re-include a **diary** entry: click the “Excluded entries” icon in the top right corner of the Entries view > select the entry in question > tap the “re-include” button in the top right corner
* To re-include an **interview** session: click the “Excluded sessions” icon in the top right corner of the Sessions view > select the interview in question > tap the “re-include” button in the top right corner
* To re-include non-refunded **usability test**, **media survey**, or **intercept study** entries: click the “View hidden entries” icon from the **Participants** view of your responses

Re-including data will add it back to your main dataset, meaning the entry or interview will be included in counts, exports, and summary charts.

### Re-including data: Diary studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dz0eZtvF7HxgDZrg4gFA/33923642573076)

### Re-including data: Interview studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QZxW0fIzR4EaA3SPwfae/33923658251028)

### Re-including data: Usability tests, media surveys, intercept studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/XAiFx2axFcN9Tmd1KXSX/47543306056596)


# Analyzing data the Dscout way

<p align="center"><img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5xxYDzSwD6ZxyRgYNog0/360045029712" alt="analyzing_data_1.png">​</p>

Once you've [closed all your studies](/study-basics/edit-close-or-relaunch-studies/close-a-study), it's time to start your analysis. Follow these best practices to ensure you capture as many insights from your data as possible. No matter what kind of project you're running on Dscout, you'll want to follow step 1 below. And if you're considering building a large tag list, reading steps 2-5 will make your life much easier when drawing conclusions.

{% stepper %}
{% step %}

#### **Immerse yourself in individual entries and high level patterns**

Before you start organizing, immerse yourself in the data to get familiar with the stories you’ve collected and discuss what you find with colleagues. What's interesting or surprising about what scouts are showing and telling you? First review some entries individually, then absorb some of your data in aggregate to help surface initial findings and inform a more strategic approach when you go a step deeper with your analysis.

​​![A2.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/kSabaIg6V5AnRJay7zJa/360049389772)

**View individual entries**

Click on an entry to bring up an expanded view. Here you can read responses, view media and see scout information. Click and drag across open-ended answers or video transcriptions to highlight text or to copy it as a quote, pre-formatted, to paste elsewhere. You can also add a bookmark to flag an individual entry with a single click, or write a note to share your opinion about a particular scout's entry with your colleagues.

​​![A3.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/0jl30lKt0aRqaAWeZDvY/360049518731)

**View entry data in aggregate**

The “Entries” dashboard automatically aggregates and organizes all of your data as it is submitted. Just click into the activity name or other headings in the left sidebar to filter by closed-ended question responses, demographics, scout groups & rankings, tags, or bookmarks. You can then investigate the entries that meet your filter parameters.

​![A4.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/lZbgYcMghmO89KjeBDTS/360049389792)​

You can also click into the closed-ended view (by either clicking the Entries dropdown in the top utility bar, or the bar chart icon in the left sidebar) to see how your selected segment's responses compare to all your participants' responses.

{% hint style="success" %}
**Tip:** You can apply multiple filters at once to isolate activities of your data and see only a specific subset of entries. And if you want only export a particular subset of data, just select those entries using filters before exporting.
{% endhint %}

**Discuss and sort key stories**

Sharing your initial impressions with colleagues at this early stage will help you identify and craft the story your data is telling you. Try printing out entries from your favorite scouts and sorting them into categories. Or ask each person on your team to read entries from 4-5 scouts and report back any interesting findings. Activities like this will help you gain a robust understanding of your entry data and make you aware of individual examples that complement your quantitative findings. Just click the arrow icon in the bottom right corner to open your export options.

​![A5.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/t6q6v1u63iPf8zPMM3Jn/360049518751)​
{% endstep %}

{% step %}

#### **Developing descriptive and thematic tag lists**

Tags are short, descriptive labels that can be attached to segments of open-ended data. If your data is highly qualitative, it may not be necessary to quantify your data using tags. On the other hand, if you've packed your entry script with closed-ended questions, you might be able to filter and drill down into your data without needing to use tags. But if your research project is complex, tags can be an essential tool for categorizing, quantifying and sorting entries with attributes you've defined.

{% hint style="success" %}
**Tip:** If you decide to use tags, it's helpful to create a comprehensive tag list *before* you begin tagging by identifying variables that will be interesting for segmenting your data. As much as possible, you want to avoid creating new tags as you go, which will leave you with a hot mess of inconsistent tags. Keep adjusting and augmenting your tag list while you're building it, and make sure everyone on your team understands each tag's definition.
{% endhint %}

*The following example is taken from a Dscout study called "Saving Moments," which asked scouts to record instances where they felt like they were saving money. Scouts captured a huge variety of moments, from using 2 for 1 coupons, to avoiding impulse purchases, to using a mobile app to track their spending. Here's how we started making sense of all that data:*

**Descriptive tags**

First we came up with some ***descriptive*** tags to mark objective, relevant things that we could observe in the entries. Descriptive tags are often situational (locations, actions, triggers) and can be grouped according to category. Keep in mind, there will be tons of things you can tag descriptively, so be sure to focus on areas that are likely to be relevant to your research question. For example, for the "Saving Moments" study, we created just two kinds of descriptive tags: the ***tool*** scouts used to save money (like an app or website), and an ***action*** that described what that tool helped do (like avoid spending or investing).

**Thematic tags**

Next, we came up with some ***thematic*** tags to quantify deeper themes that started bubbling up after immersing ourselves in the data. And after identifying the ***actions*** taken and the ***tools*** used to save money, it made sense to start tagging implied reasons for ***why*** scouts engaged in that behavior (like the desire to grow wealth or reduce the cost of essential purchases).

That effort, in turn, highlighted the fact that scouts were sharing saving moments that could be grouped into three main categories–moments where they lost money, moments where they gained money, and moments where no money actually exchanged hands. This led us to modify our thematic tag list and group them into the ***goal*** and ***cash flow*** tag groups below.

​![A6.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/k2Jo7NH8EL7SAUvdsUKM/360049389812)​

Developing a smart thematic tag list takes time, so don't be discouraged if you don't see a whole bunch of connections right away. The longer you sit with your data, the easier it will be to use thematic tags to quantify things like pain points, stages of a journey, different modes of behavior, or competing strategies.
{% endstep %}

{% step %}

#### **Build and review your tag list in Dscout**

Once you've built your tag list using a chart like the one above (or sticky notes!) it's time to build your tag list inside Dscout. Just make sure your tag list is fully mapped out first.

For more information, see [Create and manage tags](/study-basics/analyze-studies/create-and-manage-tags).​
{% endstep %}

{% step %}

#### **Evaluate your tag list, then tag every entry**

After you've applied your tags to 10-20% of entries, pause to evaluate how your tag list is working for you. The goal is to revisit your themes, condense in some places, expand in other places, and rename as needed to perfect your tag list before you've invested time tagging your entire data set. To do so, ask yourself these questions:

1. Does it feel difficult to apply your tags? A good tag list should feel easy to apply and maintain. If lots of tags seem like they could go either way with an entry, or if too many entries seem like they could fit into any tag, it's time to review your tags and your approach.
2. Cut your thematic tags by your descriptive tags and other demographic attributes to see if you find distinctions. If there are no noticeable differences between the themes, they may not be meaningful themes to focus your analysis on.
3. Is your tag list mutually exclusive and comprehensively exhaustive (MECE)? This is ideal, but not always possible. Strong knowledge of your data will help you know when to strive for MECE tags and when it would complicate your analysis.
4. Are there any tags that overwhelm the rest of a data, such as a tag that could be applied to 40% of your entries? If there are, try to break that tag down into smaller parts.
5. Are there a bunch of entries tagged "other"? If so, revisit your "other" entries and look for commonalities. Can you create a new tag for some of these entries to call home?

When you're confident that your tag list is right for your data set, dive back in and apply tags to every entry.
{% endstep %}

{% step %}

#### **Examine relationships and quantify themes**

When all your entries are tagged, you can turn to Dscout's sorting, filtering and export features to make sense of the data. Up to this point, you've spent your time identifying interesting themes and categorizing your data points with attributes that inform these themes. Now's the time to quantify how often these attributes occur and examine relationships between them.

**Start by examining the frequency of an attribute within the entire data set.**

* Out of all the saving moments, how often were scouts utilizing an app? (tag = tool: app)
* Out of all the saving moments, how often were scouts working to prevent purchase? (tag = goal: prevent purchase)
* Out of all the saving moments, how often is the scout actually spending more money than they're saving? (tag = cashflow: negative)

**Then examine the intersections between attributes (the frequency with which combinations occur).**

* When the goal is to prevent a purchase, which saving tool is most frequently mentioned?
* When the saving tool is an app, what goal is most frequently mentioned?
* With people 18-34, which saving tool is most frequently mentioned?
* Do men or women more frequently use coupons to save money?

To answer these questions, we'll segment the data by thematic tags, descriptive tags, demographics and responses to questions. You can apply multiple filters to see the frequencies of a specific subset of entries. In the example below, you can click the tag "tablet" to only display the entries where a coupon was used. Then, using the demographics tab, you can view only entries wherein a woman used her tablet to view media.

​![A9.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/XHxwJBklpidvL5GmrUlg/360049518791)​

If you're looking for more rigorous quantitative analysis, you'll likely want to use crosstabs in addition to filters. A crosstab (short for cross-tabulation), is a table that displays frequency counts for your data set. Crosstabs allow you to evaluate the intersections of certain attributes, by displaying the frequency with which combinations occur. Click the export icon to create a crosstab in .csv, with the options to include tags, questions, scout groups, age, gender and more.

Once you've wrapped up analysis, it's time to tell a story. At Dscout, we generally deliver our insights in a framework. Your insights are the things you learn, your framework is the way you relate those things together, and the story is the way you communicate the relationship between the two.
{% endstep %}
{% endstepper %}


# Create and manage tags

When analyzing your studies, you may choose to tag your entries. Tags are labels for identifying themes and/or keywords that are relevant to your project. These tags are shared across your team but are not viewable by participants. Tags can be created and managed in both a launched and closed study.

### Creating and editing tags in the tag management page

In screeners, usability tests, media surveys, and diary studies, you can navigate to the tag management page by hitting on “Entries” in the study header and selecting the “Tags” option. In interview studies, head to the sessions tab and click “TAGS.”

For all Dscout products, you can jump right in and create a tag in the existing “Ungrouped” tag group by hitting “+ New Tag.” As you create new tags, they will appear in its group chart with a “0” count, which indicates that the tag has not been applied to any response content yet.

To edit or move a tag, hover over the tag you want to adjust and click the pencil icon that appears. From there, you can change the tag’s title, move it to another tag group, or delete the tag altogether.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/12T3w5TVgNaSILiSfsfE/360089488772)

If you already have a sense for the tag groups you want to make, that works great too. You can click the “+ New Tag Group” button at the top of the page, just above the ungrouped tags. Once you have clicked this button, your “Untitled Group” will appear. Click on the more details icon on the right side and you'll be able to edit the name and tag group color, as well as provide an optional description of the group.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/XTVungPuiZSNJcrWMfod/360089491111)

{% hint style="info" %}
There is a limit of 1000 tags per study, and 100 tags per tag group.
{% endhint %}

### Applying a tag outside of the tag management page

You can apply tags directly in a participant's entry, via the open ended responses tab, or in the transcript of a session if you are using interview studies.

To apply a tag to an open ended or video response in an entry, you can either hit “Tag Response” below the question you want to tag, or you can highlight a section of the response and click “Apply Tags (#).” Either of these actions will cause a pop-up with a list of your existing tags to appear. If you have already created the tag that you want to use for this question, simply find your desired tag and click on it. If this is a new tag, type in its title and hit enter, which will allow you to indicate which group the tag belongs to.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/TIF7MKE1qLKhzfFQgJbs/4407695837204)

The [open ended response tab](/diary-studies/analyzing-your-diary-study/open-ended-responses-view) is a great way to hone in on one question and apply tags across a number of participants. In the tab, you can choose the question you want to analyze and see all the responses to it below. To apply a tag, follow the same instructions described above.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4Lmjn75ZdHGJ7SfQJA22/360089491131)

To apply a tag in interview studies, navigate to a participant's session, and then highlight the portion of the transcript you wish to tag, and follow the same steps described above for diary studies, usability tests, media surveys, and screeners.

### Using filters on tag management charts

Once you have started tagging responses, you’ll be able to see a chart that displays the total number of responses by tag within each group. If you would prefer to see counts for the number of entries or participants represented, you can use the options to the right of the “Show Count By” header at the top of the page.

In diary studies, usability tests, media surveys, and screeners, you are also able to apply filters when looking at the tag management charts to focus on certain groupings of participants. You are able to filter on a number of different factors, including demographics, participant groups, responses to closed ended questions, and even other tags.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/FpYvJxZmPWDCTHYySXro/360089491151)

### Reviewing responses and using filters on tagged response details page

When looking at the tag management charts, you’ll notice that hovering over a tag with a count greater than 0 will show a tooltip that says “View Responses”. Click on the row of the tag to view all of the responses with that specific tag. In diary studies and Recruit screeners, the grouping of responses will depend on which “Show Counts By” setting (response, entry, or participant) you are currently on. In interview studies, you will see the highlighted part of the transcript that you tagged.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/G03ofHTBTwXsbjtc5GRE/360089491171)

In diary studies and Recruit screeners, you are also able to apply filters based on attributes, such as participant group, demographic information, answers to closed ended questions, or other tags to hone in on the specific participants whose entries include your chosen tag.

### Exporting tag data

To export tagging data in diary studies, usability tests, media surveys, and screeners, click the export button (square with an arrow pointing into it) in the top right corner of the [Applications view](/recruit-participants/what-are-dscout-screeners/review-screener-responses). Click on “Tags” to view the export options. You can choose to export tag counts, the tagged responses, or a list of your tag groups and tags, all of which download as a csv. As with all [exports](/study-basics/analyze-studies/how-can-i-export-my-data) on Dscout, any filters that you have applied will affect what is downloaded in your export. In interview studies, you can find these options by hitting “Export Tags” above the tag groups.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/oFWcJSB3QjW3flyFRkaj/360089491191)

### Importing tags and tag groups

To import your tag list, navigate to the tag management page and click on “Import Tags” in the top right corner of the screen. From there, you can either import tags from another study/screener in the project, or you can import from a CSV file. This CSV file should have two columns, one titled “Tag Name” with a list of tags in each row below, and the other titled “Tag Group” with the corresponding tag group for each tag. Please see below for what this CSV file should look like.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/PRzYJ0T8WindLroERC6W/360094312371)

If you want to import tags from another study in a different Dscout project, you can easily do so by exporting the “Tag Groups and Tags” from the other study. This export will be in the correct CSV format to upload into your new study.

If you click on our example template and it downloads in Numbers, you will want to import the file into Google Sheets or Excel. In Google Sheets, you can click “file,” then “import,” attach the CSV file, hit “import data” and then click on “open now” to see the correctly formatted sheet. In Excel, you can navigate to the Data tab, click on “Get External Data” in the top left corner, and select “From Text.” From there, select the our example template CSV file, hit “Get Data,” and make sure to set “comma” as the delimiter. As long as your file follows the same format as the image included above, you should be all set to import your tag list!

### Further information

Now that you know the ins and outs of creating tags, managing tags, and the tag management tab, you may be wondering how to best utilize these features. To learn more about how we code and tag qualitative responses to gain a greater understanding of our data, check out [this article](https://dscout.com/people-nerds/how-to-code-and-tag-qualitative-data-for-research-insights) from our very own People Nerds blog post.

If you have further questions about tagging feel free to reach out to someone from the Dscout team.


# How can I export my data?

Download your study and screener data to manipulate it in other programs and share it out with stakeholders.

Just want to share a video or picture (or two)? Use [public share links](/study-basics/playlist-editor/public-share-links).

Please note that:

* Even if screeners and studies are located within the same project, data from each must be exported separately from the platform.
* Researchers may export data from the platform. If you need access to this feature, contact your Account Owner.

## Exporting data from a screener

To export data from your screener, click the export button (square with an arrow pointing into it) in the top right corner. The dialogue box that pops up has a myriad of data export options.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/k2zwTEvQvZhrM1c2f4tW/30871846609044)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7pfnOLw3yb4nBtm1QjJa/30871846610964)

In the **Basic** tab, you can download a zipped folder of all photos and videos, a .csv file of all responses to questions (including transcripts of videos), and a .csv file of all notes your team members have made on any applications.

In the **Print / PDF** tab, you can export or print a PDF of all applications.

In the **Crosstab** tab, you can toggle various row and column combinations for a crosstab to your liking. Column/row options include, but are not limited to, responses, tags, and extended profile data. Try playing around with the infinite combinations!

## Exporting data from a usability test or media survey

For information on exporting data from a usability test or media survey, see the following resources:

* [Export usability test data](/usability-tests/analyze-a-usability-test/export-usability-test-data).
* [Export media survey data](/media-surveys/analyze-a-media-survey/export-media-survey-data).

## Exporting data from a diary study

There are two kinds of diary study exports: study data and participant data.

**Study data export**

To export study data from a diary study, click the export button (the box with the arrow pointing out of it) in the top-right corner of your study’s entries page. The box that pops up also has a myriad of data export options.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/LJ5atEWGIxNteogqYnwV/360049400452)

In the **Basic** tab, you can still download a zipped folder of all photos and videos, a .csv file of all responses to questions (including transcripts of videos), and a .csv file of all notes your team members have made on any entries. Unique to diary exports, you can export any comments left on entries into a .csv file as well.

In the **Print / PDF** tab, similar to screener exports, you can export or print a PDF of all entries sorted either alphabetically, oldest to newest, or newest to oldest. You can also toggle layout and included data, including entry responses, researcher notes and highlights, and extended participant demographics.

In the **Crosstab** tab, you have the same capability to toggle row and column combinations for crosstabs. Check out all the combinations you can have in the platform!

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/pEzw8tsOhhouWsT7DcBO/360049530831)

**Participant data export**

To export participant data, select the participants in whom you are interested on the Manage page, and select "Export Data." You'll have options to:

* Export basic participant demographic data
* Export participant profile pictures
* Export your message history with participants

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/g1uFPDX1bfgWF5nGkQDz/360049530851)

## Exporting interview study data

To export data from a live interview study, see [Export interview study data](/interview-studies/view-interview-session-recordings/export-data-from-an-interview-study).


# Playlist editor

With the playlist editor built directly into the Dscout platform, you can compile and edit your videos and clips into a cohesive playlist and share them directly with your stakeholders and collaborators — without ever leaving Dscout.

## Editing a playlist

Once you've selected your clips, you'll refine your playlist in the playlist editor. Read on to learn more about all of the features you’ll find in our playlist editor:

#### **Navigating the Editor**

* On the left side of the screen, you’ll see the media queue of all videos or clips you selected. Drag and drop individual recordings in the queue to re-order. You can also duplicate, download, and remove individual recordings from the media queue; removing a recording from the media queue will remove it from your playlist.
* To trim an individual recording:
  * **Option 1:** Select that recording in the media queue on the left or in the timeline editor at the bottom of the screen. Use your cursor to click and drag from either the beginning, or the end of the recording to set the in point (where the recording starts), or out point (where the recording ends) for your edit.
  * **Option 2:** You can also trim a recording via transcript. Click and drag from either end of the transcript to highlight the portion of the text you’re interested in, and Dscout will automatically adjust the in point and out point of the recording to match your selection.
* The editing tools visible beneath the video player also function to trim recordings or to allow you to skip around within a recording. Several of these functions have keyboard shortcuts:
  * Nudge playhead back (left arrow)
  * Play (spacebar)
  * In Point (i)
  * Split (s)
  * Out Point (o)
  * Nudge playhead forward (right arrow).
* Use the timeline magnifier in the bottom right corner of the editor to zoom in on the timeline for more precise editing, or to zoom out and see more of your playlist recordings in the timeline.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/cSOYRXdRRNBMXmVvUtHG/4417989591572)

#### **Text slides:**

Text slides can be added before or after any piece of media, customizable with a title and subtitle.

* Adding a text slide
  * Tap the “+” symbol in the bottom in the media editor. You’ll see one of these icons before and after each clip.
* Removing a text slide
  * Tap the “…” in your media queue (lefthand column)
  * Tap the “...” in the bottom of the media editor
* Titles and subtitles
  * Titles and subtitles are optional, and can be up to 40 and 140 characters in length, respectively.
  * **Text style:** use this dropdown menu to change your typeface.
  * **Alignment:** use these options to align your text (left alignment, centered, right alignment).
* Duration
  * Use this to change the duration of your text slide. You can edit duration by dragging your text slide in the bottom of the media editor as well.

#### **Media settings:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/muFm1B4GEVzbOkBrM9Mp/17755150561428)

For any single piece of media, you have the ability to add a scout's first name and last initial as well as flip their media.

{% hint style="info" %}
**Note:** these features will only apply to the clip or video you’re currently editing.
{% endhint %}

* **Add scout name:** tap this toggle to apply the scout’s first name + last initial to their video. This will appear after \~1 second and is displayed for \~5 seconds before. When using this feature, we recommend introducing the scout the first time they appear on screen, then refraining from adding their name to subsequent appearances.
* **Flip media:** use this toggle to flip or “mirror” a clip or video.
* **Custom blur (Select plan only):** tap "Create blur" to add a blurred shape to your video. After tapping "Create blur," you'll be directed to the blur editor, which allows you to choose the shape of your blur (circle or rectangle); use the crosshairs to adjust the size of your blur, and click and hold on the blur to reposition. When you're done, tap "Exit editing" above the video preview to save your blur selections.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7Vthgj2YjJ56FAd34ZAx/17755187370004)

#### **Playlist settings:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/WhI5s3HIxfpUcLutXLES/17755187373460)

These changes affect all media in the playlist including media that gets added after the feature is turned on.

* **Dark theme:** apply this toggle to change the video sideboards, text slides, and fade color between black and white.
* **Level audio:** use this feature to “boost” the volume of quiet clips and lower the volume of louder clips.
* **Fade:** adds a 0.2 second fade to the beginning and end of all text slides and media. Note: this does not fade or impact audio.
* **Aspect ratio:** use this to change the ratio of your playlist. 4:3 is great for mobile videos while 16:9 is ideal for desktop videos.

## Rendering a playlist

When you’re done editing your playlist, click the “Render Playlist” button on the left to create a compiled video for sharing or download.

Depending on the length of your playlist, rendering may take up to a few minutes, during which time you will not be able to edit your playlist. Feel free to leave the playlist page while rendering happens.

{% hint style="info" %}
**Note**: If you edit your playlist after rendering it, you’ll need to re-render the playlist if you want to share or download the latest version. You'll see the "Render playlist" button update to say "Re-render playlist" after making edits.
{% endhint %}

## Sharing your playlist

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/IlDLFbr5vbESsZVx3e97/16466500557716)

You can share your playlist via public share link, or you can download it.

* **Share link:** Once your playlist is rendered, click “Share” to [create a public share link](/study-basics/playlist-editor/public-share-links) for the compiled video.
* **Download:** Once your playlist is rendered, click the “Download” icon to download the compiled video as an MP4 file.

{% hint style="info" %}
**Note**: Re-rendering your playlist will update the video that users of your share link see. That is, if you make any changes to your playlist and re-render it, the video that users see will change as well.
{% endhint %}


# Public share links

Anyone who has the public share link will be able to see the media you’ve shared—no Dscout login required! Our public share links are available for all product areas—tap the links below to learn more about sharing media from your study type:

**Don't see the ability to create public share links?** At this time, share links are only available for subscription accounts. Chat with your Account Manager to learn more!

## Creating a public share link

Users with a Member or Researcher seat and above can create public share links. The public share link icon is found in a few different places depending on your study type; check out the sections to learn more about where the option is found based on your project, then read on to learn about setting up your link once generated.

### Diary studies

![Screenshot 2023-12-10 at 2.06.00 PM.png](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QtNnxCTu19INQwsCD6NK/21741168229780)

{% stepper %}
{% step %}
Click into an individual application or entry.
{% endstep %}

{% step %}
In the top right corner of the media you’d like to share, find the “Share” icon (tray with an arrow pointing up).
{% endstep %}

{% step %}
Click “Generate public share link.”

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/XCaQ8lhDqlX7J9Tl9gbl/21741168240148)
{% endstep %}
{% endstepper %}

### Usability tests

Public share links are available for the [full recorded session view](/usability-tests/analyze-a-usability-test/view-usability-test-session-recordings) in usability tests.

{% stepper %}
{% step %}
Navigate to the full recorded session view (Analyze > Participants > "View full recording" button to the top right of the first prompt)
{% endstep %}

{% step %}
Tap "Share" in the top right corner of the media viewer

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/fFt4EbrN1Eoo1ybbXuvb/47543342803988)
{% endstep %}

{% step %}
Click “Generate public share link”
{% endstep %}
{% endstepper %}

### Interview studies

Public share links are available for [clips](/interview-studies/view-interview-session-recordings/clips-and-playlists-in-interview-studies) you've created from your interview sessions.

{% hint style="info" %}
**Note:** full session public share links are not supported at this time.
{% endhint %}

{% stepper %}
{% step %}
Navigate to the "Sessions" tab of your study.
{% endstep %}

{% step %}
Tap the share icon to the right of any clip (indicated by the purple "paper + scissors" icon).
{% endstep %}

{% step %}
Click "Generate public share link".
{% endstep %}

{% step %}
You can also tap into the session recording you'd like to share clips from, locate the clips section below your session player, then select the "Share" option to the right of your clip.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ArqJwBEYEHDxFRMB6t7h/21741168254228)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/FjTygcOb8lVCbsgLt8Jo/21741168266132)
{% endstep %}
{% endstepper %}

## Configuring your public share link

Once the public share link is generated, you’ll see a few additional options:

* Add a title to your link, to give viewers more context for what they’re seeing
* Require a password to view the link page, for additional security
* Set an expiration date for your link (default expiration is one year)

{% hint style="info" %}
**Note:** if your link expiration date extends beyond your Dscout account access, your public share link(s) will expire on the date of your subscription or trial end date.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/jJvXjz4Jo8eOKvYIaHuL/21741168271764)

Customize your link settings, then click “Save.” The “Share” button for that piece of media will change to “Sharing” to reflect your link's active status.

{% hint style="warning" %}
All that’s left is to send the link—and password, if required—to your desired audience. **Keep in mind: Anyone who has the public share link can view this media and can share the link with others. You are responsible for ensuring you only provide access to authorized individuals.**
{% endhint %}

Here’s an example of what stakeholders will see when they visit your public share link page.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/vmcQ0ToTAhXnkI9QCcxh/21741145081108)

## Editing/deleting a public share link

To edit or delete an existing public share link, click the “Shared” button on the desired media to open the link settings modal.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/kxWAsN9E7c03QPPKZUIc/21741145083156)

You can edit the title, access code requirements, or expiration date for your public share link in the settings modal. Click “Save” to apply any edits. The link URL won’t change, so no need to re-send to viewers—just make sure that you pass along any new/updated access codes.

To delete your public share link, click “Delete public share link," which will immediately delete the link and access to the video via your prior link. Anyone who attempts to visit the deleted link will see a message that the shared content is no longer available.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JcQ3GhEnRBP7trWA5Pny/21741145091476)

## Managing public share links for a project

To help you keep track of all the public share links in your project, we’ve created a link manager at the project level. Researchers can access the link manager by clicking **Manage share links** within a project.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/0QdgN4k5Z60P2Dg341Bt/47543299200276)

The link manager shows the link title, type, number of views, and expiration date for each public share link in your project. Click the “Edit Link” button to edit or delete an individual link.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/NDt3a6Bht8IQHZsY1VBb/21741168309908)

{% hint style="info" %}
**Note:** The project link manager shows up to 120 public share links. If you create more than 120 links in a given project, simply delete any links that are no longer in use to show the most relevant links in the manager.
{% endhint %}

## Sharing media to Slack

Sharing media to Slack requires the Dscout Account Owner, admin, or researcher to authorize a Slack workspace on the “Integrations” tab of the Account Management page. [Learn more](/integrations/dscout-slack-integration) about the Slack integration for Dscout.

If your Dscout account has the Slack integration enabled, you can use public share links to send Dscout media directly to public channels in your Slack workspace.

{% stepper %}
{% step %}
Generate a public share link for the piece of media you want to share
{% endstep %}

{% step %}
Click the “Share it on Slack” option in the link settings modal
{% endstep %}

{% step %}
Select a Slack channel and write an optional note
{% endstep %}

{% step %}
Click “Share to Slack” to post the media (accessed via public share link) to your desired channel

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/KjWRFvITz97n0f6r9IgV/21741168311444)
{% endstep %}
{% endstepper %}


# What are Dscout screeners?

Screeners help you find high-quality participants for your studies. Design and build your screener, review and rate applicants, and add them to your study seamlessly.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/CZGNZBzqEOmqpMl7wXAU/34717694940692)

## Get started with screeners

If you have a Dscout subscription, just log into your account, add a new project, create a screener, and dig in!

If you **don't** already have a subscription and you'd like to recruit participants from the Dscout community to participate in your research project, [get in touch](https://dscout.com/getting-started-project#contact-form) with us.


# Question types in screeners

{% hint style="info" %}
**Note:** This article details information about standalone screeners (used for recruitment only). For information regarding available question types in usability tests and/or media surveys, see [Question types in usability tests](/usability-tests/what-are-usability-tests-in-dscout/question-types-in-usability-tests) and [Question types in media surveys](/media-surveys/what-are-media-surveys-in-dscout/question-types-in-media-surveys).
{% endhint %}

## Overview Tab

From the Overview tab, you can leverage [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes) to reach participants based on demographics and some preferences/behaviors (reducing the overall number of screening questions you'd need to include).

### Targeting Attributes & Primary Attributes

As you look to target your audience, Dscout offers a growing list of [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes) available to you across categories like Device, Shopping, Subscriptions, Work, etc. These Targeting Attributes (often referred to as TA or TAs) are located in the Overview tab.

Primary Attributes are a subset of Targeting Attributes that are required to be answered by all of the participants in our scout pool. These attributes are automatically included as filters in analysis regardless of whether or not you choose to target by them. As you choose which attributes to target by in the Overview tab, you will find Primary attributes are distinguished with a star as shown below (Ethinicity is a Primary Attribute, while Work place is a Targeting Attribute).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ytGu2iwdeyrb8TUia2kd/30858749676308)

By adding an attribute to your screener, you control which answers qualify. In the example below, Homemaker, Retired, Student, and Temporarily Unemployed are the only options selected, so only scouts that chose one of those answers would find the screener. Those who are Employed full-time (30 hours +) or Employed part-time would not find the screener in this example.

Remember, this is fully customizable -- you could choose any combination here!

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/5PuhD5ETue0eiDnkbjs1/30858735546900)

## Screener tab

You’ll find both knockout questions (questions that require termination logic) and standard questions in the **Screener** tab.

We recommend including no more than 20 questions in your screener, one of which can prompt scouts to take a picture, and one of which can ask for a video.

Knockout questions automatically disqualify Scouts based on their answer choice. These applicants will be skipped to the end and will not count against the screener application limit (only qualified applications will count).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/KrdneKYwfQRGiORtUwcS/34716965645972)

In the **Screener** tab you can include:

* [Knockout logic](/recruit-participants/dscout-scout-panel/knockout-questions)
* [Must select logic](/study-basics/design-a-study/must-select-logic)
* [Quotas](/study-basics/question-types/using-question-quotas)
* [Skip logic](/study-basics/design-a-study/skip-logic-in-screeners)
* **Disqualify if all selected:** this is a toggle on multiple choice (multiple select) questions that will flag any scouts that select every option. This is on a per question basis, and shouldn't be enabled if you believe that a scout could truthfully select every option.
  * If a scout selects all choices on a multiple choice question (and this setting is enabled), the scout will be rejected, and their application will not be included in the qualified applications you receive.
  * If “Other” or “None of the Above” is a response choice, a scout will be rejected if they select all of the programmed choices. “Other” and / or “None of the Above” do not need to be selected to disqualify the scout for selecting all responses.

In addition to questions, you can leverage [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes) to reach participants based on demographics and some preferences/behaviors (reducing the overall number of screening questions you'd need to include).

### Multiple choice

* **Single select:** Limit scouts to 1 answer option.
* **Multiple select:** Allow scouts to select multiple answer options. In addition to knockout logic, multiple select questions allow you to include [must-select](/study-basics/design-a-study/must-select-logic) logic. Use this logic to designate response choices that scouts must select to qualify.

**Multiple choice programming options**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/39FOJ8Xi7HUT34E2ZA2s/30858491594004)

* **Randomize choices:** use this to present multiple choice answer options in a random order to scouts.
* **"Other (Tap to Type)":** use this to provide a write-in response option. Note that this option will always be anchored at the bottom of the list even when randomization is used.
* **"None of the Above":** use this to allow scouts to select "None of the Above." It will be excluded from randomization and cannot be chosen in combination with other response options.

{% hint style="success" %}
**Tip:** You can customize the text on "Other" and "None of the Above" choices.
{% endhint %}

### Open-ended

Ask scouts for an open-ended response.

* **140 characters**: Limit scouts to 140 characters for their response.
* **No limit:** Do not apply a character limit to the question response.

### Checkpoint

Introduce a series of questions, give scouts a moment to pause ("You're doing great, more than halfway done!"), or offer additional context without asking a question.

### Scale

Provide scouts with a numerical scale for ratings. Scale questions allow you to specify a scale as large as 0-10 and to define the **Start value** and **End value** labels for your participants. (Suggested character limit for labels of 50-100 characters.)

### Ranking

Ask scouts to rank your answer options *(e.g. rank the following pizza toppings from best (1) to worst (6)).*

* **Rank all**: ask scouts to rank *all* of the answer options listed
* **Custom limit**: ask scouts to rank at least *x* number of answer options, at most *x* number of answer options, or exactly *x* number of answer options listed.

**Randomize rank choices:** use this to present rank choice answer options in a random order to scouts.

**"Other (Tap to Type)":** use this to provide a write-in response option. Note that this option will always be anchored at the bottom of the list even when randomization is used.

**Scouts can mark rank options as N/A:** for "Rank all" ranking questions, use this to allow scouts to mark any rank choices that are not relevant to them as "not applicable." This option is not available for "Custom limit" ranking questions.

You can find a complete rundown of ranking questions and how to analyze the results in [Ranking questions](/study-basics/question-types/ranking-questions).

### Number

Ask scouts to provide a number, up to 9 digits long. (Be sure to specify the unit in your question prompt).

### Media

Ask scouts for up to 1 photo and 1 video in a screener.

* **Photo:** PNG and JPEG files accepted
* **Video:** MP4 and MOV files accepted with a maximum recording length of 1 minute.
* **Screen recording:** Ask scouts to record their phone's screen for up to 2 minutes, or their desktop for up to 2 minutes (with desktop activities). Scouts can choose what they'll show you, or you can enable a Starting URL. For more information, see [Screen recording guide for researchers](/study-basics/question-types/screen-recording-guide-for-researchers).


# Set up a screener

Screeners help you find the most qualified participants to take part in your research study. Whether you need participants for a Diary study or an interview, you’ll start by building a screener. Screeners combine targeting attributes and preliminary questions to determine a participant’s relevance to your research needs.

{% hint style="info" %}
**Note:** If you’re building a usability test or media survey study, the recruitment process is built in. You do not need to build a screener to fill these studies. However, you can add participants from a past screener to a new usability test or media survey. For more information, see [Add participants from a screener to a usability test](/usability-tests/what-are-usability-tests-in-dscout/add-participants-from-a-screener-to-a-usability-test) or [Add participants from a screener to a media survey](/media-surveys/what-are-media-surveys-in-dscout/add-participants-from-a-screener-to-a-media-survey).
{% endhint %}

## Screener types

When building a Dscout screener, you can choose one of the following recruitment methods:

* **Recruit from the Dscout Panel:** Screen and recruit participants from Dscout's existing pool of over 100,000 Scouts. You'll be able to review applications and hand-pick who you want to invite to research studies.
* **Invite your own participants:** Share a link with your own potential participants so you can screen them prior to inviting them to a research study. (These screeners are not available to members of our Dscout Panel or Partner Panels, nor will your participants be added to either panel.)
* **Recruit from Dscout's Partner Panels:** Screen and recruit participants from Dscout's Partner Panels (like Respondent). You'll be able to review applications and hand-pick who you want to invite to research studies.

When selecting a screener type, think about whether you already have a group of people you want to participate in your research study. If you do, inviting your own participants might make the most sense. If you don’t, recruit from one of our available panels.

## Create a new screener

When creating a screener, you’ll start by establishing the basic details like how long the screener will remain open, how many participant openings you have, and more. You’ll also give your screener a title and an image, which are great opportunities to make your screener fun and engaging.

{% hint style="success" %}
**Tip:** Dscout AI can help you draft an entire screener, even if all you have are a few details about your target audience. Go from idea to insights—fast. For more information, see [Draft a study with Dscout AI](/dscout-ai/dscout-ai-studio/draft-a-study-with-dscout-ai).
{% endhint %}

{% stepper %}
{% step %}
Navigate to the project where you want your screener to live.
{% endstep %}

{% step %}
Click the **Screeners** tab at the top of your project.
{% endstep %}

{% step %}
Click the **Create screener** button in the top-right corner of the page.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FR7H7KHGE4G8LdFJWthse%2FUntitled%20-%202026-07-15T121251.249.jpg?alt=media&amp;token=e68f2790-7149-4ae6-993f-f34298fe19d3" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select a **recruiting approach**, depending on who you want to participate. For more information, see [Screener types](#screener-types).

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FFGtZ6etyUKRhPVeAR6rf%2FUntitled%20-%202026-07-15T121331.438.jpg?alt=media&amp;token=63739695-831e-4010-af6a-62358f2741e8" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="success" %}
**Tip:** If you have an existing screener you want to use as a starting point, click **Duplicate an existing screener**. You'll then have a copy of your previous screener you can modify to fit your current needs.
{% endhint %}
{% endstep %}

{% step %}
Click **Continue**.
{% endstep %}

{% step %}
Enter a screener title. This title will be visible to your participants. Or, click **Skip for now**.
{% endstep %}

{% step %}
(Optional) Click **Add an internal screener name**, then enter a name only visible to you and your collaborators.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/L3u1a2wWPsXGadTB7g7U/34716506926740)
{% endstep %}

{% step %}
Click **Create screener**.
{% endstep %}
{% endstepper %}

Next, you’ll land on the **Overview** tab for your screener. Under **Setup** on this tab, you can customize your screener’s appearance, your screener’s details, and the details of the Diary or live interview study they’re applying to participate in.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/DOuZj3l7u5feEB7Aomk0/34716506928276)

### Appearance

Under **Appearance**, you have the chance to customize the look and feel of your screener. Here, you can configure the following settings:

| Setting              | Description                                                                                                                                                                                                                                                                                                                      |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Hero image**       | Upload an image to display on your [screener webpage](/recruit-participants/what-are-dscout-screeners/screener-webpages). You can choose an image provided by Unsplash or upload your own.                                                                                                                                       |
| **Company branding** | Display or hide your company branding on your screener webpage. When toggled On, participants will see your company’s name and logo. When toggled Off, participants will not see your company’s name and logo. For more information, see [Company branding](/account-management/organization-account-settings/company-branding). |

### Screener details

Under **Screener details**, you can customize the logistics of your screener. Here, you can configure the following settings:

| Setting                        | Description                                                                                                                                                                                    |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Teaser description**         | A brief summary of your research to give participants an idea of what they can expect. Be as descriptive as you want, but don’t give too much away to avoid application bias.                  |
| **Openings**                   | The number of candidates you will invite to take part in your research study.                                                                                                                  |
| **Screener application limit** | The total number of applicants allowed to complete your screener. By default, this is set to five times your selected openings.                                                                |
| **Screener open for**          | The number of days your screener will remain open if your application limit is not met. If your application limit is met, your screener will automatically close regardless of this selection. |

### Study details

Under **Study details**, you can tell your research candidates a little more about the study they’re applying to be a part of. Here, you can configure the following settings:

| Setting        | Description                                                                                                                                                                                                                                                                                                                                            |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Start date** | The date your research study will begin.                                                                                                                                                                                                                                                                                                               |
| **Duration**   | The number of days your research study will run. For interviews, we recommend using one day if you only plan to conduct one session per participant.                                                                                                                                                                                                   |
| **Incentive**  | <p>How the candidates selected to participate in your study will be compensated. You can select:</p><ul><li>Monetary. (An additional field will appear for an amount.)</li><li>Non-monetary.</li><li>None.</li></ul><p>Most Dscout projects pay between $20-$200, depending on how much time and effort is required, and how niche the recruit is.</p> |

## Targeting attributes

{% hint style="info" %}
**Note:** Targeting attributes are only available when recruiting from the Dscout Panel or Dscout's Partner Panels. If you’re inviting your own participants, it’s assumed that your participants already meet these requirements.
{% endhint %}

Once you’ve created your screener and configured the basic details, the next step is to define your target audience. You’ll do this using targeting attributes, which let you set identifying characteristics for your ideal participants. For example, you can set an age range your qualifying participants must fall into. Or, you could specify that qualifying participants must have access to a certain streaming account. You can mix and match these attributes however you see fit. Participants who do not meet your specified targeting attributes will be automatically disqualified and will not be able to participate in your study.

{% stepper %}
{% step %}
On the **Overview** tab of your screener, click **Targeting attributes** in the left sidebar.
{% endstep %}

{% step %}
Select from the list of **Categories**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/vr2p8ERzIlNSB4LaPuKi/34716502945172)
{% endstep %}

{% step %}
Click an attribute to add it to your screener. The attribute and its associated options will be added to the center panel of the builder.
{% endstep %}

{% step %}
Select your desired value(s).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/fFZCOxN1MSIBNUlIcG6v/34716506930196)
{% endstep %}

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

Once you’ve added attributes to your screener, Dscout displays the potential reach of your screener in the top-right corner. This gives you an indication of how much of our Scout pool meets your criteria. To further refine your study’s reach, you might also choose to **exclude recent participants** or **balance the demographics of your participants**. You can access these settings by clicking **Settings** in the **Targeting attributes** side panel:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/v8g2c5nRN7bPwKVQUDm2/34783829002644)

For more information on balancing your participant demographics, see [Participant balance](/recruit-participants/dscout-scout-panel/participant-balance).

## Screener questions

When you’re ready to add questions to your screener, you’ll do so under the **Screener** tab. Screener questions fall into two categories:

* **Knockout questions:** Questions with disqualifying logic. With knockout questions, you designate a correct answer. If a participant selects anything other than that answer, they do not proceed with your screener, nor are they invited to participate in your research study. For more information, see [Knockout questions](/recruit-participants/dscout-scout-panel/knockout-questions).
* **Standard questions:** Questions that neither disqualify nor qualify candidates for your study.

To add questions to your screener, use the **Add** buttons in the left sidebar or the center of the builder:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/QhKeywc8fK669IDbnSyp/34716506931220)

You can combine knockout questions and standard questions, but we recommend you have at least one knockout question to help narrow down your candidates. In total, your screener can have 20 unique questions, including one photo and one video question. For a list of available question types, see [Question types in screeners](/recruit-participants/what-are-dscout-screeners/question-types-in-screeners).

If you'd like to change the order of your questions, ensure you're not in editing mode for the question you'd like to move. Then drag and drop the question to your preferred position.

## (Optional) Submit a screener for review

Once you have created your screener (and its associated Diary study or live interview study), you can submit it for review by a Dscout Research Advisor. This helps ensure that your Scouts have the best experience and that you'll receive the most useful responses. For more information, see [Optional pre-launch review for screeners and studies](/study-basics/design-a-study/optional-pre-launch-review-for-screeners-and-studies).


# Screener webpages

Webpages are automatically created for screeners you're sending to your own participants. These webpages offer all the information your applicants need to know about the opportunity.

You can also add custom messaging to the exit screens your externally recruited participants will see when they either successfully complete the screener or get knocked out from the screener. This is helpful in giving participants more information about your study.

When designing questions in the Screener tab of your screener, you can customize text in the "Thank you" section. Edit the Completion message for qualified applicants, and/or the Knockout message for disqualified participants.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/M2z1K8mLaH6sLVsAlJLr/34717343140756)

Before launching, you can check out what your webpage will look like from a participant's perspective by finding the Private share link at the top of the Overview tab and clicking **View**. Here, you'll also be able to preview your completion and knockout messaging. The previews will show the most up-to-date copy you’ve added.

Here's what a screener splash page looks like when a participant first opens it:

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FBXhgvQXaXmaNwR6XPYLT%2FRecruitment_approach%20(8).jpg?alt=media&amp;token=74f1d09e-cc32-48e9-971a-419be6d414c7" alt=""><figcaption></figcaption></figure>

Potential participants who've never used Dscout will be able to apply by simply providing their first name, last name, and email address. Read more in [Private screener onboarding flow for first-time Scouts](/recruit-participants/what-are-dscout-screeners/screener-flow-for-bring-your-own-participants).


# Screener review checklist

Screeners are used to recruit participants for your Dscout diary, interview, or single-session study; you have the ability to screen Dscout panel scouts or a panel of your own external participants.

Most often, your first step will be building your question script into the platform. Please see [Set up a screener](/recruit-participants/what-are-dscout-screeners/set-up-a-screener) for a quick walkthrough of the screener builder experience. If you have yet to draft your screener question script, check out [Example of an effective screener](/recruit-participants/what-are-dscout-screeners/example-of-an-effective-screener) for inspiration!

Once your screener is built in the Dscout platform, you’ll submit it for review and a Dscout Research Advisor will provide feedback within 2 business days. Read more about [Optional pre-launch review for screeners and studies](/study-basics/design-a-study/optional-pre-launch-review-for-screeners-and-studies).

But, you may wonder, what do Research Advisors review for? You might think, how can I expedite the review process by submitting a super stellar screener that is already in launch-worthy shape? Here is a guide for you to refer to.

Please note that this guide is neither exhaustive nor a replacement for the Research Advisor review, but rather a straightforward checklist to walk you through the essentials of a Research Advisor review.

## Is the screener technically sound?

### Are there any programming errors or omissions?

* The screener is free from grammatical errors.
* All fields on the Overview and Screener tabs have been filled.
* Knockout and Must Select logic is present and on the correct response options and/or questions in the Screener tab.
* Skip logic is present on the correct response options and/or questions and routes scouts to the correct prompts.
* Multiple-choice questions are correctly programmed as either single- or multiple-select.
* Open-ended questions are correctly programmed as either No Limit or 140 Characters.

## Does the screener adhere to our scout experience standards and inclusive [research guidelines](/getting-started/research-basics/inclusive-research-guidelines)?

* All language is actively inclusive and anti-racist.
* The screener has no more than 20 questions.
* Each scout is asked no more than 1 video prompt and 2 open ends.
* The screener does not expose scouts' Personally Identifiable Information.\*
* An appropriate incentive amount is set for the study(s) scouts will complete.
* Options for scouts to self-identify, select multiple, and select "I prefer not to respond" are present on all questions that collect sensitive personal information.
* Only essential demographic questions are included and, if possible/appropriate, Targeting Attributes are used.

## Will the screener find the scouts you are looking for and achieve your recruitment goals?

* Screener questions address all relevant research criteria.
* The screener teaser provides a high level of detail on the project without disclosing your knockout criteria.
* The screener teaser communicates what the follow-up studies will consist of (eg, "Selected scouts will be invited to a multi-activity diary study, with the potential of a follow-up interview study for an additional incentive.")
* The recruit is feasible within the Dscout platform.\*
* The screener title is scout-facing and fun.

## Does the screener adhere to Dscout design best practices?

* Multiple-choice response options are mutually exclusive and collectively exhaustive.
* The screener contains an open-ended question and a video prompt to fully "audition" scouts' ability to speak and write on the topic.
* Questions are not binary and allow scouts to self-select into the desired response. For example, rather than asking "Do you have a blue car?" the screener asks "Which of the following colors is your car?"
* Questions begin broad, then become more narrow. For example, before asking "What brand of sedan do you own?", the screener should confirm that the scout owns a car and that the car is a sedan.
* Screener questions only collect information from scouts that is needed to determine their fit for the study.

\*These points may necessitate a conversation with your Research Advisor.


# Example screener teasers

Your teaser is intended to provide participants with a general idea about the topic of your study. The best teasers include:

* Details about your project's goals
* The amount of time and number of activities your project entails
* The reward participants who complete your project can expect
* Any specific requests you'll make during your screener. For example, if your study is about how participants play with their pets, and you require them to take a picture of their pet in your screener, let participants know they need to be around their pet when they apply.

### Good teaser examples

* "We'd love you to take us on a tour of your refrigerator in an upcoming study that pays $20. Make sure you're at home before starting this application, because we'll ask you to answer a few questions and take a quick video of your fridge!"
* "It's getting to be that festive time of year again, and we're planning a special project that will last from Thanksgiving to New Years. Apply now for the chance to participate! If selected for this project, you'll share a little about what life is like for you over the holidays in a series of 6 activities over the next 8 weeks. Participants who complete this project will earn $300!"
* "Have you ever looked at something you use, own or wear and thought of a neat way to improve it? Now is your chance to share these ideas with product designers! Apply now for the chance to make $15 by completing a 1-Activity study all about making better stuff. You will need to record a 30-second video as part of this application."


# Example of an effective screener

Your screener design will depend heavily on the type of participant you want and your research design, meaning each screener will necessarily be different! However, we do have some tips for how to make the most of Dscout Recruit:

1. Watch our webinar all about screening with Dscout [here](https://pages.dscout.com/web-clinic-dscout-better-screening?utm_campaign=inbound\&utm_source=help_page\&utm_medium=better_screening)!
2. See our sample screener, below, for a little bit of inspiration and some quick tips.

### Screener: Magical Shopping

This screener was designed to find scouts who shop frequently.

The study would focus on how scouts would use a "magic button" if they had one (Q9, the video prompt in the screener, asked scouts their opinion on that topic).

{% hint style="success" %}
**Tip:** Focus your screener video prompt on your research topic to be sure scouts are interested in it!
{% endhint %}

It uses plenty of closed-ended questions to assist with filtering applications (i.e., selecting scouts for the study) along with a few articulation (open-ended and one video) questions to help determine scouts' ability to communicate effectively, as well as their creativity.

The screener comprises 14 questions, and our standard profile demographic questions would already be included in applications from scouts in our panel. You can explore [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes) for even more ways to target your audience.

{% hint style="success" %}
**Tip:** Keep your screener short and sweet to keep scouts' attention and interest. Save the meaty questions for your study!
{% endhint %}

#### Screener Details

The name and teaser are fun and engaging, meant to draw scouts' attention and pique their interest. Be sure to make use of Dscout's fun hero images! set these up in the Overview tab.

{% hint style="success" %}
**Tip:** To encourage quick responses, be creative with your screener name and teaser to capture scouts' attention.
{% endhint %}

#### Question Script

Questions are added under the **Screener** tab. Here are the 14 questions (including knockout/disqualifying questions) we would include:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/xGJLgpz3AwRxGurhJGLt/34717535111060)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/O29Scd9eeSa3FPfMcUC1/34717506401300)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/wIYsROAfGLhuU0A6sW6E/34717506403732)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/wIYsROAfGLhuU0A6sW6E/34717506403732)


# Screener flow for bring-your-own participants

When recruiting your participants, you have several options for how to get those participants on to Dscout. In this article, we’ll be outlining how to onboard participants via invite-link screeners, but you can see links to other onboarding flows below:

* [**Diary study onboarding flow for first time participants (profile not required)**](/diary-studies/manage-a-diary-study/diary-study-onboarding-flow-for-first-time-participants-profile-not-required)
* [**Diary study onboarding flow for first time participants (profile required)**](/diary-studies/manage-a-diary-study/diary-study-onboarding-flow-for-first-time-participants-profile-required)
* [**First time participant flow in a desktop interview study**](/interview-studies/manage-an-interview-study/first-time-participant-flow-in-a-desktop-interview-study)
* [**First time participant flow in a mobile interview study**](/interview-studies/manage-an-interview-study/first-time-participant-flow-in-a-mobile-interview-study)

Once you have set up your screener and sent the [**screener webpage link**](/recruit-participants/what-are-dscout-screeners/screener-webpages) out to your participants, they’ll go through the following steps to get onboarded on to the Dscout platform:

## Participants access through the webpage

Participants will see a webpage with information about the screener. On this page, participants will submit their name and email to create a Dscout account. They will also be prompted to review the Scout Terms & Conditions and Privacy Policy and select the checkbox to indicate they agree to them. See a copy of the Scout Terms & Conditions & Privacy Policy [**here**](https://dscout.com/legal/scout-terms).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/oi3kFx7EEtq8UIxNj997/14462861943956)

{% tabs %}
{% tab title="New User" %}
Participants whose email address has never been used to sign in to Dscout

Once participants select **Begin research study** on the public webpage, they will proceed to question 1 of the screener.
{% endtab %}

{% tab title="Returning User" %}
A participant whose email address has previously been used to sign in to Dscout:

Once participants select \*Continue\* on the Public Webpage they will be prompted to verify their email.

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/THDgInWtnh8pvxLM9IAT/13381844481556" alt="" width="375">

Participants will receive an email from [**participate@dscout.com**](mailto:participate@dscout.com) which contains the smart link. Once participants click the link in their email, they will be brought to Q1 of the screener.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/fjxMUHO6jrPRr6I38oAT/13381933458196)
{% endtab %}
{% endtabs %}


# Review screener responses

Participants will have the ability to submit applications as soon as you launch your screener (read more about submitting for review in [Optional pre launch review for screeners and studies](/study-basics/design-a-study/optional-pre-launch-review-for-screeners-and-studies)).

You'll first land in the **Questions** view of the **Responses** tab. This shows an aggregate view of answers to your questions:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/SLCQFfc45IgQJFKjK0XE/47543411354004)

The Participants view shows an individual application, along with quick navigation to other applicants.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JegXEnFtMLLMSKRSimLa/47543411358612)

Use participant ratings, filters, and sorting tools to help pick participants that are right for your study.

## Potential fit

All participants who are not knocked out will come into your screener as **Eligible**. Participants who have been knocked out (i.e., terminated or disqualified) by questions in your screener will not appear in the applications.

From there, you can choose Good, Possible, or Bad fits to determine which participants you want to invite to your study:

* **Good Fit**: Good for the study and a good quality application
* **Possible Fit**: A backup option for your study
* **Bad Fit**: Quality application, but not a good fit for your study
* **Low Quality**: Applications that are identified by the platform's machine learning to be insufficient (if, say, someone answers an unlimited open-end with just a few words)

To label individual participants, select “Eligible” in the righthand sidebar when viewing an entry:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/vzOnAyNhcA7HlraNag5o/30856879952916)

You can also label groups of participants at one time, by selecting the checkbox to the left of each participant avatar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/NVdXcY1jqaJt5gBmF7hs/47543411360020)

{% hint style="info" %}
Participants cannot see your labels! This is a feature designed for your personal organization of potential participants.
{% endhint %}

## Filtering by attributes

The filter icon (top right) shows options for sorting your participant applications.

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/FKIApnYUyOPeLUAewhWM/30856899102356" alt="" width="563">

Expand this menu to filter by:

* **Close ended responses:** focus on specific answers to a screener question
* **Primary attributes:** filter by participant demographics & behaviors
* **Participant groups:** filter by participant groups you’ve created
* **Tags:** filter by any tags you’ve applied
* **Study:** filter by any studies participants completed for your team

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Q0o7etSePJ7cqtnGaoa1/30856899106580)

All applications views and exports will respect filters you've applied.

## Notes, tags, and groups

When viewing an individual application, you'll see several sections in the righthand sidebar, including "Groups" and "Notes" which can be used to manage and organize your recruit.

### Notes

To make a note, simply type in the comment box in the lower right corner of the individual application, then select **Add note**. Participants cannot see notes. Type “@” followed by a name to mention your colleagues to draw their attention to your notes.

### Tags

Click and drag across open-ended answers or video transcriptions to tap, copy, or highlight text:

* Click the tag option to create or apply an existing tag. (See more about Dscout's tagging system in [Create and manage tags](/study-basics/analyze-studies/create-and-manage-tags).)
* Click the **Highlight** button that pops up above the highlighted text to add that highlight to the Notes sidebar.
* Click the **Copy as Quote** button to copy the quote, pre-formatted for you, to paste elsewhere.

### Groups

Create participant groups by clicking **Add to group** with an individual application. Add applicants to groups individually by checking the listed participant group:

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/lgXQIN5sLEoCxRtO8OSk/30856899111956" alt="" width="375">

Add participants to participant groups in bulk by selecting at least one application (from the Questions view), selecting anyone you want in a given group, and clicking **Add to Group**.

## Sorting participants

You can sort participants by a number of characteristics:

* Application date: sorts applicants based on date of application
* Name: sorts applicants alphabetically by their first name

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/dmGBFKiGevueUlfqWEi1/30856899113748" alt="" width="375">

You're able to sort participants in ascending or descending order. The default sort is Date, from newest to oldest; so, the most recent applications will be first in your view.

## Programming insight

Want to know which questions and answer choices disqualified participants? Check out the Programming insight in the Overview tab (this chart appears only after a screener is launched).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/NlgurAFeYA05d3zmkPLX/30857706284820)

## Export screener data

<img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/GfxJIStOKTTB0N2i1GEI/21708903402900" alt="" width="563">

To [export your screener data](/study-basics/analyze-studies/how-can-i-export-my-data), you'll click the export icon (a box with an arrow pointing down) in the top right corner of your screen. Export options include:

* **Application Photos and Videos:** Bulk download all media files in a .zip archive folder
* **Application Data:** A .csv file of all non-media questions and answers
* **Application Notes:** If you've written notes (described above), a .csv of all notes
* **Print/PDF:** 1 application per page PDF file, including the data you specify on the righthand side of the dialogue box
* **Crosstab:** A cross-tabulation determined by the options you select in the dialogue box

{% hint style="info" %}
Not seeing the export button? That likely means your Dscout access is limited; check out [User roles and permissions](/getting-started/dscout-quickstart-guide/user-roles-and-permissions) for details on seat types, and chat with your Account Owner about adjusting your seat access if needed.
{% endhint %}

## Close your screener

When you no longer need additional participants to apply for your study(s), it's time to close your screener. You'll still be able to access all of your applications, as well as add participants to your study. Closing your screener will simply prevent new participants from applying.

{% hint style="info" %}
Screeners will also automatically close two weeks after your launch date, or as soon as you reach your application limit.
{% endhint %}

Just click the **Close** button in the top right corner. Once a screener is closed, it cannot be reopened.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/lnBzZHq3Z5AFqzkYOrn3/47543426559508)

Next, launch your [diary study](/diary-studies/what-are-diary-studies-in-dscout/set-up-a-diary-study), [usability test](/usability-tests/manage-a-usability-test/launch-a-usability-test), [media survey](/media-surveys/manage-a-media-survey/launch-a-media-survey), or [interview study](/interview-studies/manage-an-interview-study/launch-an-interview-study) with the participants you've selected.


# Add participants from a screener to a study

If you've used a Dscout screener to recruit participants, you can add those participants to a study when you're ready to hear more from them.

Here are some things to keep in mind when adding participants from a screener to a study.

* Participants added to **draft studies** will be invited when the study is launched.
* Participants added to **launched studies** will be invited immediately.
* **Partner Panels participants** can only be added to one Dscout study.
* Participant cannot be added manually to **intercept studies**, which recruit based on live behavior.

**To add participants from a screener to a study:**

{% stepper %}
{% step %}
Navigate to the **Responses** tab of your screener.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FvA2qZojm1hIEyp3pIszC%2FAdd_from_screener.jpg?alt=media&amp;token=db75fb3b-fbd8-4595-a02a-9b39dab352df" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select the participants you want to add to a study using the checkboxes beside their names. The bulk action toolbar is displayed.
{% endstep %}

{% step %}
Click **Invite to study** in the toolbar. A list of studies within your project is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FsrC8tbfHF3DnT0IqcSsz%2FInvite_to_mediausability%20(2).jpg?alt=media&amp;token=9e6300c8-195c-4fae-8681-6474acf5f42b" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select the study you want to add your participants to. Then, click **Invite**.

{% hint style="info" %}
**Note:** If a participant has already been added to a study, that study is greyed out/unavailable.
{% endhint %}

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FhEnixQYPLSjzAicDSvWq%2FInvite_to_mediausability.jpg?alt=media&amp;token=9a6a32ba-d7f8-42c2-9290-dadefee6388b" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**(Launched diary and interview studies only)** Verify or edit the invite message for your study. Then, click **Send x invites**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2Foj5NVYg0a6iyCYRdaTG1%2FScreenshot%202026-08-04%20at%209.58.18%E2%80%AFAM.png?alt=media&amp;token=0adbab10-72c4-45fd-a539-de01d8e3bc3e" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** For diary studies with data translation enabled, you'll be prompted to enter your invite message in both English and your selected language.
{% endhint %}
{% endstep %}
{% endstepper %}

Now, your selected participants are added to your study. If you've yet to launch your study, these participants will automatically be invited when you do launch it. If you've already launched your study, the participants will receive invitations to participate immediately.


# Report an applicant in a screener

Dscout takes pride in the quality of our Scout Panel and Partner Panels. So, if you have concerns about the quality, honesty, or integrity of a screener applicant, you can report them directly from your screener. Reporting sends your concern to Dscout Support for review.

## Report an issue with an applicant or response

{% stepper %}
{% step %}
Navigate to the **Responses** tab of your screener.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FrDj0fvWxRmfTZLiJKzMG%2FScreener_issue%20(3).jpg?alt=media&amp;token=115553b8-2f63-4e6c-9238-4827414c6502" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Participants** in the left sidebar. Then, select the participant whose response you want to report. The participant’s details are displayed in the right sidebar.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FuXH3xID2rmddMsATLMzh%2FScreener_issue%20(2).jpg?alt=media&amp;token=62f4751d-b916-41e0-845f-c63d55adc322" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click the three-dot icon in the right sidebar. Then, select **Report an issue**. A confirmation modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FCbvg4H5SrCbm4AR1gaO2%2FScreener_issue%20(4).jpg?alt=media&amp;token=9cbfc0f3-68eb-4b00-bda5-0017e8fe4a92" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select from the following issue types, then click **Next**:

| Issue type      | Possible reason                                                                                                                                                                                           |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Participant** | <ul><li>Low effort.</li><li>Duplicate account.</li><li>Instructions not followed.</li><li>Potential Gen AI usage.</li><li>Dishonesty.</li><li>Off-topic content.</li><li>Inappropriate content.</li></ul> |
| **Technical**   | <ul><li>Incomplete or missing.</li><li>Low audio or video quality.</li></ul>                                                                                                                              |
| {% endstep %}   |                                                                                                                                                                                                           |

{% step %}
Select a **Reason**.
{% endstep %}

{% step %}
Enter a description of the issue.
{% endstep %}

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

Now, your report is sent to Dscout Support who will review the participant’s response.

{% hint style="info" %}
**Note:** Unlike Dscout studies, screeners don’t include refund, exclusion, or backfill options as part of a report. Reporting a response simply sends your concern to Dscout for review.
{% endhint %}

## Set an applicant aside

You can’t exclude applications from a screener the way you can in Dscout studies. Instead, use the applicant’s **Fit** rating to keep them out of the participants you select for your study. Assigning a `Bad Fit` or `Low Quality` rating removes the applicant from your `Good Fit` picks, while keeping their application accessible if you need it later.

For more information on fit ratings, see [Review screener responses](/recruit-participants/what-are-dscout-screeners/review-screener-responses#potential-fit).


# Dscout Scout Panel

Dscout’s Scout Panel is our proprietary pool of research participants. It is only available through Dscout. We stand behind the quality of the Scout Panel, so you can collect thoughtful responses and useful insights across study types.

When you recruit from the Scout Panel, you can shape your audience before launch and refine your selection after applications arrive. Use targeting tools to reach the right people, screening logic to qualify applicants, and selection tools to hand-pick or auto-select participants who match your research goals.

{% hint style="info" %}
**Note:** Some recruiting tools in this section are only available when recruiting from the Dscout Scout Panel.
{% endhint %}

## Ways to narrow your recruit

Use these tools to define who can apply:

* [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes) to filter participants by demographics, behaviors, and custom criteria.
* [Knockout questions](/recruit-participants/dscout-scout-panel/knockout-questions) to disqualify applicants who do not fit your study.
* [Exclude recent participants from studies](/recruit-participants/dscout-scout-panel/exclude-recent-participants-from-studies) to avoid hearing from the same Scouts too often.
* [Participant balance](/recruit-participants/dscout-scout-panel/participant-balance) and [Ethnicity balance](/recruit-participants/dscout-scout-panel/ethnicity-balance) to create a more balanced sample.
* [Expressiveness](/recruit-participants/dscout-scout-panel/expressiveness) to prioritize clear, thoughtful communicators.

## Ways to select participants

After your screener or study collects applications, you can choose participants in two ways:

* **Hand-pick participants:** Review applications, compare responses, and invite the best-fit Scouts. For more information, see [View applications and select participants](/recruit-participants/what-are-dscout-screeners/review-screener-responses).
* **Auto-select participants:** In supported study types, Dscout can automatically advance qualified applicants based on your targeting and screening criteria.

## Learn more about Scout Panel tools

Explore these related articles:

* [Standard targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/standard-targeting-attributes)
* [Behavioral targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/behavioral-targeting-attributes)
* [Custom targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/custom-targeting-attributes)
* [Programming insight](/recruit-participants/dscout-scout-panel/programming-insight)


# Exclude recent participants from studies

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests (auto-recruit)</strong></td><td>true</td></tr><tr><td><strong>Media surveys (auto-recruit)</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr><tr><td><strong>AI moderated studies (auto-recruit)</strong></td><td>true</td></tr></tbody></table>

Recruiting from the Dscout Scout Panel is a fast and easy way to find participants for your research. However, if you’re running similar studies close together, you may want to ensure you hear from new voices—not the same Scouts who’ve already shared their insights.

With **activity filters** in screeners, usability tests, and media surveys, you can prevent Scouts from participating in your studies if they’ve already done so in the last 90 days. This ensures you’re recruiting a fresh group of Scouts every time.

{% hint style="info" %}
**Note:** Activity filters are only available when auto-recruiting from Dscout’s pool of participants (known as Scouts). When using any other recruitment method, invite only participants you want to participate in your studies.
{% endhint %}

## Activity filter options

Activity filters are enabled on screeners and studies individually, but you can choose to apply them in one of two ways:

* **Within this project:** Applies your selected filters only to Scouts who have taken part in a screener or study in this same Dscout project.
* **Within this account:** Applies your selected filters to Scouts who have taken part in any screener or study across your Dscout account, regardless of project.

From there, you can choose to exclude participants who fall into the following categories:

* **Study participants from the last 90 days:** Scouts who have participated in a study in the last 90 days.
* **Qualified screener applicants from the last 90 days:** Scouts who have applied to and qualified for a screener in the last 90 days, regardless of study completion. Keep in mind that Scouts who have applied to screeners in the last 90 days but have not qualified will not be excluded by this filter.
* **Both:** Excludes all Scouts who fall into either of the above categories.

The following options are selected by default:

| Screener default activity filters                                                                   | Study default activity filters                                                           |
| --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| <ul><li>Within this project.</li><li>Qualified screener applicants from the last 90 days.</li></ul> | <ul><li>Within this project.</li><li>Study participants from the last 90 days.</li></ul> |

## Access activity filters

{% stepper %}
{% step %}
Navigate to the **Screener** tab of your screener or study.
{% endstep %}

{% step %}
Click **Targeting attributes** in the left sidebar. The Targeting attributes side panel is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/O8Gb88qeZ94oUaKrDUlt/38476692919956)
{% endstep %}

{% step %}
Click **Settings** in the Targeting attributes side panel.
{% endstep %}

{% step %}
Here, customize the activity filters to fit your research needs.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/FLN1kGCAaS3GXPFjI7iC/38476692920468)
{% endstep %}
{% endstepper %}

Now, when you launch your screener or study, only the Scouts in Dscout’s pool who meet your criteria will be able to apply to your study.


# Knockout questions

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests (auto-recruit)</strong></td><td>true</td></tr><tr><td><strong>Media surveys (auto-recruit)</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr><tr><td><strong>AI moderated studies (auto-recruit)</strong></td><td>true</td></tr></tbody></table>

Recruiting for studies, you want to find people who fit your research needs as closely as possible. To help, you can use knockout questions to eliminate applicants if their answers don’t line up with what you’re looking for. For example, let’s say you’re looking for participants who exercise at least three times a week. You can use a knockout question to disqualify applicants who indicate they exercise less frequently.

{% hint style="success" %}
**Tip:** We recommend always starting a screener or study with a knockout question or two. This will save applicants time by letting them know right away if they aren’t qualified, but it will also help weed out those who won’t be helpful to your study.
{% endhint %}

## How do knockout questions work?

When building a screener or study, you’ll add knockout questions and select which answers are acceptable (**May select**) and which are not (**Knockout**). These questions are then presented to applicants first so they can find out as quickly as possible if they do not qualify. When an applicant selects an answer you’ve marked **Knockout**, they are sent to the end of the screener or study and don’t count toward your total participants.

**Note:** If **Multi-select** is enabled for a question, you’ll also see an option to mark answer choices as **Must select**. Participants must select these answers to qualify for your study. Those who don’t are disqualified, regardless of their other selections.

Applicants disqualified by knockout questions won’t show in your final results, but you can view how many people were disqualified by each question from within your screener or study. For more information, see [Programming insight](/recruit-participants/dscout-scout-panel/programming-insight).

## Knockout questions in screeners

When building a screener, you’ll add knockout questions on the **Screener** tab.

**To add a knockout question to a screener:**

{% stepper %}
{% step %}
Navigate to the **Screener** tab of your screener.
{% endstep %}

{% step %}
Click **+ Add knockout question** in the builder or in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6yIsXgoCtHX3M7YqYAsO/36687935403028)
{% endstep %}

{% step %}
Select **Multiple choice**. (Or, select **Add from question bank** to add a question you have saved. For more information on saved questions, see [Question banks](/study-basics/question-types/question-banks).)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/fEIs4BoESvInRv6897T4/36687945903892)
{% endstep %}

{% step %}
Enter a **Prompt**.
{% endstep %}

{% step %}
Enter your answer **Choices**.
{% endstep %}

{% step %}
Select **Knockout** beside the answers you want to disqualify applicants.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/d423VfHps849p192zQY5/36687935406740)
{% endstep %}

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

Now, once you launch your screener, applicants who select answers you’ve marked **Knockout** will be disqualified and sent to the end of your screener.

## Knockout questions in usability tests and media surveys

When building a usability test or media survey, you’ll add knockout questions on the **Screener** tab.

{% hint style="info" %}
**Note:** Knockout questions are only available in studies that auto-recruit from Dscout’s pool of participants. When using other recruitment methods, it’s expected that you have already in some way screened the participants you invite.
{% endhint %}

**To add a knockout question to a usability test or media survey:**

{% stepper %}
{% step %}
Navigate to the **Screener** tab of your study.
{% endstep %}

{% step %}
Click **+ Add** beneath **Screener questions** in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/CYo0W8UdLBswFsG4q6vD/36687935408148)
{% endstep %}

{% step %}
Select **Multiple choice**. (Or, select **Add from question bank** to add a question you have saved. For more information on saved questions, see [Question banks](/study-basics/question-types/question-banks).)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/D7SoBFDTTvxUwDcwmMDT/36687935409428)
{% endstep %}

{% step %}
Enter a **Prompt**.
{% endstep %}

{% step %}
Enter your answer **Choices**.
{% endstep %}

{% step %}
Select **Knockout** beside the answers you want to disqualify applicants.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/tqo3lGNPXlGL2dfqbWbc/36687945908628)
{% endstep %}

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

Now, once you launch your study, applicants who select answers you’ve marked **Knockout** will be disqualified and sent to the end of your study.


# Targeting attributes

When recruiting for a study, it’s important to only find people who fit your research needs. To help, you can use targeting attributes to ensure participants meet basic requirements to qualify. Here’s an example: You’re conducting a study on streaming services and only want to hear from Hulu or Netflix subscribers. With targeting attributes, you can identify those people and disqualify anyone else.

{% hint style="info" %}
**Note:** Targeting attributes are only available when recruiting from the Dscout Scout Panel. When inviting your own participants, it is up to you to properly screen your participants to ensure they meet your requirements.
{% endhint %}

Dscout offers three categories of targeting attributes:

| Category                            | Description                                                                                                                                                                                                                                                                                                                         | Availability                                                                                    |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Standard targeting attributes**   | Pieces of information Scouts either self-disclose in their Dscout profiles or can answer in a simple screener question. Think demographics, like age, gender, and location. For more information, see [Standard targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/standard-targeting-attributes). | All Dscout plans                                                                                |
| **Behavioral targeting attributes** | Browsing data collected for Scouts who’ve enrolled in Dscout XT. Think website visitation, like how often a Scout visits amazon.com. For more information, see [Behavioral targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/behavioral-targeting-attributes).                                    | All Dscout plans                                                                                |
| **Custom targeting attributes**     | Attributes custom-built in partnership with your Dscout Account team to fit your unique research needs. For more information, see [Custom targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/custom-targeting-attributes).                                                                         | Custom attributes are a **paid add-on**. Contact your Dscout Account team for more information. |

## Add targeting attributes to a screener or study

Targeting attributes can be added to screeners or studies recruiting from the Dscout Scout Panel. When building, you’ll add targeting attributes on the **Screener** tab (or the **Intercept** tab of intercept studies).

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4MbHVTO6pKEDkxrwhOhn/46606558954260)

## Targeting attributes in analysis

Targeting attributes are not only useful when finding participants—they’re also helpful when analyzing results. Dscout automatically creates participant groups based on certain targeting attributes. For example, if you used the **Marital status** attribute to find participants who are married or in domestic partnerships, you’d see the following groups during analysis:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ttIg7VRgL7c1Zip7HVA2/46606574525716)

These groups function the same as other participant groups, so you use them to filter, edit them, or delete them as needed. For more information, see [Participant groups](/recruit-participants/working-with-participants/scout-groups).

Targeting attributes are available in exports. Since they function similarly to participant groups, they’ll appear in the export file alongside other groups you may have utilized. For more information, see [How can I export my data?](/study-basics/analyze-studies/how-can-i-export-my-data).


# Standard targeting attributes

Standard targeting attributes are one of three attribute types offered by Dscout to help you recruit participants. These attributes are pieces of data self-disclosed by members of our Dscout Scout Panel either during account creation or that can be answered through a simple screener question.

Standard attributes are broken into two categories: **Primary** and **Non-primary**.

## Primary attributes

Primary attributes are required in order for Scouts to create a Dscout account. These attributes include:

* Age (required)
* Country (required)
* Ethnicity
* Education
* Employment
* Gender
* Household income
* Household composition
* Job title

When you add a primary attribute, only participants who meet your chosen criteria will see your opportunity in the Dscout app and be able to apply. Those who don’t won’t.

{% hint style="success" %}
**Tip:** Primary attributes are denoted in the builder with a star as seen below:
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/aDPyJr7XoUphzboJ19P8/46246214878484)

## Non-primary attributes

{% hint style="info" %}
**Note:** Non-primary attributes are not available in intercept studies.
{% endhint %}

Non-primary attributes are optional when Scouts create a Dscout account. These attributes include:

* Apps & accounts
* Devices
* Shopping
* Subscriptions
* Marital status
* Pets
* General work industry
* Parent status

When you add a non-primary attribute, any Scouts who have not already provided this information will simply answer the question as part of the screening process. Scouts who *have* provided this information previously but don’t meet your requirements won’t be able to apply.

{% hint style="info" %}
**Note:** If a Scout has not updated or answered a question related to your selected non-standard attributes in the last three months, they'll be re-asked as part of your screener. If their answer meets your criteria, they'll progress. If their answer doesn't, they'll be disqualified.
{% endhint %}

For more information on adding targeting attributes to a screener or study, as well as other targeting attributes available in Dscout, see [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes).


# Behavioral targeting attributes

Behavioral targeting attributes are one of three attribute types offered by Dscout to help you recruit participants. These attributes rely on **website visitation** data collected for Scouts who have joined Dscout XT, which means you can recruit based on what Scouts *do* and not just what they *say*.

Let’s say you want to target Scouts who have visited amazon.com in the last two weeks. You can do that using behavioral targeting attributes.

## Behavioral attribute parameters

When adding behavioral attributes to a screener or study, you can keep things simple by only requiring Scouts to have visited one website in a set timeframe. Or, you can combine requirements using AND/OR conditions.

For example, you can recruit Scouts who have:

*\[visited **amazon.com** OR **lowes.com** in the last 14 days] AND \[visited **chatgpt.com** in the last 30 days]*

In a single study, you can have two groups (separated by an AND condition), and each group can have up to three websites (separated by OR conditions). You can assign each group its own timeframe ranging from the last 14 days to the last 90 days.

## Add behavioral attributes to a screener or study

Behavioral attributes can be added to any screener or study recruiting from the Dscout Scout Panel. You’ll add these attributes on the **Screener** tab (or the **Intercept** tab of intercept studies).

{% stepper %}
{% step %}
Navigate to the **Screener/Intercept** tab of your screener or study.
{% endstep %}

{% step %}
Select **Behavioral attributes** in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/Efrx8ZlX5Is85FREnmJB/47839761942676)
{% endstep %}

{% step %}
Select **Website visitation** in the right sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/oZaG0H7JBLmZPEDwjwYM/47839761944724)
{% endstep %}

{% step %}
Select a **Website** you want participants to have visited.

{% hint style="success" %}
**Tip:** Click **Add website (OR condition)** to add up to three websites to this group. Participants must only have visited one website in each group.
{% endhint %}
{% endstep %}

{% step %}
Select a **Timeframe** in which you want participants to have visited your selected website.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/oiC1CWnTCevMeVLICboT/47839702059540)
{% endstep %}

{% step %}
(Optional) Click **Add AND condition** to add a second group of up to three websites. Participants must meet the requirements set in the first group and this second group.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4Bh4dizJQ1q3qNPtWxgZ/47839761950100)
{% endstep %}

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

Now, the selected attributes are added to your study. In the right sidebar, you'll see an estimated number of **Reachable Scouts** based on your requirements. This gives you an idea of how many people in the Dscout Scout Panel could potentially qualify for your study:

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FSnERMTVORRBmCGBSdWrK%2FXT%20updates.jpg?alt=media&amp;token=62a15858-164d-4610-9e6d-f09bf222da43" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** This estimate updates as you add or update targeting attributes, so keep an eye on it as you build.
{% endhint %}

When you launch your study, only Scouts who meet your set criteria will be able to apply for your study in the Dscout app. Those who don’t meet your criteria won’t see the opportunity at all.

## Request a website visitation domain

If you don't see a domain you need when targeting by website visitation, you can request we add it to the list of options. You'll provide information on how many participants you're hoping to recruit on that domain and how often you'll need to recruit them. Our Data Science team will review your request and reach out with a decision on whether we're able to fulfill the request or not.

{% stepper %}
{% step %}
Follow the steps above to add the **Website visitation** attribute to your study.
{% endstep %}

{% step %}
Click **Submit a request**. The domain request modal is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1YhhptfcOZVsl1ciEmld/47839761952660)
{% endstep %}

{% step %}
Enter the **Domain name**. For example, **yourcompany.com**.

{% hint style="info" %}
**Note:** Only top-level domains are supported, not individual pages within a domain. For example, you can request **yourcompany.com** but not **yourcompany.com/about**. For more information on how to customize attributes further, see [Custom targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes/custom-targeting-attributes).
{% endhint %}
{% endstep %}

{% step %}
Enter the approximate number of participants you're hoping to reach under **What kind of reach are you looking for?**
{% endstep %}

{% step %}
Enter some information about how you'll use this domain under **How important is this domain to your research?** Include anything you think is relevant, including how often you'll target participants on this domain or your research goals.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4BgS7WXYDx7g1N67Du6h/47839702066964)
{% endstep %}

{% step %}
Click **Submit request**.
{% endstep %}
{% endstepper %}

Now, your domain request is sent to our Data Science team. They will review the provided information and reach out in about a week.

For more information about other targeting attributes available in Dscout, see [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes).


# Custom targeting attributes

{% hint style="info" %}
Custom attributes are a **paid add-on**. Contact your Dscout Account team for more information.
{% endhint %}

Custom targeting attributes are one of three attribute types offered by Dscout to help you recruit participants. These attributes leverage the wide breadth of behavioral data collected for Scouts who have joined Dscout XT, but they’re tailor-made to fit your organization’s unique needs.

## Custom attribute categories

Depending on your recruitment need, you’ll work with your Dscout Account team to create your custom attributes. However, they’ll always fall into one of these four categories:

* **Journey:** Identifies participants who move between two specific domains or URLs.
* **Frequency:** Identifies participants based on how often they engage with a specific domain or URL.
* **Engagement duration:** Identifies participants based on how much time they spend on a specific domain or URL.
* **Multi-condition:** Identifies participants based on a combination of the previous three categories.

For example, if you want to target participants who have visited your company’s website and ChatGPT within 60 seconds of each other, you can do that using a custom targeting attribute.

## Add custom attributes to a screener or study

You can combine up to 10 custom targeting attributes in a single screener or study using OR conditions to ensure you reach just the right audience. You’ll add these attributes on the **Screener** tab (or the **Intercept** tab of intercept studies).

{% hint style="info" %}
**Note:** Before you can add custom attributes to a study, they must first be created for your organization and added to your Dscout account. For more information, contact your Dscout Account team.
{% endhint %}

{% stepper %}
{% step %}
Navigate to the **Screener/Intercept** tab of your screener or study.
{% endstep %}

{% step %}
Select **Behavioral attributes** in the left sidebar.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JXDc4GQUdAd5ydP8y4sk/46246655562260)
{% endstep %}

{% step %}
Select **Custom attributes** in the right sidebar. The custom attributes block is added to the builder.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/C5WNXwBy5f1GZUGGzJ8k/46246687208084)
{% endstep %}

{% step %}
Select an **Attribute**. This drop-down displays all of your organization’s custom attributes.
{% endstep %}

{% step %}
Select a **Timeframe** in which you want participants to meet the selected attribute’s requirements.

{% hint style="success" %}
**Tip:** Once you’ve added one attribute, click **+ Add attribute (OR condition)** to add more. You can combine up to 10 custom attributes.
{% endhint %}

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/EFkyKpnJ7108uddHT7x2/46246655563156)
{% endstep %}

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

Now, the selected attributes are added to your study. When you launch your study, only Scouts who meet your set criteria will be able to apply for your study in the Dscout app. Those who don’t meet your criteria won’t see the opportunity at all.

## Create custom attributes

Custom attributes are created in collaboration with your Dscout Account team to ensure they meet your specific needs. If you want to explore your options with custom attributes, contact your Dscout Account team.

For more information about other targeting attributes available in Dscout, see [Targeting attributes](/recruit-participants/dscout-scout-panel/targeting-attributes).


# Participant balance

To ensure your responses are balanced across major demographics (age, ethnicity, and gender), you can enable participant balance during recruitment.

{% hint style="info" %}
**Note:** This feature is only available when recruiting participants from Dscout's Scout Panel in the United States.
{% endhint %}

With this setting enabled, responses from any of the following segments will be capped at 65% of your total n-size:

| Segment category | Segment breakdown                                                                                                                                                                                                                                                                               |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Age**          | <ul><li>Under 13</li><li>13-17</li><li>18-24</li><li>25-34</li><li>35-44</li><li>45-54</li><li>55-64</li><li>65-74</li><li>75-99</li></ul>                                                                                                                                                      |
| **Ethnicity**    | <ul><li>American Indian or Alaska Native</li><li>Asian</li><li>Black or African American</li><li>Hispanic or Latinx</li><li>Middle Eastern or North African</li><li>Native Hawaiian or other Pacific Islander</li><li>White</li><li>Prefer to self-identify</li><li>Prefer not to say</li></ul> |
| **Gender**       | <ul><li>Woman</li><li>Man</li><li>Non-binary</li><li>Prefer to self-identify</li><li>Prefer not to say</li></ul>                                                                                                                                                                                |

## Enable participant balance

Participant balance can be enabled when recruiting US-based participants from the Dscout Scout Panel.

{% stepper %}
{% step %}
Navigate to the **Screener** or **Intercept** tab of your study.
{% endstep %}

{% step %}
Select **Standard targeting** in the left sidebar. The targeting attributes sidebar is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/0ey0EeD7HgfiCA1Jj1qh/47954790665236)
{% endstep %}

{% step %}
Click **Settings** in the right sidebar.
{% endstep %}

{% step %}
Set the **Balance participant demographics** toggle to **ON**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/bgb4xxcMYUTKuuA8bmko/47954784707988)
{% endstep %}

{% step %}
*(Optional, screeners only)* Click **Customize ethnicity balance** to enter custom percentages for each ethnicity segment. No ethnicity will be allowed to exceed its respective percentage of your total n-size when launched.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1gxKIeGfzlcE33AXyYNE/47954784709908)
{% endstep %}
{% endstepper %}

Now, participant balance is enabled for your screener or study. Once launched, no individual segment will be allowed to account for more than 65% (or your custom percentage if enabled on screeners) of your total number of desired responses.


# Ethnicity balance

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Screeners</strong></td><td>true</td></tr><tr><td><strong>Usability tests (auto-recruit)</strong></td><td>true</td></tr><tr><td><strong>Media surveys (auto-recruit)</strong></td><td>true</td></tr><tr><td><strong>Intercept studies</strong></td><td>true</td></tr><tr><td><strong>AI moderated studies (auto-recruit)</strong></td><td>true</td></tr></tbody></table>

You may already be familiar with the [Participant balance](/recruit-participants/dscout-scout-panel/participant-balance) control which ensures a balanced sample across major demographics (i.e. age, ethnicity, gender) by limiting samples within each segment to 65%. The **Ethnicity Balance** feature allows you to further customize your participant pool by editing the maximum number of responses allowed per ethnicity group in a given screener, usability test, or media survey.

To access this feature, navigate to the **Overview** tab of your screener or **Screener** tab in your study, and toggle on the Balance feature.

In screeners, you can click Customize Ethnicity Balance to view the percentages grid and further customize.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1QPROc0x4bNBydCpHnpt/36684746334100)

This feature gives you more flexibility in creating a well-balanced mix of participants or narrowing your focus on one or more specific ethnic groups. For example, if you wanted to see no more than 25% of responses from participants who identify as White, you’d set the percentage next to “White” to be 25%. From there, you’d be able to customize the percentages for all other groups. Once the maximum percentage you set is reached, participants in that ethnicity group will no longer be able to view your screener or studies.

Similarly, if you wanted to see only responses from participants who identify as Black or African American, you’d set the percentage next to “Black or African American” to be 100%, and all other percentages to be 0%.

{% hint style="info" %}
**Note:** Sum of percentages must be equal to or greater than 100%.
{% endhint %}


# Expressiveness

During analysis, Dscout can automatically detect how expressive applicants are in their responses. Expressiveness lets you get an idea for how engaged each participant was while submitting their answers to your screener.

Expressiveness is determined by a proprietary machine learning algorithm. Some factors that play into an applicant's expressiveness include:

* Linguistic features of participants’ open-ended and video responses.
* Metadata from their videos.
* Their ability to follow instructions.

When reviewing responses, you can sort based on expressiveness. Sorting by expressiveness is a good way to randomize responses during analysis, and it also helps you find higher quality responses first.

**Screeners, usability tests, media surveys, intercept studies, AI moderated studies:**

Navigate to the **Participants** view of the **Responses** tab. Then, click the filter icon at the top of your participants list. Here, you can select to either sort from **Most expressive to least** or **Least expressive to most**:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/jCGX7S4J6uXlNngeLBa7/47543383411604)

Don’t forget to also [view applications and select participants](/recruit-participants/what-are-dscout-screeners/review-screener-responses), to make sure you’re focusing on the participants and topics you need.

**Diary studies:**

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/JLeaoBLNfwqMWqPhRtMK/4406310295828)

To sort by Expressiveness in diary studies: Expand the "Sort by" section in the top right of the Entries Grid in Diary, then select Expressiveness. Participants will automatically be sorted from most to least Expressive.


# Programming insight

When recruiting participants, it can be useful to see where applicants are most often being disqualified. In screeners, usability tests, and media surveys, you can see exactly how many applicants were disqualified by each of your knockout questions. Then, you can use that data to update your knockout logic to either be more or less inclusive depending on your needs.

{% hint style="info" %}
Programming insight is only available when auto-recruiting from the Dscout Scout panel.
{% endhint %}

Once you launch your screener or study, you'll find programming insights on the **Overview** tab:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/CPJERknDybCKjPK22ue6/35527443273108)

{% hint style="info" %}
If your participant numbers are low and one question is disqualifying most of your applicants, consider whether your requirements for that question can be more flexible.
{% endhint %}


# Partner Panels

Partner Panels are a way to expand your research reach beyond Dscout’s Scout Panel, your Private Panels, or other participants you may invite on your own. With Partner Panels, you can recruit directly from Dscout’s trusted third-party partners like Respondent, letting you find participants for even the most niche research needs. Want to hear from people who live in specific parts of the world? How about individuals who work in ultra-specific industries? Thanks to Partner Panels, you can.

{% hint style="info" %}
**Note:** Partner Panels currently support recruitment through Respondent. However, Dscout plans to support additional platforms in the future.
{% endhint %}

## Available countries

Partner Panels grant you access to participants in the following countries:

* Australia
* Brazil
* Canada
* Colombia
* Denmark
* Finland
* France
* Germany
* India
* Indonesia
* Ireland
* Italy
* Japan
* Kenya
* Mexico
* Netherlands
* New Zealand
* Norway
* Philippines
* Poland
* Portugal
* Singapore
* South Africa
* Spain
* Sweden
* Switzerland
* United Kingdom
* United States

You can learn more about how Respondent powers Dscout's Partner Panels in Respondent's [Panel Book](https://cdn.prod.website-files.com/681b20d52ce4849a8d67ec3b/6892e077d18722004625e7a2_Panel%20Book%20-%202025.pdf).

## Recruitment methods

Recruiting from Partner Panels is easy—and you never have to leave Dscout to do it. You can recruit participants from Partner Panels in two ways:

* **Recruit using a screener:** Build a screener with targeting attributes and screener questions. Once launched, your screener is made available to participants on our Partner Panels. You can then review their responses right in Dscout and add those who qualify to your studies. For more information, see [Recruit from partner panels using a screener](/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener).
* **Auto-recruit (usability tests and media surveys only):** Add targeting attributes and screener questions to your study. Once launched, the screener portion of your study is made available to participants on our Partner Panels. Those who qualify are then automatically directed to Dscout to complete the rest of your study. For more information, see [Auto-recruit from partner panels](/recruit-participants/partner-panels/auto-recruit-from-partner-panels).

Whichever option you choose, you’ll always be able to tell when a participant came from Partner Panels by looking for the Partner Panels badge during analysis:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/6alc5sVxbazbNydRhpXz/41239385577108)

<details>

<summary>Does recruiting from Partner Panels cost extra?</summary>

Additional activity credits may be required for participants recruited from Partner Panels. For more information, contact your Dscout Account Manager.

</details>

For more information on Partner Panels, see the following articles:

* [Recruit from partner panels using a screener](/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener).
* [Auto recruit from partner panels](/recruit-participants/partner-panels/auto-recruit-from-partner-panels).
* [How are partner panels participants paid](/recruit-participants/partner-panels/how-are-partner-panels-participants-paid)


# Recruit from Partner Panels using a screener

Building a Partner Panels screener works the same as building any other screener in Dscout. When creating your screener, you’ll select Partner Panels as your recruitment method, then you’ll define your targeting attributes and write your questions as you normally would.

{% hint style="info" %}
**Note:** You can only choose one recruitment approach for your screener. So, choosing to recruit from Partner Panels means your screener will only be available on our third-party partner platforms.
{% endhint %}

**To create a Partner Panels screener:**

{% stepper %}
{% step %}
In your Dscout project, open the **Screeners** tab.
{% endstep %}

{% step %}
Click **Create screener**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FR7H7KHGE4G8LdFJWthse%2FUntitled%20-%202026-07-15T121251.249.jpg?alt=media&amp;token=e68f2790-7149-4ae6-993f-f34298fe19d3" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select **Recruit from Dscout's Partner Panels** as your recruiting approach.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FXrwuBfuS6tBtgtdefQsk%2FRecruitment_approach.jpg?alt=media&amp;token=21e7f303-1c5d-4b40-b483-37fd326477ff" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Continue**.
{% endstep %}

{% step %}
Enter a screener **title**.
{% endstep %}

{% step %}
Click **Create screener**.
{% endstep %}
{% endstepper %}

Now, build your screener by adding targeting attributes and screener questions. (Be sure to refer to the next section to understand the slight differences between a standard Dscout screener and a Partner Panels screener.) And when you’re ready, submit your screener for review so we can open it for participants.

{% hint style="info" %}
**Note:** You cannot skip review for Partner Panels screeners. Our typical turnaround time for screener review is 1–2 business days.
{% endhint %}

## Requirements and limitations

While recruiting from Partner Panels works very similarly to other Dscout recruiting methods, we impose a few limitations to ensure compatibility with our third-party partners.

### Piping logic

Piping logic (the ability to recall participants' responses in subsequent questions) is not currently supported when recruiting from Partner Panels.

### Targeting attributes

Targeting attributes automatically filter who can apply to your screener or study based on information available in their profile with our third-party partners. When recruiting from Partner Panels, the following targeting attributes are available:

| Category              | Attributes                                                                                                                                                                                                                                          |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Demographics          | <ul><li>Country. (For more information on available countries, see <a href="/recruit-participants/partner-panels">Partner Panels</a>.)</li><li>Household income.</li><li>Gender.</li><li>Education.</li><li>Ethnicity.</li><li>Age Range.</li></ul> |
| Work and professional | <ul><li>Role level.</li><li>Company size.</li><li>Professional industries (select up to 5).</li><li>Job function (select up to 3).</li><li>Job titles (select up to 30).</li><li>Audience skills (select up to 25).</li></ul>                       |

### Screener questions

Screener questions are what participants will answer when applying to participate in your study. **You must include a minimum of two questions drawn from the following question types:**

* Multiple choice (single- or multi-select).
* Typed response (Open-ended).
* Scale.
* Number.

{% hint style="info" %}
**Note:** Checkpoint, Ranking, Photo, Video, and Screen recording questions are not supported when recruiting from Partner Panels. However, you can include them in your actual study.
{% endhint %}

Some of your questions should include knockout logic, which will automatically reject applicants who provide responses that don’t fit your research needs.

{% hint style="info" %}
**Note:** **Must select any** logic is not supported in Partner Panels screeners. If a single question has multiple acceptable responses, a participant must select all of them to qualify. For guidance on how to apply knockout logic in Partner Panels screeners, see [Knockout logic in partner panels screeners](/recruit-participants/partner-panels/knockout-logic-in-partner-panels-screeners).
{% endhint %}

## Review responses

You can view responses to a Partner Panels screener directly in Dscout as you normally would with any other screener. Simply navigate to the **Participants** view of the **Responses** tab of your screener and you’ll find a list of participants. Participants recruited from Partner Panels are indicated with a Partner Panels badge:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/4aAuBJ2bKv5xIy43jzvq/47543391725716)

Select a participant to view their screener responses and profile information provided by our third-party partners.

## Add participants to a study

Once you’ve identified participants you want to invite to your study, you can do so from within your screener or from within the study itself. However, keep the following in mind when inviting Partner Panels participants to studies:

* **Partner Panels participants can only be added to one Dscout study.** Once added to a study, a participant cannot be added to another, even if removed from the first study.
* Whether adding participants to a study before or after launch, **the study incentive must be equal to or higher than the incentive listed on the screener.**

For more information on Partner Panels, see:

* [Partner Panels](/recruit-participants/partner-panels).
* [Auto recruit from Partner Panels](/recruit-participants/partner-panels/auto-recruit-from-partner-panels).
* [How are Partner Panels participants paid?](/recruit-participants/partner-panels/how-are-partner-panels-participants-paid)


# Auto-recruit from Partner Panels

<table><thead><tr><th>Study type</th><th data-type="checkbox">Availability</th></tr></thead><tbody><tr><td><strong>Usability tests</strong></td><td>true</td></tr><tr><td><strong>Media surveys</strong></td><td>true</td></tr><tr><td><strong>AI moderated studies</strong></td><td>true</td></tr></tbody></table>

With auto-recruit, you can let Dscout automatically progress qualifying applicants into your study based on targeting attributes and screener questions added to the start of your study. This speeds up your research by removing the need to manually screen each participant. And if you need both speed and expanded reach, you can choose to auto-recruit from Partner Panels when setting up your study.

{% hint style="warning" %}
You can only choose one recruitment approach for your study, so choosing to recruit from Partner Panels means your study will only be available on our third-party partner platforms.
{% endhint %}

**To auto-recruit from Partner Panels:**

{% stepper %}
{% step %}
On the **Studies** tab of your Dscout project, click **Create study**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FJVDYUy3NRBWC4oD2wJeJ%2FRecruitment_approach%20(1).jpg?alt=media&amp;token=b4681036-375c-48d6-94b9-bd62bd74294b" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select a supported study type (Usability test, media survey, or AI moderated study).
{% endstep %}

{% step %}
Select **Auto-recruit from Partner Panels** as your recruiting approach.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FsNnORQXxwHk9lQf9LGJa%2FRecruitment_approach%20(2).jpg?alt=media&amp;token=d1189091-7006-4555-a8b9-82c2d572f7d7" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Continue**.
{% endstep %}

{% step %}
Configure the remaining settings as prompted to create your study.
{% endstep %}
{% endstepper %}

Now, add your targeting attributes and screener questions on the **Screener** tab of the builder. (Be sure to refer to the next section to understand the slight differences between recruiting from Dscout’s Scout Panel and Partner Panels.) Then, build the rest of your study. And when you’re ready, submit your study for review so we can open it to participants.

{% hint style="info" %}
You cannot skip review when recruiting from Partner Panels. Our typical turnaround time for study review is 1–2 business days.
{% endhint %}

## Requirements and limitations

While recruiting from Partner Panels works very similarly to other Dscout recruiting methods, we impose a few limitations to ensure compatibility with our third-party partners.

### Skip logic

Skip logic (the ability to skip participants to different questions depending on their answers) is not supported in the screener portion of your study.

### Piping logic

Piping logic (the ability to recall participants' responses in subsequent questions) is not supported in the screener portion of your study.

### Targeting attributes

Targeting attributes automatically filter who can apply to your screener or study based on information available in their profile with our third-party partners. When recruiting from Partner Panels, the following targeting attributes are available:

| Category              | Attributes                                                                                                                                                                                                                                          |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Demographics          | <ul><li>Country. (For more information on available countries, see <a href="/recruit-participants/partner-panels">Partner Panels</a>.)</li><li>Household income.</li><li>Gender.</li><li>Education.</li><li>Ethnicity.</li><li>Age Range.</li></ul> |
| Work and professional | <ul><li>Role level.</li><li>Company size.</li><li>Professional industries (select up to 5).</li><li>Job function (select up to 3).</li><li>Job titles (select up to 30).</li><li>Audience skills (select up to 25).</li></ul>                       |

### Screener questions

Screener questions are what participants will answer when applying to participate in your study. **You may only use multiple choice questions as screener questions, and you must include a minimum of two.**

Be sure your questions include knockout logic, which will automatically reject applicants who provide responses that don’t fit your research needs.

{% hint style="info" %}
**Must select any** logic is not supported in Partner Panels screeners. If a single question has multiple acceptable responses, a participant must select all of them to qualify.
{% endhint %}

## Review responses

You can view responses from Partner Panels participants directly in Dscout as you would for any other study. Simply navigate to the **Responses** tab of your study. Responses from Partner Panels participants are indicated with a Partner Panels badge:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/z9SLVXoCNG222EALO5lQ/47543380041876)

Once participants complete your study, you'll have seven days to review their responses before payments are automatically made. In those seven days, a participant’s payment will remain on hold in the event that you flag their response as low-quality.

For more information on Partner Panels, see:

* [Partner Panels](/recruit-participants/partner-panels)
* [Recruit from Partner Panels using a screener](/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener)
* [How are Partner Panels participants paid?](/recruit-participants/partner-panels/how-are-partner-panels-participants-paid)


# Knockout logic in Partner Panels screeners

Recruiting from Partner Panels helps you find participants who meet more specific, often niche criteria. However, there are sometimes limitations imposed by Dscout’s third-party partners. For example, using knockout logic on multi-select questions works a little differently from how you might be used to with a standard Dscout screener.

## Limitation

Standard knockout logic on multi-select questions allows you to apply one of three options to each answer choice on a given question:

* **May select:** A participant may or may not select this answer with no bearing on their qualification.
* **Must select:** If a participant **does not** select this answer, they are disqualified, regardless of their other selections.
* **Knockout:** If a participant selects this answer, they are disqualified, regardless of their other selections.

In a standard Dscout screener, you can include multiple **Must select** answers and only require participants to select *one* of these answers in order to qualify. However, Partner Panels screeners require participants to select all answers marked **Must select** in order to qualify—even if you only need them to select one.

## Solution

If you want to program a multi-select question to have more than one acceptable response in a Partner Panels screener, you can do so using a combination of knockout logic and skip logic.

Let’s say you’re looking for participants who have used either a drip coffee maker *or* French press in the past year and only want to disqualify those who’ve used neither. Here’s what your first question would look like:

**Which of the following ways have you made coffee in the past year? Please select all that apply.**

* Drip coffee maker (May select) (Skip to question 3)
* French press (May select) (Skip to question 3)
* Espresso machine (May select)
* Pour over (May select)
* Other (May select)

You’d then follow this with a question in which all answers are marked as **Knockout** responses. The content of the question doesn’t matter because its only purpose is to disqualify the participants who see it (more on this later). Here’s an example:

**Which of the following best describes where you live?**

* Urban (Knockout)
* Suburban (Knockout)
* Rural (Knockout)

The important thing here is that **only the participants you want to disqualify should see this question**. So, you’d then apply skip logic to your acceptable answers so anyone who selects those skips the disqualifying follow-up. In this case, that would be **Drip coffee maker** and **French press**. By applying skip logic to these answers and not the others, you ensure anyone who only selects **Espresso machine**, **Pour over**, or **Other** is sent to your disqualifying question and knocked out of the screener.

Here’s how this series of questions would look while building your screener:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7tiybuyivNA5zj34Njli/39230390382868)


# How are Partner Panels participants paid?

You’ll issue payments for Partner Panels participants like you would for any other participants. However, once a payment is initiated in Dscout, it is then processed by the third-party partner who sourced the participant. Because of this, be aware of the following payment limitations for Partner Panels participants:

* Only one payment can be issued.
* Payments cannot be lower than the incentive listed on your screener or study.

For more information on Partner Panels, see:

* [Partner Panels](/recruit-participants/partner-panels)
* [Auto-recruit from Partner Panels](/recruit-participants/partner-panels/auto-recruit-from-partner-panels)
* [Recruit from Partner Panels using a screener](/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener)


# Working with participants

Working with participants covers the tools and workflows you use before, during, and after a study. Use this section to understand participant requirements, communicate clearly, manage participant status, and handle common support issues.

In this section:

* [Participant technology requirements by opportunity type](/recruit-participants/working-with-participants/participant-technology-requirements)
* [Best practices for inviting external participants to Dscout](/recruit-participants/working-with-participants/best-practices-for-inviting-external-participants)
* [Communicating with participants](/recruit-participants/working-with-participants/communicating-with-participants)
* [Scout groups](/recruit-participants/working-with-participants/scout-groups)
* [What is the scout rating system in recruit](/recruit-participants/working-with-participants/screener-scout-rating-system)
* [Close or re open a participant](/recruit-participants/working-with-participants/close-or-re-open-a-participant)
* [What if a scouts media isnt uploading](/recruit-participants/working-with-participants/what-if-a-participants-media-isnt-uploading)


# Participant technology requirements

For participants to succeed in Dscout studies (and for you to collect the best data), it's important participants have the right equipment. What they'll need depends on the study type as well as the type of device you're conducting that study on. Use the sections below to understand what your study's specifications will mean for your participants' technology requirements.

## Screeners

| Screener type                                                                        | Mobile app   | Web extension | Web browser                                                                                                                                                                            |
| ------------------------------------------------------------------------------------ | ------------ | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Public screeners** (auto-recruiting from the Dscout Scout Panel or Partner Panels) | ✅ (Required) |               | <p>Scouts in the Dscout panel discover new screener opportunities through the Dscout app.<br><br>Scouts can complete web-based screeners if sent a screener webpage link directly.</p> |
| **Private screeners** (inviting your own participants)                               |              |               | ✅ (Required)                                                                                                                                                                           |

## Diary studies

| Device type                               | Mobile app   | Web extension | Web browser                        |
| ----------------------------------------- | ------------ | ------------- | ---------------------------------- |
| Diary study with **desktop** activities\* |              | ✅ (Required)  | ✅ (Google Chrome or Edge required) |
| Diary study with **mobile** activities\*  | ✅ (Required) |               |                                    |

{% hint style="info" %}
**Note:** Diary studies can include both desktop and mobile activities. If you include both types of activities in your study, participants will need both the Dscout app and the [Dscout browser extension](https://participanthelp.dscout.com/hc/en-us/articles/35668866016916-Installing-the-Dscout-browser-extension).
{% endhint %}

## Interviews

| Device type | Mobile app   | Web extension | Web browser                        |
| ----------- | ------------ | ------------- | ---------------------------------- |
| **Desktop** |              |               | ✅ (Google Chrome or Edge required) |
| **Mobile**  | ✅ (Required) |               |                                    |

## Usability tests

| Device type                | Mobile app   | Web extension  | Web browser                        |
| -------------------------- | ------------ | -------------- | ---------------------------------- |
| **Desktop** usability test |              | ✅ (Required)\* | ✅ (Google Chrome or Edge required) |
| **Mobile** usability test  | ✅ (Required) |                |                                    |

{% hint style="info" %}
**Note:** You can bypass the need for participants to have the Dscout browser extension in desktop usability tests; however, less data will be collected. For more information, see [Manage participant experience in a usability test](/usability-tests/create-a-usability-test/manage-participant-experience-in-a-usability-test).
{% endhint %}

## Media surveys

| Device type              | Mobile app   | Web extension | Web browser  |
| ------------------------ | ------------ | ------------- | ------------ |
| **Desktop** media survey |              |               | ✅ (Required) |
| **Mobile** media survey  | ✅ (Required) |               |              |

For more information on device requirements, see [Minimum device requirements](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196-Minimum-device-requirements).


# Best practices for inviting external participants

When inviting your own participants to Dscout, we have some guidelines and best practices to make their onboarding as smooth as possible. When inviting participants via webpage, participants **will not be required to create a** **Dscout** **account**. They will only need to supply their name, email address, and agree to Dscout's [**Scout Terms and Conditions & Privacy Policy**](https://dscout.com/legal/scout-terms).

## Related articles

### Screeners

* [Screener webpages](/recruit-participants/what-are-dscout-screeners/screener-webpages)
* [Private Screener Onboarding Flow for First-Time Scouts](/recruit-participants/what-are-dscout-screeners/screener-flow-for-bring-your-own-participants)

### Diary studies

* [Inviting first-time scouts to a Diary study](/diary-studies/manage-a-diary-study/inviting-first-time-participants-to-a-diary-study)
* [Diary webpages](/diary-studies/what-are-diary-studies-in-dscout/diary-webpages)
* [Diary Study Onboarding Flow for First-Time Scouts - Scout Profile Required](/diary-studies/manage-a-diary-study/diary-study-onboarding-flow-for-first-time-participants-profile-required)
* [Diary Study Onboarding Flow for First-Time Scouts - Scout Profile Not Required](/diary-studies/manage-a-diary-study/diary-study-onboarding-flow-for-first-time-participants-profile-not-required)

### Interview studies

* [Enable a webpage for an interview study](/interview-studies/create-an-interview-study/enable-a-webpage-for-an-interview-study)
* [First-time participant flow in a mobile interview study](/interview-studies/manage-an-interview-study/first-time-participant-flow-in-a-mobile-interview-study)
* [First-time participant flow in a desktop interview study](/interview-studies/manage-an-interview-study/first-time-participant-flow-in-a-desktop-interview-study)

### Usability tests and media surveys

* [Bring your own (BYO) participants FAQ](/recruit-participants/bring-your-own-byo-participants-faq)
* [Participant flow in a usability test](/usability-tests/manage-a-usability-test/participant-flow-in-a-usability-test)
* [Participant flow in a media survey](/media-surveys/manage-a-media-survey/participant-flow-in-a-media-survey)

## Related Articles for Participants

* [Participating in Diary studies](https://participanthelp.dscout.com/hc/en-us/search/click?data=BAh7DjoHaWRsKwiU5qnBcCA6D2FjY291bnRfaWRpA2LNkDoJdHlwZUkiDGFydGljbGUGOgZFVDoIdXJsSSJoaHR0cHM6Ly9wYXJ0aWNpcGFudGhlbHAuZHNjb3V0LmNvbS9oYy9lbi11cy9hcnRpY2xlcy8zNTY2ODY1NzU2MzI4NC1QYXJ0aWNpcGF0aW5nLWluLURpYXJ5LW1pc3Npb25zBjsIVDoOc2VhcmNoX2lkSSIpZTcwNDYyYTQtNDlmMy00ZjFiLTk1ZDQtYTIyOThmMzk0ZWE1BjsIRjoJcmFua2kGOgtsb2NhbGVJIgplbi11cwY7CFQ6CnF1ZXJ5SSIicGFydGljaXBhdGUgaW4gZGlhcnkgbWlzc2lvbnMGOwhUOhJyZXN1bHRzX2NvdW50aSI%3D--003a2065cd7d57f82248d088c0e8e0db7a439546)
* [Participating in interview studies](https://participanthelp.dscout.com/hc/en-us/articles/35669420294676-Participating-in-Live-missions)
* [Participating in single-session studies](https://participanthelp.dscout.com/hc/en-us/articles/35669655437460-Participating-in-Express-missions)
* [Receiving your reward](https://participanthelp.dscout.com/hc/en-us/articles/35730442464660-Receiving-your-reward)
* [How to create a PayPal account](https://participanthelp.dscout.com/hc/en-us/articles/35730776426900-How-to-create-a-PayPal-account)
* [How to add your PayPal email address to your Dscout account](https://participanthelp.dscout.com/hc/en-us/articles/35730750753044-How-to-add-your-PayPal-email-address-to-your-Dscout-account)
* [Add an alias to your PayPal](https://participanthelp.dscout.com/hc/en-us/articles/35730859996564-Adding-an-alias-to-your-PayPal)

## Best practices

* **Gauge interest + over-recruit -** If you’ve already recruited or gauged interest from a listserv, we typically see somewhere around \~30-40% drop-off, so make sure to over-recruit to account for this! We always recommend gauging interest or recruiting first, because when it comes to sending a study invitation straight to a listserv, we see drop-off closer to 90-95%!

  ***Note:** if you can ask about willingness to share selfie photos/videos + willingness to download the Dscout app at the screener stage, that can help improve participation!*
* **Send an email from a familiar address with details on what to expect -** sending it from a familiar address, whether that’s the recruiter or the client, will improve participation. See a sample email template for what details to include below.
* **Customize your study invite message -** this will be the first information participants see from Dscout, so make sure your invite message includes key details about your project like the overall objective of the study, deadlines, length of study, and incentive!
* **Tell participants to allow or add <participate@dscout.com> to their email contacts -** making sure participant email clients don’t block or send critical Dscout emails to spam will help everyone stay on top of comms.

## Email copy

### Screeners

*Hello,*

*I hope this message finds you well. We are reaching out to invite you to participate in a research study to gain deeper insights into **\[INSERT RESEARCH STUDY TOPIC]**.*

*In order to capture this information, we are partnering with a platform called Dscout. To start, we’d love to invite you to apply to the study to see if you are a good fit.*

*Click here **\[INSERT LINK]** to access the application and create your Dscout account. Add your name and email address, and agree to the Dscout terms and conditions.*

*You will then be able to fill out your responses to the application.*

*If you are a good fit for the study, you can expect an invitation with additional information to follow.*

*Have questions or need technical support? Take a look at this* [*Knowledge Base article about Applying on Dscout*](https://participanthelp.dscout.com/hc/en-us/articles/35668107016340-Applying-to-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*

### Diary studies

#### Mobile diary study

*Hello,*

*Thank you so much for agreeing to participate in this project!*

*Over the next **\[INSERT TIMEFRAME]**, we are going to ask you to complete **\[XX NUMBER OF]** research activities so that we can learn **\[INSERT PROJECT OBJECTIVES]**. In order to capture this information, we are using a smartphone app called Dscout that will allow you to easily provide us with a glimpse into your life. In each research activity (what we’ll refer to as a "study activity"), you will be asked to answer a set of questions and submit a photo and/or video of yourself.*

*Click here **\[INSERT LINK]** to access the study and create your Dscout account.*

*Then, download the Dscout app onto your smartphone from* [***Google Play***](https://play.google.com/store/apps/details?id=com.vokal.dscout\&hl=en) *or the* [***App Store***](https://itunes.apple.com/us/app/dscout/id395563123?mt=8)*. Use the account information you just created to sign in.*

*Once you log in to the Dscout app on your smartphone, look out for the **\[INSERT STUDY NAME]** study on the 'Studies' tab, under the ‘Invites’ section, which contains additional details about the project.*

*Accept the study, read the instructions, and select 'new entry' so you can open the set of questions you will need to answer.*

***Payment information:** Dscout process payments through PayPal (more info* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35730442464660-Receiving-your-reward)*). In order to receive your reward please make sure you create a PayPal account or use your PayPal email to sign up for Dscout. You can also add an alias to your PayPal account if you would prefer to sign up for Dscout with a different email.*

*\*Please note: You must have an iPhone with iOS14+ or an Android phone with Oreo/8.0+ to download the Dscout app. Learn more about device compatibility* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196-Minimum-device-requirements)*.*

*Have questions or need technical support? Take a look at the* [*Dscout Help Center*](https://participanthelp.dscout.com/hc/en-us/categories/34520632367124-Diary-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*

#### Desktop diary study

*Hello,*

*Thank you so much for agreeing to participate in this project!*

*Over the next **\[INSERT TIMEFRAME]**, we are going to ask you to complete **\[XX NUMBER OF]** research activities so that we can learn **\[INSERT PROJECT OBJECTIVES]**. In order to capture this information, we are using a platform called Dscout that will allow you to easily provide us with a glimpse into your life. In each research activity (what we’ll refer to as a "study activity"), you will be asked to answer a set of questions and submit a photo and/or video of yourself.*

*Click here **\[INSERT LINK]** to access the study and create your Dscout account.*

*Then, download the* [*Dscout browser extension*](https://participanthelp.dscout.com/hc/en-us/articles/35668866016916-Installing-the-Dscout-browser-extension) *and install it in your Chrome or Edge browser. Use the account information you just created to sign in.*

*Once you have the Dscout browser extension installed, click the extension to open the window. Tap “Studies” and look out for **\[INSERT STUDY NAME]**.*

*Accept the study, read the instructions, and follow the prompts to complete your very first desktop entry.*

***Payment information:** Dscout process payments through PayPal (more info* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35730442464660-Receiving-your-reward)*). In order to receive your reward please make sure you create a PayPal account or use your PayPal email to sign up for Dscout. You can also add an alias to your PayPal account if you would prefer to sign up for Dscout with a different email.*

*Have questions or need technical support? Take a look at the* [*Dscout Help Center*](https://participanthelp.dscout.com/hc/en-us/categories/34520632367124-Diary-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*

### Interview studies

#### Mobile interview study

*Hello,*

*Thank you so much for agreeing to participate in this project!*

*Over the next **\[INSERT TIMEFRAME]** we are going to ask you to complete an interview with us so that we can learn **\[INSERT PROJECT OBJECTIVES]**. In order to capture this information, we are using a smartphone app called Dscout that will allow you to easily provide us with a glimpse into your life.*

*Click here **\[INSERT LINK]** to access the study, create your Dscout account, and choose a time slot that works for your schedule.*

*Then, download the Dscout app onto your smartphone from* [***Google Play***](https://play.google.com/store/apps/details?id=com.vokal.dscout\&hl=en) *or the* [***App Store***](https://itunes.apple.com/us/app/dscout/id395563123?mt=8)*. Use the account information you just created to sign in.*

*Once you log in to the Dscout app on your smartphone, look out for the **\[INSERT STUDY NAME]** study on the 'Studies' tab, under the ‘Invites’ section, which contains additional details about the project.*

*Check out these* [***guidelines and walkthrough***](https://participanthelp.dscout.com/hc/en-us/articles/35669283142036-Live-Mobile-Participation-Guidelines-Walkthrough) *at least 24 hours before your session. Then talk to a researcher one-on-one and get paid for your opinion.*

***Payment information:** Dscout process payments through PayPal (more info* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35730442464660-Receiving-your-reward)*). In order to receive your reward please make sure you create a PayPal account or use your PayPal email to sign up for Dscout. You can also add an alias to your PayPal account if you would prefer to sign up for Dscout with a different email.*

*\*Please note: You must have an iPhone with iOS14+ or an Android phone with Oreo/8.0+ to download the Dscout app. Learn more about device compatibility* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196-Minimum-device-requirements)*.*

*Have questions or need technical support? Take a look at the* [***Dscout Help Center***](https://participanthelp.dscout.com/hc/en-us/categories/34520634103444-Live-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*

#### Desktop interview study

*Hello,*

*Thank you so much for agreeing to participate in this project!*

*Over the next **\[INSERT TIMEFRAME]** we are going to ask you to complete an interview with us so that we can learn **\[INSERT PROJECT OBJECTIVES]**. In order to capture this information, we are using a platform called Dscout that will allow us to chat.*

*Click here **\[INSERT LINK]** to access the study, create your Dscout account, and choose a time slot that works for your schedule.*

*Add **\*<participate@dscout.com>\*** to your email address book or allowlist so you can receive messages and reminders from your researcher.*

*Make sure you have Google Chrome or Microsoft Edge installed on a computer with a microphone and a webcam. Download* [***here***](https://www.google.com/chrome/)*.*

*Accept the study and complete your interview pre-test by clicking on the session link in your invitation email. Follow the prompts there to test your connectivity, camera, microphone, and speakers to make sure your set-up is good to go for your call.*

*Once you complete your tech check, schedule your session. If you don’t see this option, your study leader will be in touch.*

*Complete* [***this checklist***](https://participanthelp.dscout.com/hc/en-us/articles/35669348346388-Your-Live-Desktop-To-Do-List) *at least 24 hours before your session. Then talk to a researcher one-on-one and get paid for your opinion.*

***Payment information:** Dscout process payments through PayPal (more info* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35730442464660-Receiving-your-reward)*). In order to receive your reward please make sure you create a PayPal account or use your PayPal email to sign up for Dscout. You can also add an alias to your PayPal account if you would prefer to sign up for Dscout with a different email.*

*Have questions or need technical support? Take a look at the* [***Dscout Help Center***](https://participanthelp.dscout.com/hc/en-us/categories/34520634103444-Live-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*

#### Mobile usability test or media survey

*Hello,*

*Thank you so much for agreeing to participate in this project!*

*Over the next **\[INSERT TIMEFRAME]**, we are going to invite you to participate in a research study so that we can learn **\[INSERT PROJECT OBJECTIVES]**. In order to capture this information, we are using a smartphone app called Dscout. In this study, you will be asked to answer a set of questions and may be asked to submit a photo and/or video.*

*Click here **\[INSERT LINK]** to sign up and access the study.*

*Then, download the Dscout app onto your smartphone from* [***Google Play***](https://play.google.com/store/apps/details?id=com.vokal.dscout\&hl=en) *or the* [***App Store***](https://itunes.apple.com/us/app/dscout/id395563123?mt=8)*. Use the account information you just created to sign in.*

*Once you log in to the Dscout app on your smartphone, look out for the **\[INSERT STUDY NAME]** study on the 'Studies' tab, under the ‘Invites’ section, which contains additional details about the project.*

*Accept the study, read the instructions, and get started.*

*\*Please note: You must have an iPhone with iOS14+ or an Android phone with Oreo/8.0+ to download the Dscout app. Learn more about device compatibility* [*here*](https://participanthelp.dscout.com/hc/en-us/articles/35668393762196-Minimum-device-requirements)*.*

*Have questions or need technical support? Take a look at the* [***Dscout Help Center***](https://participanthelp.dscout.com/hc/en-us/categories/34520645550484-Express-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*

#### Desktop usability test or media survey

*Hello,*

*Thank you so much for agreeing to participate in this project!*

*Over the next **\[INSERT TIMEFRAME]**, we are going to ask you to complete **\[XX NUMBER OF]** research activities so that we can learn **\[INSERT PROJECT OBJECTIVES]**. In order to capture this information, we are using a platform called Dscout. In this study, you will be asked to answer a set of questions and may be asked to submit a photo and/or video.*

*Click here **\[INSERT LINK]** to access the study and create your Dscout account.*

*Then, download the* [*Dscout browser extension*](https://participanthelp.dscout.com/hc/en-us/articles/35668866016916-Installing-the-Dscout-browser-extension) *and install it in your Chrome or Edge browser. Use the account information you just created to sign in.*

*Once you have the browser extension installed, click the extension to open the window. Tap “Studies” and look out for **\[INSERT STUDY NAME]**.*

*Accept the study, read the instructions, and get started.*

*Have questions or need technical support? Take a look at the* [***Dscout Help Center***](https://participanthelp.dscout.com/hc/en-us/categories/34520645550484-Express-missions)*. If you get stuck, reach out to the scout support team at* [***help@dscout.com***](mailto:help@dscout.com) *with a clear description of the problem. If you have any questions about the project itself, feel free to reach out to me at **\[INSERT EMAIL]**.*


# Communicating with participants

There are two ways to communicate with your participants via Dscout: messages and comments.

## Messages vs. comments

**Messages** are best for logistical communication with scouts, like sending due dates, reminders, and general information. You may also *receive* messages from scouts with questions about the study. You'll know you have a new scout message when you see a blue bubble on the Manage page:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/vNKewW0pfypIri0J6EpV/6093180200980)

You can send messages in **bulk** by selecting multiple scouts at once. Filter by scout group or progress on the lefthand side of the Manage page to expedite this process.

**Comments** are tied to specific entries, and are best for research-related communications and questions for scouts – especially follow-ups. See how to comment on an entry [below](#how-to-comment-on-an-entry).

{% hint style="info" %}
Both comments and messages are **exportable**, so you'll be able to save and analyze them outside of the platform.
{% endhint %}

## How to send a message

To send a message, start on the Manage page of your study. To message more than one scout at a time, select the checkmark next to the scouts' names and click "Message" from the blue menu bar that appears. A message box will open on the righthand side of the page.

{% hint style="info" %}
***Note:** this will send an individual message to each scout you've selected, as opposed to creating a group message.*
{% endhint %}

To message just one scout, take a shortcut by clicking on the scout's grey circle in the Unread Messages column.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/N6XfWtLtgm1knnqHAFxp/6093337561748)

## Sample messages

### Introduction messages

When scouts are first invited to your study, they will receive the invite message that you included in your study design. Once they accept the study, it's always a good idea to send a quick message introducing yourself and giving some context for the study.

Examples:

*Hi there! My name is Elyse, and I'll be your study leader! As a reminder, your first entry is due TONIGHT in order to secure your spot in the study :) In this study activity, we want to see a variety of entries showing us your life as a student at Hogwarts School of Witchcraft and Wizardry. Let me know if you have any questions – I'm here to help! You can also reach out to* [*help@dscout.com*](mailto:help@dscout.com) *to address any technical problems.*

*Hello, scouts! Thanks for accepting this study – we are so excited to get started. Over the next two weeks, you'll be testing out some new products in our line. To ensure that your products arrive in time, we need you to complete Activity 1 ASAP! Let me know if you have any questions, and feel free to email* [*help@dscout.com*](mailto:help@dscout.com) *if you encounter any technical problems.*

### Reminders

To encourage active participation throughout the study, it's important to send scouts reminder messages. Keep these messages friendly and supportive!

Example:

*Good morning, scouts! Remember, BOTH entries for Activity 2 are due TOMORROW at midnight! We're so excited to hear about your underwater basket weaving experiences. Please feel free to reach out with any questions, and email* [*help@dscout.com*](mailto:help@dscout.com) *if you encounter any technical difficulties! Thanks :)*

### Invited scout messages

If a scout's status is still "Invited" after a day or two, you may want to send a quick message to encourage them to accept.

Example:

*Hi there, Katie! We loved your application to this study and sent you an invite, but we haven't heard from you yet. If you're still interested in participating in this project to earn $60, please hit "Accept" no later than TONIGHT at 11:59pm! If you're no longer interested in this study, please decline the study so that we know to offer your spot to someone who would like to participate!*

### Coaching/redirection messages

Sometimes, a scout might misunderstand a question prompt or submit an entry that doesn't quite hit the mark. Send a positive but firm message to get the scout back on track.

Examples:

*Hi, Austin! Thanks for getting started on this study. I noticed that in your video for Activity 1, you showed us where you were, but didn't narrate what makes it a "hidden gem" in your neighborhood. In future entries, we need you to talk us through the whole experience. Be sure to read the question prompt carefully! Thanks, and let me know if you have any questions about this.*

*Thanks for submitting 5 entries for this study, Emma! While it's great to hear about how you care for your dog in general, this study is primarily about pet food, and we weren't able to see your shopping journey. Can you submit 2+ more entries in Activity 2? We'll give you until TOMORROW MORNING at 9:00am EST to get these extra entries in. Let me know if you have any questions. Thank you!*

### New activity reminders

When a new study activity opens, it's a good idea to send scouts a quick update.

Example:

*Happy Friday, scouts! Activity 4 of this study is now open. In this activity, we want to hear your funniest knock-knock jokes! You'll need to submit 3 entries by 10/18 at 11:59pm CT.*

### Upload error messages

Sometimes, a scout's photo or video will not upload properly due to wifi connectivity issues. Dscout has settings and help articles in place for scouts when this happens, but occasionally those emails are lost in the shuffle and you'll need to ping the scout.

Example:

*Thanks for submitting an entry to Activity 2! Unfortunately, it looks like your video failed to upload. Please follow these instructions to retry the upload:* [*What if a scouts media isnt uploading*](/recruit-participants/working-with-participants/what-if-a-participants-media-isnt-uploading)*?*

{% hint style="info" %}
**Note:** if the error persists, talk to your Research Advisor. The scout can email the media file to <help@dscout.com> with the subject line "Attn: \[research advisor's name]," and we will be able to upload the file manually.
{% endhint %}

### Payment questions

Scouts may reach out with questions about payments. Again, there is in-platform messaging for the scouts, but sometimes that can be missed. If Dscout is handling payment processing for your project, you can always direct them to email <payments@dscout.com> with questions.

Example:

*Thanks for reaching out! Sometimes we need a few days to review entries before processing payments to make sure we have everything we need. Once we've had a chance to review your entries and process reward payments, you'll get an email from PayPal within two weeks (10 business days) indicating that your payment is ready. Make sure to claim this payment within 30 days! For more on payment timelines and statuses, see* [*Request payments in a diary study*](/diary-studies/manage-a-diary-study/request-payments-in-a-diary-study)*.*

### Missing scout messages

If a scout is unresponsive, you'll want to close them out of the study and send a quick message letting them know.

Example:

*Hi, Charles! We know that sometimes life gets in the way, but we haven't received the required entries you need to complete this study. We've closed this study for you, but we hope to see you in another Dscout study soon!*

### "Last chance" reminders

Before your study closes, send a group message to all the scouts who haven't finished yet giving them a heads up that time is running out! Be firm but cordial. Scouts are busy folks, but they want to do good work!

Example:

*Good morning, scouts! This is just a reminder that all 3 entries for Activity 7 are due today to earn your $150 reward! To make sure you have a chance to get your entries in, we're extending the deadline to 11:59PM Central tonight. We're excited to hear about your experience as a circus performer! Please let me know if you have any questions.*

## How to comment on an entry

To comment on a scout's entry, click into the entry from the Entry Grid page. Then, scroll all the way to the bottom on the entry.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/36nzhogztyM7Lpngzbxe/6093863460884)

## Sample comment

With multi-question prompts (i.e. "barreling"), it can be easy to miss a question or two. You can always follow up with a scout to answer any questions they may have missed.

Example

*Hi Zoe! Thanks for submitting your entry to Activity 2. In the last question, we asked you to describe \*two things that bring you joy\* but only heard about one. Before we move onto Activity 3, please leave a comment here on your entry to describe one more thing that brings you joy. Thank you!*


# Scout groups

Scout groups are a great way to organize and assign scouts based on segments, waves, or other categorizations. You can add any scout to any scout group for deeper analysis and easier scout management across the platform.

Scouts can be added to multiple groups within the same study or screener. For example, a scout can be in the "Free music apps" group, as well as the "Cohort A" group. Scout groups are automatically carried over with a scout when the scout is invited to studies within in the same project environment. Scout groups are always available in scout exports and crosstabs.

### Scout groups in screeners, usability tests, media surveys, and intercept studies <a href="#h_01fgmn7ck2h7t5c1pcr5kq03cw" id="h_01fgmn7ck2h7t5c1pcr5kq03cw"></a>

**Grouping**

One way to create and manage scout groups in screeners is through an individual application, or what we call a screener "entry." In the entry, find "Participant groups" in the right sidebar and click "Add." To add a new group, click "Create new Group." Follow this same process in usability tests, media surveys, and intercept studies to group study entries.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FxfebetndLz1ph5brZy5g%2Fimage.png?alt=media&amp;token=8da78c8a-c20a-4563-a882-4deead85b785" alt=""><figcaption></figcaption></figure>

To group multiple scouts at once, begin on the **Responses** tab and make sure you're in the Participants view (instead of Questions view) -- all eligible applicants will appear on the left side of the screen. Select the applicants you'd like to group. Then, at the bottom of the page, you'll see a blue banner pop up. First click "Add to Group," then select any existing group or "Create new group."

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FDOxP8DnfVnXodMpozkHq%2Fimage.png?alt=media&amp;token=8771a5f8-b3e9-4aae-bb34-be56b571dc91" alt=""><figcaption></figcaption></figure>

**Filtering by groups**

Filter entries by the groups you've created by clicking the filter icon in the top right corner. Then, click Participant groups." Keep in mind, filtering uses "or" logic, meaning that if you filter to multiple groups, all scouts in *either* group will be visible (not solely the scouts who reside in both groups).

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FFwHxMvccAqAmcflJ8A96%2Fimage.png?alt=media&amp;token=60d8058a-db72-460f-943a-37dc88139820" alt=""><figcaption></figcaption></figure>

### Scout groups in diary studies <a href="#creating-scout-groups" id="creating-scout-groups"></a>

**Grouping via the Manage page**

One way to create a new scout group in your diary studies is from the Manage page. Begin by selecting "New Group" from the left-hand sidebar, under "Filter by Scout Groups." Tap enter on your keyboard or click "Create" once you've typed out a name for your new group.

<figure><img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/MkmPK8mpq9RmL0oXkNnw/4415890005268" alt=""><figcaption></figcaption></figure>

Then, select the scout(s) you'd like to group and click "Add to Group" from the toolbar that appears above the scout rows. Check the box to the left of the group to which you'd like to add your selected scouts.

You can also add or edit your groups from this dropdown menu.

{% hint style="info" %}
**Note:** When creating a new group via the dropdown menu, your selected scouts will not be automatically added to the new group. You must still select the box to the left of the group to add your scouts.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/2EIKcrCNGpLHTqR7OeQV/4415890035476" alt=""><figcaption></figcaption></figure>

**Grouping via diary entries**

Just like a screener, usability test, or media survey entry, you can create and manage scout groups from a single diary entry. To create a new scout group from an entry, click "Add to Group" on the right-hand sidebar. Then click "New Group."

To add the scout to an existing group, click "Add to Group" and select the group to which you wish to add them.

<figure><img src="https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/sP2dneE77GDahOKffnhc/4407786396820" alt=""><figcaption></figcaption></figure>

**Filtering by groups in diary studies**

To message only the scouts in a single group, start on the Manage page. Then, filter by that group by clicking the group name under the left-hand sidebar, "Filter by Scout Groups." Select all, and then click on the message icon from the toolbar.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FOiCMx3f666B2HAqSakAu%2Fimage.png?alt=media&amp;token=a6ace30c-053f-4ba2-b11e-faa9de3415cf" alt=""><figcaption></figcaption></figure>

To view only the entries of scouts in a single group, start on the Entries Grid page. Select "Scouts" from the "Filter by Attributes" box on the left-hand sidebar. Then click "Scout Groups," and select your preferred group.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FGZSqVsRmXj4BLDXfwWdF%2Fimage.png?alt=media&amp;token=9a05c92c-78a5-4ff8-a149-7529041b62ad" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** On both the Entries Grid and the Manage page, filtering uses "or" logic; meaning, if you filter by multiple groups, all scouts in *either* group will be visible.
{% endhint %}

### Scout groups in interview studies <a href="#h_01fsd6mfk2d3dqw9d93jhevdzn" id="h_01fsd6mfk2d3dqw9d93jhevdzn"></a>

**Grouping via the Manage page**

Begin by selecting the scout you'd like to group via the Manage page (select a scout by clicking their name or profile picture). Once the scout is selected, click "Add to Group" from the toolbar above the scout rows. Click "New Group" to create your group and add your scout, or click the name of the group to which you'd like to add your selected scout.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FKQX12NMkDvyEcAEqhlRk%2Fimage.png?alt=media&amp;token=ef64ed46-41ad-4463-9407-0fe0a8a7dcc3" alt=""><figcaption></figcaption></figure>

Currently, scouts can be grouped one at a time.

**Filtering by groups in interview studies**

Scouts can be filtered by group via the Manage page and the Sessions page. From the Manage page, begin by clicking "Filter," then “Add Filter.” From the dropdown menu labeled “Category,” select “Scout Groups.” Then, from the dropdown menu labeled “Specifier,” select the group by which you’d like to filter. Finally, tap “Apply Filter.” Now, only scouts in that group will be visible.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FpbXQlDC5a9iwzJWIAb8x%2Fimage.png?alt=media&amp;token=dca3a1c1-c45f-438d-a892-9585feafd813" alt=""><figcaption></figcaption></figure>

To message the scouts in a single group, follow the instructions above to filter to that group via the Manage page. Then, click “Select All” from the toolbar above the scouts' names. Once all are selected, click the message icon to open the messaging panel and type out your message to the scouts!

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FHVVAbca19AxTVHbjvNwk%2Fimage.png?alt=media&amp;token=9f04a8d8-a516-46cc-88cd-b760e161eb45" alt="" width="375"><figcaption></figcaption></figure>

You can also filter by scout groups via the Sessions page if you'd like to view sessions or clips with *only* the scouts in a specific group.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FHQwDeQYk9dpvLyeJ4Wue%2Fimage.png?alt=media&amp;token=f1fa7817-f43a-4f2f-beb7-8a7a18dafc2a" alt=""><figcaption></figcaption></figure>

### Carrying over scout groups within a project <a href="#h_01fssb8x8f8290d80jj6fgzyrv" id="h_01fssb8x8f8290d80jj6fgzyrv"></a>

As scouts are added to different studies within the same projec&#x74;*,* they will carry their associated scout group(s) with them. Meaning, scouts will automatically bring their assigned scout group to new studies they participate in. This applies for screeners and all study types within the same project.

{% hint style="info" %}
**Note:** Scout groups do *not* sync backwards. **Scout groups are only carried through when invited to a study from a screener or previous study.** For example, when inviting a scout from a diary study to an interview study, any new groups or edits to existing groups in the interview study will not sync backwards to the diary study. Any group changes in the diary study will not sync to the interview study after a scout has been added.
{% endhint %}

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FfyGrD7VYReu3K59oMAvg%2Fimage.png?alt=media&amp;token=63d60aa8-050a-4da2-9375-fea453c322f5" alt=""><figcaption></figcaption></figure>


# Screener Scout rating system

The rating system in Recruit allows you to group scouts in the ways that matter to you. Here’s the lingo we use:

* **Eligible**: Scouts come in unlabeled by default
* **Good Fit**: Good for the study and a good quality application
* **Possible Fit**: A backup option for your study
* **Bad Fit**: Quality application, but not a good fit for your study
* **Low Quality**: Poor quality application -- didn’t follow instructions, or video didn’t come through, for example


# Close or re-open a participant

In some cases, you may wish to prevent participants from submitting further entries in a Diary study or from scheduling additional live interviews. Maybe a participant has missed a deadline, or maybe they’ve finished a study early and you don’t want them to feel obligated to do anything else while waiting for payment. To do that, you’ll manually “close” participants within your study.

### Close or re-open participants in Diary studies <a href="#h_01k0sag50d2cnx025hzkwk02z3" id="h_01k0sag50d2cnx025hzkwk02z3"></a>

To prevent participants from submitting further entries in a Diary study, you’ll “close” them on the **Manage** tab of your study.

**To close participants in Diary studies:**

{% stepper %}
{% step %}
Navigate to the **Manage** tab of your study.
{% endstep %}

{% step %}
Find the participant you want to close.
{% endstep %}

{% step %}
Select the checkbox beside the participant’s name.
{% endstep %}

{% step %}
Click **Close** at the top of the participant list. A confirmation modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FCnCxtIPT4KcwYNgxl4Qp%2Fimage.png?alt=media&amp;token=9c3ea50d-a457-4125-a5c0-92a598a45cb5" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Close Scout** to confirm.
{% endstep %}
{% endstepper %}

Now, the participant will no longer be able to submit further entries in this Diary study.

{% hint style="success" %}
**Tip:** We recommend sending any participants you “close” a message letting them know. To find example messages to spark inspiration, see [Communicating with participants](/recruit-participants/working-with-participants/communicating-with-participants).
{% endhint %}

If you change your mind and wish to re-open a closed participant, you can do so from the **Manage** tab of your study.

**To re-open participants in Diary studies:**

{% stepper %}
{% step %}
Navigate to the **Manage** tab of your study.
{% endstep %}

{% step %}
Find the participant you want to re-open.
{% endstep %}

{% step %}
Select the checkbox beside the participant’s name.
{% endstep %}

{% step %}
Click **Message** at the top of the participant list. The messaging sidebar is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FUeir2mpUGLh9LTnciJVc%2Fimage.png?alt=media&amp;token=66e4e9d9-4f38-40a9-9638-5e1447e2e047" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Reopen scout** in the messaging sidebar. A confirmation modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FyVzTjSowh7MkfIS0zh85%2Fimage.png?alt=media&amp;token=05588049-33f2-4067-9c30-5f2832c527d9" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Reopen** to confirm.
{% endstep %}
{% endstepper %}

Now, the participant is once again able to submit entries as part of this Diary study.

### Close or re-open participants in interview studies <a href="#h_01k0sag50kspadcjwdd2145x81" id="h_01k0sag50kspadcjwdd2145x81"></a>

To prevent participants from scheduling further interview sessions, you can “close” them on the **Manage** tab of your study.

{% hint style="info" %}
**Note:** Only participants who have *not* completed an interview session can be closed. Participants who have already completed their session won't be able to schedule additional sessions on their own, so there's no need to close them manually.
{% endhint %}

**To close a participant in an interview study:**

{% stepper %}
{% step %}
Navigate to the **Manage** tab of your study.
{% endstep %}

{% step %}
Find the participant you want to close.
{% endstep %}

{% step %}
Click the **three-dot icon** beside the participant’s scheduled time.
{% endstep %}

{% step %}
Select **Close scout**. A confirmation modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2F4PphSpXyiHbKm26yTH34%2Fimage.png?alt=media&amp;token=57b2de33-4bc8-455e-81fd-274af041bf19" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Close scout** to confirm.
{% endstep %}
{% endstepper %}

Now, the participant will no longer be able to schedule interviews or take part in this study.

{% hint style="success" %}
**Tip:** We recommend sending any participants you “close” a message letting them know. To find example messages to spark inspiration, see [Communicating with participants](/recruit-participants/working-with-participants/communicating-with-participants).
{% endhint %}

If you change your mind and wish to re-open a closed participant, you can do so from the **Manage** tab of your study.

**To re-open a participant in an interview study:**

{% stepper %}
{% step %}
Navigate to the **Manage** tab of your study.
{% endstep %}

{% step %}
Find the participant you want to re-open.
{% endstep %}

{% step %}
Select the checkbox beside the participant’s name.
{% endstep %}

{% step %}
Click **Message** at the top of the participant list. The messaging sidebar is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FoARgAeTfO6mWng48HJ8z%2Fimage.png?alt=media&amp;token=86e0e6f5-a2a8-474b-965d-f26afe3c19d7" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Reopen scout** in the messaging sidebar. A confirmation modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FZjYDEa5c2ahXFLbefSbp%2Fimage.png?alt=media&amp;token=90a1174c-be7f-4adb-a5e5-6710702a1ffc" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Reopen** to confirm.
{% endstep %}
{% endstepper %}

Now, the participant is once again able to schedule interview sessions and take part in this study.


# What if a participant's media isn't uploading?

***

If any of your scouts are having trouble uploading entries, have them take a look at [this comprehensive troubleshooting guide](https://participanthelp.dscout.com/hc/en-us/articles/35730994556564-Upload-issues-troubleshooting-steps-for-Dscout-mobile-app). (See an example message you can send participants below.)

90% of the time, if a photo or video doesn't upload correctly, it's due to connectivity issues; all your scout will need to do is connect to a strong WiFi signal and tap on the entry with an error to retry re-uploading the entry.

### Example message you can send to scouts having trouble <a href="#example-message-you-can-send-to-scouts-having-trouble" id="example-message-you-can-send-to-scouts-having-trouble"></a>

"Hi there!

Looks like at least one of your entries didn't upload successfully. Would you mind connecting to a strong WiFi signal and trying again? It's also a good idea to make sure the Dscout app and your phone's operating system are both up to date.

If you're still having issues, go ahead and force quit the Dscout app and restart it, then sign out and back into your account. (If you've forgotten your password, just click the "forgot password" link to reset it.)

If all else fails, delete the Dscout app and reinstall it. All your profile data, study history, and any submitted entries will all be saved! Only entries that haven't been submitted successfully won't be saved.

Please take a look at this extensive troubleshooting guide if you need additional details:

[Upload issues and troubleshooting for Dscout mobile app](https://participanthelp.dscout.com/hc/en-us/articles/35730994556564-Upload-issues-troubleshooting-steps-for-Dscout-mobile-app)

If you're experiencing a problem that isn't listed in this article, please send an email to scout technical support at <help@dscout.com>. Thanks for your perseverance!"


# Paying participants

Paying participants works a little differently depending on your study type. For more information, see the articles below:

* [Pay participants in a usability test or media survey](/recruit-participants/working-with-participants/paying-participants/pay-participants-in-a-usability-test-or-media-survey).
* [Request payments in a diary study](/diary-studies/manage-a-diary-study/request-payments-in-a-diary-study).
* [Request payments in an interview study](/interview-studies/manage-an-interview-study/request-payments-in-an-interview-study).


# Pay participants in a usability test or media survey

Depending on your recruitment approach and study setup, payments can be issued for usability tests and media surveys in one of two ways: Participants will either be paid by Dscout automatically via PayPal, or you can manage incentives on your own outside of the platform (for bring-your-own participants only).

### Paid via Dscout <a href="#h_01hqkscmj0d0e5s34k67v0ymdp" id="h_01hqkscmj0d0e5s34k67v0ymdp"></a>

For the majority of usability tests and media surveys, participants are paid automatically. This includes studies with the following recruitment approaches:

* Recruit from the Dscout Scout Panel.
* Recruit from Partner Panels.
* Invite via share link (when **Paid via Dscout** is enabled).

For studies using these recruitment methods, participants with completed submissions are put on a seven-day payment hold in which you can review their entries for quality. If you spot any issues, you can report an entry to prevent the participant from being paid. Otherwise, payments are automatically released to participants via PayPal after their seven-day payment hold. For more information reporting or flagging entries, see [Exclude responses from a usability test](/usability-tests/analyze-a-usability-test/exclude-responses-from-a-usability-test) or [Exclude responses from a media survey](/media-surveys/analyze-a-media-survey/exclude-responses-from-a-media-survey).

{% hint style="info" %}
**Note:** You must have a verified form of payment on file with Dscout as you will be charged for these incentives, incentive fees, and the associated activity credits. Speak with your Dscout Account Manager to learn more about how your account manages incentives and activity credits.
{% endhint %}

### Paid manually <a href="#h_01hqkscmj02re90qv3sd2jsv8v" id="h_01hqkscmj02re90qv3sd2jsv8v"></a>

In some cases, you will be responsible for managing payments on your own outside of the Dscout platform. This includes studies with the following recruitment approaches:

* Invite via share link (when **Paid via Dscout** is disabled).
* Invite from Private Panels.

For studies using these recruitment methods, participants will *not* be paid automatically upon completion of your study. Instead, you must facilitate payments to ensure participants receive the incentives they are owed.


# Bring your own (BYO) participants FAQ

**Applies to:** **Usability tests** and **media surveys**

You can bring your own external participants to usability tests and media surveys. Below, you'll find a list of frequently asked questions and their answers.

<details>

<summary>How do I screen external participants for a BYO study?</summary>

There will be no screener questions or targeting attributes in BYO studies, so researchers should only invite pre-screened participants. You can access the invite link for your study on the **Overview** tab.

</details>

<details>

<summary>How do I invite my participants to my BYO study?</summary>

You have two options to invite your own participants to a study:

* Invite via share link.
* Invite from Private Panels.

You’ll select your recruitment method when setting up your study. If you choose to invite using a share link, the link will become available as soon as you launch your study. If you choose to invite participants from Private Panels, you’ll do so directly in the builder.

</details>

<details>

<summary>Which devices can participants use to complete a BYO study?</summary>

Usability tests and media surveys can be completed via a desktop/laptop computer or via mobile device. You will set this specification at the study level. For example, if you set the device type to desktop, all participants will be required to complete the study on a desktop or laptop computer.

</details>

<details>

<summary>Can I invite participants outside the United States?</summary>

Yes! As you’ll be pre-screening your participants and sharing the URL to your BYO study directly with them, you can invite participants from all over the world and gain perspectives from multiple global markets.

</details>

<details>

<summary>Is there a participant limit?</summary>

Participant limits for BYO studies are optional. For more information, see [Manage participant limit and incentive in a usability test](/usability-tests/create-a-usability-test/manage-participant-limit-and-incentive-in-a-usability-test) or [Manage participant limit and incentive in a media survey](/media-surveys/create-a-media-survey/manage-participant-limit-and-incentive-in-a-media-survey).

</details>

<details>

<summary>Can I add additional documentation that I may need my participants to complete before participating (informed consent, Figma consent, etc.)?</summary>

Yes, you’ll have the ability to add these documents to your BYO studies just like those that recruit from our Dscout Scout Panel. For more information, see [Custom informed consent](/getting-started/research-basics/custom-informed-consent).

</details>

<details>

<summary>Does my BYO study need to be submitted for review?</summary>

No! You can launch your BYO study whenever you’re ready. You do not have to submit a review request to a member of the Dscout team. However, we’re always happy to review your study before you launch if you’d like.

</details>

<details>

<summary>How long will participants have to complete their BYO study?</summary>

Once they have started, participants will not have any set time limit to finish the BYO study. Participants will be able to start the study as long as they have access to the shared link (and the researcher has launched and activated the study from the builder).

{% hint style="info" %}
**Note:** Any participants that have started the study before you deactivate the share link or before your participant limit is reached will still be able to complete the study. Deactivating only prevents new participants from starting the study, if they haven't already done so.
{% endhint %}

</details>

<details>

<summary>Can I reopen my BYO study to allow more participants in after I’ve deactivated my study?</summary>

Yes! You can simply toggle your BYO study back to “active” if you’d like to allow more participants the chance to complete your study. You’ll likely want to re-share your study URL again to ensure that traffic is coming to your study. The URL will remain the same regardless of how many times you activate or deactivate it. If your study has a participant limit, you'll need to increase it before you're able to re-launch.

</details>

<details>

<summary>How will my participants be paid?</summary>

BYO participants can either be paid via Dscout or outside of the platform. You'll make this decision when you build your study. If you choose to pay participants via Dscout, payments will be automatically sent via PayPal seven days after a participant completes their entry. If you choose to pay participants outside of Dscout, you're responsible for ensuring participants receive the incentive they're owed.

For more information on bringing your own participants to a study, see [Recruitment options in a usability test](/usability-tests/what-are-usability-tests-in-dscout/recruitment-options-in-a-usability-test) and [Recruitment options in a media survey](/media-surveys/what-are-media-surveys-in-dscout/recruitment-options-in-a-media-survey).

</details>


# What are usability tests in Dscout?

Usability testing is the fastest way to get feedback on a website, prototype, or design. This study type lets you ask participants to perform tasks that reflect their goals—for example, purchasing an item on your e-commerce website—and measures whether they can complete the task, how long it takes, and more. Wondering if your product is working as intended? Want to know where your users are getting stuck? Try a usability test.

In Dscout, some key usability test features include:

* **Continuous recording:** Record participants’ screens and/or cameras to get the full picture of their experience. For more information, see [Device and recording options in a usability test](/usability-tests/what-are-usability-tests-in-dscout/device-and-recording-options-in-a-usability-test).
* **Task-based prompts and metrics:** Direct participants to prototypes on platforms such as Figma, capturing success rates, time on task, and more. For more information, see [Add a Figma prototype to a study](/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study).
* **Privacy options:** Guard your participants’ personal information so you can collect the data you need without compromising security. For more information, see [Privacy blur](/study-basics/testing-prototypes/privacy-blur).

### Recruitment options

To find participants for a usability test, you can:

* Add participants from an existing Dscout screener.
* Auto-recruit from Dscout’s Scout Panel.
* Auto-recruit from Dscout's Partner Panels.
* Invite your own participants.
* Add participants from Private Panels.

For more information, see [Recruitment options in a usability test](/usability-tests/what-are-usability-tests-in-dscout/recruitment-options-in-a-usability-test).

### Usability tests vs. media surveys

Usability tests are ideal when you want to:

* Determine whether early concepts or prototypes are usable and identify the direction you should pursue.
* Improve the effectiveness and efficiency of a website or app by identifying friction points through task completion and click‑mapping events.
* Validate a product pre‑launch by measuring task success and reviewing a full session recording.
* Reduce friction or discover new use cases by watching real users perform critical tasks.

However, you might be wondering whether to use a usability test or media survey. To help, here’s a comparison of each study type to help you choose:

| Capability                      | Usability test            | Media survey                                                                                                                                                                                                                                                                                      |
| ------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Participant limit**           | 100 participants          | 1,000 participants                                                                                                                                                                                                                                                                                |
| **Recommended incentive range** | $1–200                    | $1–100                                                                                                                                                                                                                                                                                            |
| **Media capture**               | Continuous recording      | <p>Individual photo, video, and screen-recording question types</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Media surveys are limited to a maximum of three video questions (including screen recording questions).</p></div> |
| **Heat maps and click data**    | Yes (on Figma prototypes) | No                                                                                                                                                                                                                                                                                                |

For more information on media surveys, see [What are media surveys in Dscout?](/media-surveys/what-are-media-surveys-in-dscout) Or if neither of these seem to be the right fit, read more about our other study types in [Dscout quickstart guide](/getting-started/dscout-quickstart-guide).


# Question types in usability tests

Usability tests let you ask participants to perform specific tasks related to concepts, prototypes, and more. Responses are continuously recorded, and you can combine many different question types in your study to collect the information you need.

The table below outlines which Dscout question types you can use in a usability test:

{% hint style="info" %}
**Note:** The following question types can be combined in the usability test portion of your study (on the **Usability test** tab). However, only multiple choice questions can be used in the screener portion (on the **Screener** tab) when auto-recruiting participants.
{% endhint %}

| Question type                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multiple choice**           | <p>Provide participants with a list of options to choose from.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Tip:</strong> Knockout logic can be applied to multiple choice questions to disqualify applicants during the screener portion of your study. For more information, see <a href="/recruit-participants/dscout-scout-panel/knockout-questions">Knockout questions</a>.</p></div>                                                                                           |
| **Typed response**            | Allow participants to provide a written response. You can limit responses to 140 characters or apply no limit.                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| **Checkpoint**                | Provide additional context or instructions to participants without asking a question or requiring a response.                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Scale**                     | Have participants rate how they feel about a statement or stimuli on a predefined scale. You can customize the **Start value** and **End value** with your own labels.                                                                                                                                                                                                                                                                                                                                                                         |
| **Ranking**                   | <p>Have participants rank a list of options in comparison to one another. For example, “Rank the following pizza toppings from best (1) to worst (6).”</p><p><br>For more information, see <a href="/study-basics/question-types/ranking-questions">Ranking questions</a>.</p>                                                                                                                                                                                                                                                                 |
| **Number**                    | Have participants provide a number up to nine digits in length.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Card sort**                 | <p>Provide participants with a set of items (cards) to sort into different categories.</p><p>For more information, see <a href="/study-basics/question-types/card-sort-questions">Card sort questions</a>.</p>                                                                                                                                                                                                                                                                                                                                 |
| **Tree testing**              | Have participants show you how they would navigate an organizational structure to find a specific item or complete a specific task. For more information, see Tree testing questions.                                                                                                                                                                                                                                                                                                                                                          |
| **Task (up to 15 per study)** | <p>Prompt participants to complete a specific action or activity on an attached website or prototype. For more information, see <a href="/study-basics/question-types/task-questions">Task questions</a>.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><br><strong>Note:</strong> It’s important to maintain participants’ privacy, including when capturing task screen recordings. For more information, see <a href="/study-basics/testing-prototypes/privacy-blur">Privacy blur</a>.</p></div> |
| **Talk out loud**             | Allow participants to provide a verbal answer that will be transcribed as part of their recorded response.                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Question groups**           | Organize related questions in the builder for easier study design or to randomize the way they are presented to participants. For more information, see [Question groups](/study-basics/question-types/question-groups).                                                                                                                                                                                                                                                                                                                       |
| **Multi-variate**             | Organize questions by concept or design variants and randomize how they are presented to participants. For more information, see [Multi-variate testing](/study-basics/question-types/multi-variate-testing).                                                                                                                                                                                                                                                                                                                                  |

To learn more about adding questions to your study, see [Add questions to a usability test](/usability-tests/create-a-usability-test/add-questions-to-a-usability-test).


# Recruitment options in a usability test

Finding the right participants is the key to great research. When conducting usability tests, you have a few options to find just the voices you want to hear.

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FvkI12YKW1AzoV4hmyYbY%2FRecruitment_approach%20(3).jpg?alt=media&amp;token=b53322e7-471c-4627-9e9a-f2a0a3268f26" alt="" width="563"><figcaption></figcaption></figure>

To recruit for your study, you can:

* **Auto-recruit from the Dscout Panel:** Build a screener into your study to qualify or disqualify applicants from Dscout’s existing Scout Panel. Those who meet your criteria automatically advance to your study. Those who don’t are rejected.
* **Auto-recruit from Dscout's Partner Panels:** Build a screener into your study to qualify or disqualify applicants from Dscout’s Partner Panels like Respondent. Participants complete your screener on the relevant third-party platform and are then redirected to Dscout to complete the study if they qualify. For more information, see [Auto-recruit from Partner Panels](/recruit-participants/partner-panels/auto-recruit-from-partner-panels).
* **Recruit from standalone screener:** Invite participants you’ve already found using a Dscout screener to your study. For more information, see [Add participants from a screener to a usability test](/usability-tests/what-are-usability-tests-in-dscout/add-participants-from-a-screener-to-a-usability-test).
* **Invite your own participants using a share link:** Generate a share link to send to participants you’ve found outside of Dscout. For more information on sharing links with participants, see [Share usability test links with participants](/usability-tests/manage-a-usability-test/share-a-usability-test-link-with-participants).
* **Invite your own participants from Dscout's Private Panels:** Add participants to your study from your own Private Panels. For more information, see [Add panelists to a Dscout study from Private Panels](/private-panels/get-started/add-panelists-to-a-dscout-study-from-private-panels).




---

[Next Page](/llms-full.txt/1)

