Embedding a survey on your website

Embedding puts the survey where the experience is happening, which is why website feedback collected in context tends to be more specific than feedback collected by email a day later.

Get the code

On the survey’s card in Survey Builder, open the ⋯ menu and choose Embed.

Under Widget Style there are two options:

Full Survey — Complete survey embedded in your page. The survey renders inline where you place the code. Best when you want feedback about that specific page, and the format people are most willing to complete.

Popup Feedback — A button that opens a popup survey. Adds a fixed Feedback button to the corner of your site; clicking it opens the survey over the page. Best as a general “how are we doing” route that’s always available without interrupting anyone.

Submissions from the embed land on the Website widget touchpoint, so they show up in every report next to your QR codes and email sends. → Touchpoints

Pick a style, then Copy Code. If someone else manages your website, Send to Developer emails it to them instead — much less error-prone than relaying it yourself.

Install it

Full Survey produces an iframe. Paste it into your page exactly where you want the survey to appear.

Popup Feedback produces a button plus a script tag. Paste it anywhere before the closing </body> tag, on every page you want the button to appear on.

Common platforms

• WordPress — a Custom HTML block for Full Survey; a header/footer snippet plugin for the popup site-wide
• Shopify — the relevant template for Full Survey; your theme layout for the popup
• Webflow, Squarespace, Wix — the custom code or embed element

Check it worked

Load the page in a private window, confirm it appears, then submit a test response and check it arrives.

Do the test submission. A survey that renders but doesn’t record is a failure mode that goes unnoticed for weeks — you only find out when you wonder why nobody’s responding.

If it doesn’t appear

• Caching. The most common cause. Clear your site and CDN cache after installing.
• Content Security Policy. If your site sets one, it may block the widget script. Your browser console will name the blocked domain.
• Ad blockers. Some block embedded widgets — test in a clean profile before concluding it’s broken.
• Wrong placement. Confirm the code is inside the page body and not somewhere your theme strips.

Still stuck? Send us the page URL and we’ll look at it.