Test live prototypes and websites inside your interviews

A product team can build a working prototype on Replit or deploy a new landing page to Vercel in an afternoon. Getting real consumers to try it usually means a separate testing tool, a link that opens in another tab, or a recording someone narrates alone. The clicks end up in one place and the reasons in another. With the Website embed stimulus, the live site opens inside the Conveo interview, and participants use it while the AI research assistant asks what they expected and why.

A short, silent look at website stimuli: from pasted link to playback.

How it works

• Add a Website embed stimulus. In your study's stimuli, pick Website embed, give it a title and paste the link to your hosted prototype, landing page or web app. Attach it to a question or a section of your topic guide.

• Conveo checks the link. Some sites refuse to be shown inside another page. Conveo checks whether yours allows embedding before you can attach it, so a blocked site shows up as a warning during setup, before any participant meets it.

• Participants use it inside the interview. The site opens in the interview window. Participants share their screen and click through it while the AI research assistant asks your questions and follows up on what they say.

• A fallback when a page will not load. If the site does not load for someone, a "Not loading? Open it in a new tab" link sits above it.

One stimulus type for code prototypes, live pages and web apps

Website embed covers anything hosted that allows embedding: a prototype built on Replit or deployed on Vercel, a landing page you want to check before a campaign, or a web app your team already runs. Figma files keep their own stimulus type, described in Figma prototype testing. For a site that blocks embedding, use the Link stimulus type and participants open it themselves.

Research teams asked for it in five situations

These come from teams we work with in financial services, software, music and media, online betting, apparel, food and drink, healthcare and home security, and from digital agencies. We kept them anonymous.

• New websites before launch. A redesigned site or a new offer gets first impressions and a usability check before it goes live.

• Think-aloud journey tests. Participants get a scenario, work through the journey and say what they expect at each step.

• New against current. People try a new flow and say how it compares with the one they use today.

• Digital products in progress. Agencies and product teams test single moments of a website or web app journey while they build it.

• Usability checks that need follow-up questions. Teams that sent people to a separate testing tool want the site and the questions about it in one video conversation.

What this means for your research

The site and the conversation happen in the same session, so you see where someone stalls and hear why in that moment. A prototype can go in front of consumers the day it is deployed, long before anyone builds the real thing.

Two limits to know. Embedding depends on the site owner: when a site blocks it, the setup check tells you and the Link stimulus type is the fallback. Conveo records the shared screen and the conversation, and clicks inside the site are not tracked, so there are no heatmaps or click analytics.

Website embed in under three minutes, start to finish

From adding the link to the setup check, the interview and playback, with the five ways research teams asked to use it.

Boris shows website embed in two and a half minutes

Boris Gordts, who built the feature with Dag Malstaf, adds a Replit prototype as a stimulus, opens it in a test interview and shows the setup check on a site that blocks embedding.

Read the stimuli guide to set up a stimulus.