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 Iterable as a custom event with the score, the AI reading and every answer, so a journey can react to what people told you.
Iterable runs journeys across email, push and SMS. Send each answer to Iterable as a custom event, and a journey can react to the score or to what the AI read in the answer.
The event carries your user ID and the email when Usertick has them. Every answer goes in one answers list, so a survey with many questions never adds a field for each one.
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 carries your user ID from Usertick.identify() and the email when Usertick has them. An answer with neither is skipped, and so is one Iterable doesn't know.
One custom event for each answer, sent to the region Usertick finds for your project.
Connecting sends nothing by itself. A workflow decides which answers become events.
In Usertick, open Settings, then Integrations, select Iterable and paste a server-side API key. Usertick finds the project'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.
Iterable 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, or Iterable has no person with them. The workflow's activity lists each skipped run with its reason.
Yes, in one answers list with each question and its answer, so a long survey adds a single field. Files, screenshots, signatures and contact details are never sent.
No. Usertick sends the custom event only. A journey in Iterable decides what happens next.
No. Each event carries an id, so Iterable 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.