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.

Choose a format

Inline form. Sits in the page like normal content. Best when you want feedback about that specific page — a checkout, a help article, a product page. Least intrusive, and the format people are most willing to complete.

Popup. Appears over the page, usually on a trigger like exit intent or time on page. Higher visibility, higher irritation. Use sparingly and never on a page where someone is trying to complete a task.

Feedback button. A persistent tab pinned to the edge of the screen. Doesn’t interrupt anyone, and catches people who actively want to tell you something. The best default for a general “how are we doing” route.

Install the snippet

Copy the generated code and paste it into your site’s HTML where you want the survey to appear — or, for the popup and button formats, anywhere before the closing </body> tag.

The snippet is self-contained. It doesn’t need jQuery or any other library.

If someone else manages your website, use the option to send the snippet to a developer rather than trying to relay it yourself.

Common platforms

• WordPress — paste into a Custom HTML block, or use a header/footer snippet plugin for site-wide formats
• Shopify — add to your theme layout for site-wide, or a specific template for one page
• Webflow, Squarespace, Wix — use the custom code or embed block

Verify it’s working

After installing, load the page in a private window and confirm the survey appears. Then submit a test response and check it arrives in your workspace.

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

If it doesn’t appear

• Check placement. Inline forms only appear where the snippet is; popups and buttons need to load site-wide.
• Check for aggressive caching. Many hosts and CDNs cache HTML — clear the cache after installing.
• Check your content security policy. If your site sets a CSP, it may block the embed. You’ll see an error in the browser console naming the blocked domain.
• Check ad blockers. Some block third-party widgets. Test in a clean browser profile before assuming it’s broken.

Still not working? Send us the page URL and we’ll look at it directly.