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 Amplitude as an event with the score, the survey and the AI reading, so you can chart feedback beside what people do in your product.
Amplitude shows what people do in your product. Send each answer there as an event, and you can compare the people who gave a low score with the rest, or watch the score move after a release.
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. It carries the survey, the scores and the AI reading, and leaves the written answers in Usertick.
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 Amplitude. An answer without a user ID is skipped, and the workflow's activity says why.
One event for each answer, sent to the region you chose.
Connecting sends nothing by itself. A workflow decides which answers become events.
In Usertick, open Settings, then Integrations, select Amplitude and paste the project's API key with its region. Usertick doesn't need the secret key.
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.
Amplitude 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.
No. The event carries the survey, the scores, the AI reading and where the answer came from. The written answers stay in Usertick, one click away through response_url.
No. Usertick sends one event for each answer and leaves the user's properties as they are.
No. Each event carries an insert_id, so Amplitude 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.