In-app surveys that reach
the right users at the right time
Canviq collects customer feedback in one place: a public board, in-app surveys and email surveys. Ask inside your product when a customer has just done something worth asking about, and read the answers next to everything else they have told you.
Free up to 100 responses a month. No credit card.
Why ask inside the product instead of by email?
An email survey reaches a customer when they are doing something else. They have to remember what your product did for them, and many will not bother. A survey shown inside the product reaches them while the experience is fresh, so the answer reflects what just happened and not a vague memory.
Email still has a job. It reaches customers who have not logged in lately, which is often the group you most want to hear from. Canviq runs both from the same survey, so you write the questions once and choose the delivery.
How does an in-app survey get to the right person?
Triggers on real events
You add the Canviq JavaScript SDK to your app once. After that, a survey appears when your product reports an event you picked, such as finishing onboarding or using a feature for the first time. Timing is the main reason in-app surveys get better answers than a blast to your whole list.
Targeting rules that decide who sees it
When an event fires, Canviq checks the user against your rules before showing anything. Rules can use plan, device, locale or a custom attribute you send, so a question about a paid feature never reaches a free user. Targeting rules are available on Startup and above. For the PMF survey, you can limit it to people who have actually been using the product.
Limits that protect your customers
By default, a customer who answers a survey is not asked again, and one who dismisses it is left alone for 30 days. Those two rules are fixed defaults. Each survey also has a cooldown between showings (7 days by default) and a cap on how often one person is asked (once every 30 days by default), and you can change both for that survey. That keeps response quality up and keeps your product from feeling like a questionnaire.
A sensible first setup is small. Pick one event that marks a customer getting value, write a survey of three or four questions, target it at customers who have been active recently, and leave the fatigue limits on. You can widen the audience once you have seen the first answers and know the question reads the way you meant it.
What can you ask in an in-app survey?
In-app surveys can ask rating, NPS, multiple choice, yes or no, free text, matrix and ranking questions. When someone answers from the survey link instead, you also get image choice, file upload and branching, so a later question can depend on an earlier answer. The surveys feature page lists the templates and settings in full.
If you want one question to start with, the PMF survey asks how disappointed a customer would be if they could no longer use your product. The customers who answer "very disappointed" are the ones who would miss you most, and their answers show you what to protect and build on.
Where do the answers go?
Survey answers do not sit alone in a separate report. They appear in the same dashboard as ideas from the public feedback board, where customers post requests, vote and follow the outcome. A survey tells you what a sampled group thinks. The board tells you what customers volunteer. Reading both is how you tell a loud request from a widely shared one.
For a wider view of the whole approach, see voice of customer.
What do people ask before adding in-app surveys?
Do I need a developer to run in-app surveys?
You build and edit surveys in the dashboard without code. Showing them inside your product needs one SDK snippet added once, and it works with React, Next.js, Vue, Angular and plain JavaScript.
How do I stop users from being over-surveyed?
By default, a user who answers a survey is not shown it again, and one who dismisses it is left alone for 30 days. Those two rules are fixed defaults. Each survey also has a cooldown between showings (7 days by default) and a cap on how often one person is asked (once every 30 days by default), and you can change both for that survey.
What about customers who are not in the product?
The same survey can go out as an email link, so customers who have not logged in recently can still answer.
Ask your customers at the moment it matters.
Free up to 100 responses a month. No credit card.
Start freeLast reviewed: