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 Braze as a custom event on an existing user, with the score, the AI reading and the answers, ready for segments and Canvas journeys.
Braze runs your lifecycle messages. Send each answer to Braze as a custom event, and a Canvas can follow up on a low score, or a segment can hold everyone who asked for a feature.
The event is sent for your user ID, or for the email when there is no user ID, and only to people Braze already knows. Usertick never creates a Braze user from an answer.
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, and only to a user Braze already has. An answer with neither is skipped, and the workflow's activity says why.
One custom event for each answer, sent through the REST endpoint you chose.
Connecting sends nothing by itself. A workflow decides which answers become events.
In Usertick, open Settings, then Integrations, select Braze, choose your REST endpoint and paste an API key with only the users.track permission.
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.
Braze can't check a key without sending data, so the first answer sent confirms the connection.
Read the setup guideBraze 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 Braze has no user with that ID or email. 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.
Braze has no way to drop a duplicate event, so Usertick doesn't send an event again after a timeout. The workflow's activity notes that it may have arrived.
No. Usertick sends the custom event only, and leaves attributes and purchases as they are.
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.