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 Customer.io as an event on the person, with the score, the AI reading and the answers, so a campaign can follow up on what they said.
Customer.io sends messages based on what people do. Send each answer there as an event on the person, and a campaign can follow up on a low score or invite a promoter to share their story.
The event is sent for your user ID from Usertick.identify(), or for the email when there is no user ID. Answers with neither are skipped, and person attributes stay as they are.
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 your user ID from Usertick.identify(), or to the email when there is no user ID. An answer with neither is skipped, and the workflow's activity says why.
One event for each answer, sent to the region Usertick finds for your account.
Connecting sends nothing by itself. A workflow decides which answers become events.
In Usertick, open Settings, then Integrations, select Customer.io and paste your Site ID and Track API key. Usertick finds the account's region by itself.
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.
Customer.io comes with every plan, along with the workflows that send the event. Free runs 1 workflow per survey.
The answer had no user ID and no email, 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 the event only, so attributes such as unsubscribed stay as they are.
No. Each event carries an id, so Customer.io 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.