Run Different Interviews on the Same Website

You can ask landing-page visitors one set of questions, invite customers by email to another interview, and leave a feedback launcher available elsewhere. Use three Studies in one Project and install the Project snippet once.

1. Install once and choose your Studies

Open Studies → Copy snippet and install it across the website, including the page your email link will open. Use Website interviews to check a public page where it runs. See Widget Integration for the snippet and installation troubleshooting.

Reuse First user interview as your general-feedback Study, or pause it before adding a replacement. It starts active and eligible everywhere, so leaving it unchanged can compete with another broad Study.

Create the other two Studies with New study. Give each a distinct title and research goal. Use the interview recipes to build and save each flow.

2. Ask landing-page visitors

In the landing Study:

Under How participants arrive, choose On-site Invitation → Open when eligible.
Write a short invitation, such as “What brought you here today? Share what you were hoping to find.” Match its duration to your interview.
In page placement, choose Only these pages. Set Path to / and Rule to Show this page only.
Under Go live → Interview websites, add your website origin, such as https://example.com. Save and resolve any readiness items before activating.

Use a discovery conversation about what the visitor came to do, or a concept-reaction recipe if you want to hear how they interpret the page.

3. Invite customers by email

In the email Study:

In the new draft Study, add the website origin under Go live → Interview websites. The generated link uses the first website in this list.
If the interview should open a specific page, set Only these pages with that path while the draft still uses On-site Invitation. The generated URL uses the first included path, or / if none is set. Make sure the Project snippet runs there.
Choose Recruitment link under How participants arrive, save, and activate when ready. Page placement no longer controls who can open this Study through the link.
Choose Copy link and paste the generated recruitment URL into your email tool. Keep the complete link, including ut_research.

For example, write: “I'd like to understand how you handled your last busy inbox. Would you share your experience in a short voice interview?” Then add the copied link.

The link opens the selected Study on your website. It is not a separate hosted survey page. Opening it does not start recording; the participant still chooses to start and grants permissions. UserTold generates the link but does not send email or track recipients. Changing the invitation away from Recruitment link revokes the old link; switching back creates a new one.

In the general-feedback Study:

Choose On-site Invitation → Launcher only.
Use a label such as “Share feedback” and a short invitation that says this opens an interview.
Choose Every page for placement. Keep languages unrestricted unless you need a particular language.
Save, add the website origin, and activate when ready.

Use a short Talk flow: ask what they wanted to share, what happened the last time, and what they expected instead. This launcher starts a voice interview, with microphone permission and the recording notice; it is not a text feedback form.

Which interview appears?

Only one Study wins automatic placement. With this setup, the exact / rule selects the landing Study on the homepage; the broad general-feedback Study appears on other pages. The general-feedback launcher is not a second simultaneous launcher on /. The email link selects its own Study directly.

Page and language specificity are considered before priority and Project order. You do not need a priority change for this exact-page versus every-page example. Keep the starter and any other active Studies from competing with these rules. See Visibility matching if you need exclusions, language targeting, or overlapping rules.

Test all three entry paths

Open / without an invitation query. Confirm the landing invitation appears.
Open another page, such as /help, without an invitation query. Confirm the general-feedback launcher appears and opens the intended interview when clicked.
Open the copied email link. Confirm it selects the email Study, even when the destination normally shows another invitation.
Complete an interview from each entry path. In Interviews, check the Study association, recording, and transcript.

For a routing check in the CLI, run usertold study resolve --path / --language en --json, then repeat with /help. This checks automatic selection; test the recruitment URL itself in a browser.

If nothing appears, check activation, placement, language, and the installed Project key. An invalid or revoked recruitment link does not fall back to a different Study. An unavailable automatic winner also does not fall back to the broad Study.