Name the event
Add Track an event to a workflow and keep the default name, Survey Response, or write your own with fields from the answer. Nothing is sent until the workflow is published.
Send each survey answer to Mixpanel as an event with the score, the AI reading and every answer as properties, ready to break down a report by what people said.
Mixpanel shows what people do in your product. Send each answer there as an event with every answer as a property, and you can break a report down by score or see what detractors did before they answered.
The event goes out only for a person your site identified with Usertick.identify() and a user ID, so it lands on the same user as their other events. Answers from visitors you never identified are skipped.
A workflow sends the event. It can send every answer to a survey or only the ones its conditions pick, such as detractors or answers the AI read as a bug, and it can wait until the AI has read the answer.
A workflow step names the event, and Usertick sends it for the person who answered.
Add Track an event to a workflow and keep the default name, Survey Response, or write your own with fields from the answer. Nothing is sent until the workflow is published.
The event goes to the user ID your site passed to Usertick.identify(), so it joins the rest of that person's events in Mixpanel. An answer without a user ID is skipped, and the workflow's activity says why.
One event for each answer, imported into the region you chose.
Connecting sends nothing by itself. A workflow decides which answers become events.
In Usertick, open Settings, then Integrations, select Mixpanel and paste the project token with its region, United States, Europe or India. Usertick never needs the API secret.
Add Track an event, keep or change the event name, and choose which answers the workflow sends.
A test run checks the connection and shows the request it would send, without writing an event. Then publish the workflow.
Mixpanel comes with every plan, along with the workflows that send the event. Free runs 1 workflow per survey.
The answer had no user ID from Usertick.identify(), so the step skipped it. The workflow's activity lists each skipped run with its reason.
Yes. Each answered question becomes its own property, named after the question's text, such as answer_what_could_we_improve. Files, screenshots, signatures and contact details are never sent.
No. Usertick sends one event for each answer and leaves the person's profile as it is.
No. Each event carries an $insert_id, so Mixpanel drops a duplicate when a retry follows a timeout.
At the moment the answer arrived, even when the workflow waited for the AI reading or a retry sent it later.
Start free, see what your customers mean, and get each answer to the person who can act on it.