Umfragen
Stellen Sie Besuchern auf Ihrer Website eine Frage und lesen Sie die Antworten neben Ihren Analysen.
Building a survey
Surveys sit under Engage. A new survey starts blank or from a template: Net Promoter Score (NPS), product-market fit (PMF), customer satisfaction (CSAT) or cancellation reasons. Its kind is a Popover, which Prodantix shows on the page, or API, which your own code shows through the SDK’s getSurveys. The Questions tab orders the questions: a score from 0 to 10, a rating, an emoji scale, pick one, pick several, a written answer or a link. A question can be optional, and a branch sends an answer in a score range to a chosen next question. The survey ends on a thank-you message, and a preview beside the tabs draws it as a visitor sees it.
Who sees it, and when
Targeting narrows the survey to pages, to visitors in any picked cohort (none means everyone), to a feature flag and one of its variants, or to the moment after a named event. It can show once per visitor and wait a number of days between surveys. Schedule sets when it starts and ends; left empty, it shows once you start it and runs until you stop it. A survey can repeat every so many days: each round asks visitors again and its results read per round. Appearance sets an accent colour, which is the messenger’s when left empty. Languages adds translations, so a visitor whose browser asks for one reads the survey in it; removing a language sends its readers back to the default text.
Results
A survey is a Draft until Start, then Running until Stop. The Results tab counts responses and how many finished, and reads each question by its kind: a recommend score with its promoters, passives and detractors, an average for a rating, the share of each choice, and the written texts. Answers are also events, so they read beside the rest of your analytics. Archiving a survey takes it off the list and stops it showing; its answers stay in your events.
Permissions, API and agents
Creating, changing, starting or stopping a survey needs prodantix.messaging.send. REST serves surveys under /v1/projects/{projectId}/surveys, and agents work with them over MCP (prodantix.surveys.list, prodantix.surveys.get, prodantix.surveys.template, prodantix.surveys.create, prodantix.surveys.update, prodantix.surveys.duplicate, prodantix.surveys.translate, prodantix.surveys.start, prodantix.surveys.stop, prodantix.surveys.archive, prodantix.surveys.results, prodantix.surveys.response_counts).