Show a survey on your own site or web app, on the pages you choose, when something happens, to the visitors it's about. Then stop asking them. It asks visitors questions; it isn't a screenshot or bug-report tool.
On Team and up. No credit card: every new account starts with 14 days of Growth, which includes it.
A "Feedback" tab waits for someone frustrated enough to click it. You hear from a few people, mostly on bad days, and never at the moment you wanted to understand: why people leave the pricing page, what they think of checkout, whether the new help article answered the question. The widget asks instead. You pick the question, the page, the moment and the share of visitors, and it keeps track of who has already answered or said no. For the method behind it, read how to collect feedback on your website.
When the page loads (after a delay you set), after time on the page, after the visitor scrolls, on exit intent on a desktop (with a time or scroll fallback you choose for phones), when your site reports an event such as a finished checkout, when a visitor clicks an element you name, or when your own code calls it. It follows page changes in single-page apps. From Team.
Rules on the page path (is, starts with, contains, ends with), with exceptions. Desktop or phone, signed-in or anonymous visitors, and a sample: ask 10% of visitors, not all of them. From Team.
Pass details such as plan or account age with identify, and show the survey only to visitors who match up to 10 rules. Or show it after someone has done something a set number of times, on a later visit, or when they came from a particular site or campaign. A signed identify links each answer to the contact. From Growth.
Set the wait before asking again after an answer, and after someone closes it without answering, plus a quiet period across every widget on the site. Ask everyone again when you want a fresh round. From Growth, signed-in visitors are remembered on every device, so an answer on a laptop counts on a phone.
Switch on consent mode and the widget writes nothing lasting to the visitor’s browser until your site calls SurveyRock('consent', true), so it can wait for your cookie banner. Until then it remembers only who closed or answered, in the tab’s session storage, which the browser clears when the tab closes. From Team.
The corner card and the edge tab never take focus, and the card collapses rather than cover the field someone is typing in. Spotlight moves focus into the survey and gives it back when it closes. Escape closes any of them, and reduced-motion settings are respected.
A card in a corner, a tab on the edge of the page, or Spotlight, a card in the middle of a dimmed page for the questions that matter most. On phones it becomes a sheet at the bottom of the screen, and a visitor can minimize it to a small button and come back to it on the next page.
The card follows your survey’s theme, with a separate dark-mode theme for visitors whose device is set to dark, and its own text uses your site’s font. Preview it on a real page of your site before it goes live, and send the preview link to a colleague.
Each answer records the page, the format, what opened it, and whether the visitor closed it before the end. Each widget shows how often it was shown, answered and completed, and its answer rate. Workflows run on each new response with those fields, for example posting a low score to Slack with the page it came from. From Team.
Add a Website in SurveyRock and paste its snippet into every page, or into Google Tag Manager. You do this once.
On a survey’s Distribute page, choose the Website, the format, the pages, the moment and how often.
Open a real page with the widget showing at once, as you set it. Nothing is counted or stored.
Answers arrive with the page and trigger beside them, and workflows send them to the people who can act.
Changes to which survey, which pages and when reach your site within about a minute, with no deploy on your side.
Shows a survey wherever you place it (inline, as a popup or as a slider) to everyone who loads that page. Use it for a survey that belongs on one page.
Decides who sees a survey, where, when and how often, and counts what happened. Use it to ask visitors as they move around your site or product.
Every paid plan can be paid monthly, or yearly at ten times the monthly price.
Step by step: Add the website widget to your site
Triggers and frequency: When the widget shows, and how often
Cookie banners: The website widget and cookie consent
For your team: SurveyRock for CX teams
Not on the Free plan: the widget starts on Team. Every new account gets 14 days of Growth, which includes it, so you can try it on your own site first.
The snippet loads in the background (async), so it doesn’t hold up your page. The survey itself loads only when the widget is about to show it.
If your site waits for consent, switch on consent mode: the widget writes nothing lasting to the visitor’s browser until your site says yes. Until then it remembers only who closed or answered, in the tab’s session storage, which the browser clears when the tab closes. The cookie consent guide lists what to put in your banner.
Yes, on Team and up. On Growth and up you can also target by details you pass about them, such as their plan.
As often as you allow. You set the wait after an answer and after a dismissal, and a quiet period across every widget on the site.
Yes. Add the snippet as a Custom HTML tag that fires on all pages.
Workflows on Team and up can post to Slack or call a webhook when an answer arrives. HubSpot and Zendesk connect on Pro and up.
An embed (Solo and up) shows a survey wherever you place it, to everyone who loads that page. The widget (Team and up) decides who sees a survey, where, when and how often, and counts what happened.