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.
Segment integration
Survey answers as Segment events
Send each survey answer to Segment as a track event, with the score, the AI reading and every answer as properties, for the people you identify on your site.
Feedback in the same stream as your product data
Segment passes your events to every tool you connect to it. With the Usertick integration, each answer joins that stream as a track event for the person who gave it, so a warehouse, an analytics tool or a messaging tool downstream can use the score and the reading.
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 the rest of their 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.
- Plan
- Every plan, 1 workflow per survey on Free
- Connects with
- A write key and a region
- Sends
- One event for each answer a workflow picks
- Sent for
- People with a user ID from Usertick.identify()
How answers become Segment events
A workflow step names the event, and Usertick sends it for the person who answered.
Sent for the people you identify
The event goes to the user ID your site passed to Usertick.identify(), so it joins the rest of that person's events in Segment. An answer without a user ID is skipped, and the workflow's activity says why.
What Usertick sends to Segment
One track call for each answer, sent to the region you chose.
FieldWhat it holds
eventThe event name you set in the step, Survey Response unless you change it
userIdThe user ID your site passed to Usertick.identify()
timestampWhen the answer arrived
properties.survey_id, survey_nameThe survey the answer belongs to
properties.response_id, response_urlThe answer, and a link that opens it in Usertick
properties.nps_score, csat_score, ces_scoreThe scores the survey asked for
properties.ai_type, ai_theme, ai_urgency, ai_sentimentThe AI reading of the answer
properties.country, language, page_urlWhere the answer came from, with the page's query string removed
properties.answer_<question>One property for each answered question, named after its text
context.traits.emailThe person's email, when your identity settings allow it
messageIdAn ID Segment uses to drop a duplicate
Connect Segment in three steps
Connecting sends nothing by itself. A workflow decides which answers become events.
- 1
Connect Segment
In Usertick, open Settings, then Integrations, select Segment and paste a write key with its region, United States or Europe.
- 2
Add the step to a workflow
Add Track an event, keep or change the event name, and choose which answers the workflow sends.
- 3
Test it, then publish
A test run checks the connection and shows the request it would send, without writing an event. Then publish the workflow.
Segment accepts any write key without checking it, so the first answer sent confirms the connection.
Read the setup guideFrequently asked questions
Segment 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 track call for each answer, for the user ID your site already identifies.
No. Each call carries a messageId, so Segment 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.
More integrations
Google SheetsLog every response as a row that stays current as the AI reading, corrections and status change.
BigQueryLand each response in a BigQuery table with the same columns every time, ready to query.
Google AnalyticsSee survey completions in Google Analytics, sent through the script already on your page.
NotionAdd each response to a Notion database or a new page.
Listen better, act faster, and build what truly matters.
Start free, see what your customers mean, and get each answer to the person who can act on it.
- 150 responses a month on Free
- Every channel and AI analysis
- No card needed