User Interviews + UserTesting integration for unmoderated tests

On this page:

• About the User Interviews + UserTesting integration
• How to send a UserTesting test to your User Interviews audience
• How to finalize participation and incentives

About the User Interviews + UserTesting integration

• The User Interviews + UserTesting integration works for any UserTesting survey or interaction test that uses Invite Network.
• Recruitment and screening happen in User Interviews, and qualified participants are automatically directed into your UserTesting test.

• The integration streamlines recruiting and routing, but successful completion still depends on manual status updates after the sessions are completed. Here is what's automated and what's manual:

  Automated	Manual
  Screener distribution Redirecting qualified participants into UserTesting Status syncing during fieldwork Marking User Interview participants as “Submitted” after UserTesting test completion	Changing User Interview participant status from Submitted → Completed to release incentive payment Excluding participants in the correct order (User Interviews → UserTesting) if removing due to poor quality

• Be sure your team has a clear owner for post-test reconciliation to avoid delays in incentives or reporting discrepancies.
• If you have questions about setup or reconciliation, your Customer Success Manager can help walk through best practices before launch.
  
   

How to send a UserTesting test to your User Interviews audience

Part I: Create your Invite Network test in UserTesting

1. Build your test in UserTesting as your typically would.
2. Select Invite Network as the audience you'll use.
3. After you launch the test, copy the Invite Network link.

Part II: Set up the screener in User Interviews

In this part, you will connect the two platforms. They will communicate with one another via UI IDs and participant statuses once the test is launched and participants begin entering the screener.

1. Create your screener survey.
2. Navigate to the Integration page.
3. Paste the Invite Network link from UserTesting into the designated field.

Part III: Launch your User Interviews project

When you launch the project in User Interviews:

1. Participants are automatically invited to complete your User Interviews screener.

2. Participants who pass the screener are automatically redirected into the UserTesting Invite Network test.

    

How status updates work during fieldwork

As the test fills, User Interviews and UserTesting communicate in the background:

• Participant IDs are passed back and forth between platforms.
• Statuses update automatically (for example: screen out, qualified, incomplete, submitted).
• When a participant completes the UserTesting test, their status in User Interviews is automatically updated to “Submitted.”
• In UserTesting, the same User Interviews participant ID will appear as a complete.

You’ll see slightly different ID formats across platforms for UserTesting tests (surveys, interaction tests):

• User Interviews format: pp_9exh736
• UserTesting format: i9exh736

The IDs correspond to the same participant, just formatted slightly differently. In User Interviews, the IDs begin with ‘pp_’ and in UserTesting they begin with the letter ‘i. Everything that follows is identical.

The ID format aligns 100% between User Interviews and UserTesting Classic tests (talk-out-loud, moderated): pp_9exh736

 

How to finalize participation and incentives

While recruitment and routing are automated, finalizing participation and incentives is manual. The following steps are critical:

Part I: Triggering incentive payments (required)
When a participant completes the UserTesting test:

• Their status in User Interviews will show as “Submitted.”
• To release the incentive payment, you must manually update their status from “Submitted” to “Completed” in User Interviews.

If this step is not completed, incentive payment will not be triggered. 

Please make sure your team understands this responsibility before launching tests.

Part II: Excluding a session (if needed)

If you need to exclude a participant:

1. First, remove the participant in User Interviews.
2. Then remove the participant in UserTesting.

Order matters. Once the participant is removed from UserTesting, the participant ID will no longer be visible there. Removing from UserTesting first can make reconciliation more difficult.

Part III: ID usage limitation

The User Interviews and UserTesting participant IDs:

• Are used for tracking between systems
• Cannot be used for re-contacting participants

If you need to reconnect with a User Interviews participant, do so directly through User Interviews using standard platform workflows.The IDs displayed through the User Interviews + UserTesting integration do not remain with the participant outside of the current test.

Related content