DOCS · FIELDINGEMBEDDING

Ask inside your website.

Copy an embed from the web app and place it where your respondents already are. Your website builder needs to support custom HTML and scripts.

Before you start: save the survey and open collection in Deploy. Use respondent preview first to test questions without saving answers.

Copy the embed from Deploy

  1. Open the web app and choose your saved study.
  2. Go to Deploy, open the survey to respondents, and copy the embed snippet.
  3. In your website builder, add a custom HTML or embed block where the survey should appear. Paste the complete snippet into that block’s source editor.
  4. Save the page and test its published or staging version. Some builders do not run scripts inside their editor preview.

The app supplies your survey identifier and host address. Copy these from Deploy rather than choosing a domain yourself. The structure looks like this:

<div data-voxq-survey="YOUR_SURVEY_ID"></div>
<script src="https://YOUR_APP_HOST/embed.js" async></script>

Both values above are placeholders. They are not a working survey or an announced voxq domain. Paste the actual snippet provided by your app, unchanged.

What respondents see

The interview presents your questions one at a time, with answer controls for each format. People can answer without a researcher account. Basic branding comes from your study settings.

For hosted images, video, or audio, people choose Load before contacting the media host. Include a description or transcript and test it on mobile. File uploads are not available in the question editor yet.

When the study owner enables AI voice in Deploy, respondents can explicitly opt in to microphone access and a remotely processed conversation through Not Organic and OpenAI. On-screen controls and typing remain available. Speech can be reviewed and edited before submission and never sends an answer automatically.

Allow voice and local downloads in an embed

The generated embed needs permission for microphone access, audio playback, and downloads. Serve the host page and survey over HTTPS. Your website administrator must also allow the survey origin in the host’s Permissions-Policy; the embed cannot override a host policy that blocks the microphone.

Keep the permissions supplied by the embed loader. Microphone and autoplay permissions allow the browser to offer voice; they do not bypass respondent consent or browser playback restrictions. If your website builder wraps the survey in another sandboxed frame, it must also allow the required permissions and downloads. Give its administrator the developer permissions checklist.

Local recording requires a separate explicit opt-in. Supported browsers can download audio and a timeline only to the respondent’s device; Voxq does not upload or store that recording or persist the voice transcript on its server. Submitted survey answers are still stored normally. Recording locally does not stop Not Organic and OpenAI from processing live voice remotely.

If your platform cannot permit voice or downloads, share the full interview link from Deploy. The typed survey remains usable inside the embed.

Check the published page

  • Confirm the right study appears and collection is open.
  • Try the page on a phone and move through its controls with the keyboard.
  • Check long choices, ranking controls, scale bounds, media descriptions, and dynamic followups.
  • If voice is enabled, check the opt-in, microphone permission, playback, typed fallback, and separate recording/download controls on the published HTTPS page. A live voice test can spend the owner’s wallet funds.
  • To verify real collection, submit a clearly labelled test answer and check Results. This creates saved data; respondent preview does not.

Preview followups are templates. Connected followups need a configured Not Organic account and available model access. Test the mode respondents will use before inviting them.

If the survey does not appear

Check that your builder supports scripts in custom HTML blocks, that the complete snippet is present, and that the survey is open. Try the published page rather than only the editor. If media does not load, check the hosted URL and offer its description or transcript.

If the website platform blocks the embed, share the interview link from Deploy while your website administrator checks its settings. You do not need to rebuild the survey.

Explain the invitation

Tell people who is asking, what answers will be used for, and what information they should avoid entering. Not requiring login does not make a study anonymous if its questions ask for identifying details.

Keep the snippet free of passwords and account credentials. For customer-account linking or a custom integration, give your developer the developer embedding guide.

Want your own survey address?

Managed custom domains are planned. Use the link and embed supplied by Deploy until the app offers and verifies your domain. See what to prepare for a custom domain.