Run in-app surveys at the moments that matter: right after someone uses a feature, finishes setup or gets stuck. Every answer arrives with who gave it and what plan they’re on, so the right team can act on it.
The best time to ask about a feature is a few seconds after someone used it.
The details are still fresh, the person answering is the one who did it, and one question on the page they’re already on takes a second to answer. Usertick opens the survey at that moment, for the users you choose, and keeps it from coming back too often.
How targeting and triggers workEvery way to show a survey on your siteEach moment comes with what opens the survey, who it shows to and a template to start from. Change the wording, the timing or the audience to fit your product.
Ask how well a feature did its job right after it ran. Your app tells Usertick when an export finishes, and the survey can wait for the third export, so only people who rely on it are asked.
Check how getting started felt while it’s fresh. Show the survey on the page people reach once the checklist is done, and learn which step slowed them down before they forget it.
Find out whether people found what you shipped. Ask the users on the plans that include it, from the date you choose, and hear what keeps the rest from trying it.
Catch a problem while the person who hit it is still on the page. Usertick notices rage clicks, buttons that do nothing and page errors adding up, then asks what went wrong.
Track how likely users are to recommend you without sending another email. Ask NPS inside the app to people who have been around for a month, then not again for 90 days, and follow each score with its own question.
Learn what holds people back from upgrading. When someone heads away from the plans page without choosing one, ask what stopped them while the plans are still on screen.
Add the widget, tell it who is signed in and send the moments only your app knows about. After that, every survey is set up in Usertick, without another release.
Add the script tag, or the npm package for React, Next.js, Vue, Angular, Svelte and other frameworks. The widget follows route changes on its own, so a single-page app needs nothing extra.
Pass your user ID and a few traits, such as the plan or the role. Each answer arrives with the person who gave it, and from Starter surveys can target by any trait.
Send an event when something worth asking about happens, such as an export or a finished setup. A survey opens on that event, on a later call or only when its details match.
Each answer carries the user’s ID, name, email and traits, and AI reads what they wrote, so a bug reaches your engineers and an idea reaches your roadmap.
The inbox shows who answered, with their company and plan. A hash from your server can verify the user ID, so a verified mark means the answer came from that user.
AI reads each written answer and sorts it as a bug, an idea, a complaint, a question or praise, with its theme and urgency. On every plan, bugs can go to Jira or Linear as issues.
On every plan, Amplitude, Mixpanel and Segment receive an event for each answer from an identified user, so you can set what people said beside what they did.
Only one popup shows at a time. Other surveys wait until it closes, so a user is never handed two at once.
Don’t interrupt holds the survey while the user is typing, scrolling or watching a video, and opens it at the first pause. Pro and above.
Show a survey once, until it’s answered, or again after the number of days you set, with a wait after each close.
Double the wait after each close, and after the third close the survey stops showing to that user. Pro and above.
Show a second survey only to users who skipped the first, or who answered it more than 90 days ago. Starter and above, and 1 survey on Free.
Show the survey to a share of the users who match, so a busy product hears enough without asking everyone. Starter and above, and 1 survey on Free.
Lead with a question that takes a second to answer, and ask the follow-up only to people who answered it. Branching picks the next question by the answer, so a low score and a high score each get their own.
Open the survey once the export has finished or the setup is done. A short wait after the trigger lets the user see the result first.
Target by plan, role or any trait your app sends, so a question about a Pro feature reaches only Pro users and an admin question reaches only admins.
Show each survey once, or again after weeks, and use the earlier-survey rules so nobody gets three surveys in one week.
Use your colors, fonts and corners, and the names your product uses on screen. A survey that looks like part of the app reads as part of it.
Give each answer an owner, mark it Planned or Resolved as the work moves, and tell users when what they asked for ships.
Start from a survey written for a feature, a finished setup or an upgrade, or from a single question that fits the moment.
Yes. The widget follows route changes on its own, so page rules, triggers and page counts keep working as people move around your app without a full page load. Install it once with the script tag or the npm package, and start it a single time when the app loads.
Pass the signed-in user to Usertick with their ID and a few traits, such as the plan, the role or the number of seats. A survey can then show only to identified users, or to users whose traits match rules like plan is pro or seats is at least 10. Trait and sign-in rules are on the Starter plan and above.
Yes. Your code sends an event, such as report_exported, and the survey that listens for it opens. The survey can wait for a later call, such as the third export, or open only when the event’s details match a rule. Custom events work on 1 survey on the Free plan and on every survey from Starter.
No. The widget loads after the page without holding it up, and it draws inside its own isolated layer, so your styles don’t reach it and its styles don’t reach your app. If Usertick can’t be reached, your app works as usual, and an answer that couldn’t be sent is kept in the browser and sent later.
Only one popup shows at a time, and each survey has its own repeat setting: once, until answered, or again after the days you choose, with a wait after each close. Earlier-survey rules keep a follow-up away from users who already answered, and on the Pro plan and above the wait can double after each close.
Usertick runs in web apps, including on phones and tablets in the browser, where a popup shows as a sheet at the bottom of small screens. Native iOS and Android apps aren’t supported, because Usertick runs in the browser only.
Yes. Your server signs the user ID with a secret, and the widget sends that signature with each answer. Usertick checks it and marks the answer as verified, so a user ID typed into the browser can’t pass as someone else. Verification works on every plan.
Surveys in your app, page rules, delays, exit intent, NPS and the Jira, Linear, Amplitude, Mixpanel and Segment connections work on the Free plan, and so do custom events and earlier-survey rules on 1 survey. Trait and sign-in rules, and custom events on every survey, are on the Starter plan and above. The smart triggers that notice frustration are on the Pro plan and above.
Start free, see what your customers mean, and get each answer to the person who can act on it.
