Name the event
Add Track an event to a workflow and keep the default name, Survey Submitted, or write your own with fields from the answer. Nothing is sent until the workflow is published.
Send each survey answer to the shopper's Klaviyo profile as a Survey Submitted event, with the score and the answers, so a flow can follow up on what they said.
Klaviyo knows each shopper by email. Send each answer to their profile as an event, and a flow can thank a promoter, ask for a review or reach out after a low score.
The event goes out for answers that come with an email, together with the user ID when your site identified the person. Klaviyo creates the profile when it has none.
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 Submitted, or write your own with fields from the answer. Nothing is sent until the workflow is published.
The event goes to the profile with the answer's email, and your user ID rides along when your site identified the person. An answer without an email is skipped, and the workflow's activity says why.
One event for each answer, on the profile with the answer's email.
Connecting sends nothing by itself. A workflow decides which answers become events.
In Usertick, open Settings, then Integrations, select Klaviyo and sign in. Usertick asks to write events and profiles, and to read your account name.
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.
Klaviyo comes with every plan, along with the workflows that send the event. Free runs 1 workflow per survey.
The answer had 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 and leaves consent, lists and profile properties as they are. A flow in Klaviyo decides what happens next.
No. Each event carries a unique_id, so Klaviyo drops a duplicate when a retry follows a timeout.
Usertick revokes its access in Klaviyo, and the workflow steps that used the connection stop sending until another one is assigned.
Start free, see what your customers mean, and get each answer to the person who can act on it.