A Respondent Watches, Then Answers, On One Page

What you can do together

• Put the clip inside the question, so a respondent watches and answers without leaving the survey or losing their place in it.
• Allow only the survey domain to render the material, with signed URLs that expire, which is what keeps unreleased stimulus from being passed around.
• See how much of the clip respondents watched beside what they said about it, rather than inferring attention from completion.
• Have a workflow read thousands of responses through Qualtrics's server and summarize the themes, with a person reviewing before anything is circulated.

How it connects

Playback is the JavaScript widget, placed in a Qualtrics question through its HTML editor. The documented set covers video, audio, image, document, collection and playlist players as well as library views, so a question can carry one clip or a short set for comparison. Nothing about the media enters Qualtrics, and no survey-platform module is required.

Two controls matter for stimulus material that should not circulate. Embedding is restricted to the domains you name, so the Qualtrics domain serving the survey is allowed and anything else refused, and content URLs are signed and expire rather than staying valid once a respondent shares one. Engagement on the embed is read back per surface, so how far respondents actually watched is measurable rather than assumed from a completion rate.

Qualtrics runs an official MCP server over its public API, and AI Intelligence Hub connects to MCP servers as a client. The connection is configured once with a name, the server URL, the transport and the headers carrying its credential, and the tool list is fetched when it binds rather than coded in. A workflow can then read responses and distributions through that server. The connection carries its configured credential, so what it can reach in Qualtrics is what that credential is granted there.