Survey events
The five survey events Encatch can send, who they are sent for and what each one carries
Overview
A survey event is one thing that happened to one survey for one person: it was shown, started, submitted, left unfinished or dismissed. Each Data sync connection chooses which of these events to send and to which tool.
This page explains the events themselves. For the fields of the connection form, see Connection settings.
The five events
| Event | Default name | When it is sent |
|---|---|---|
| Survey shown | encatch_survey_shown | A survey was shown to the user. For shareable links that identify the contact (for example email surveys): when the link opens a new response. This may include automated link checks by email security scanners. |
| Survey started | encatch_survey_started | The user answered the first question. For shareable links that identify the contact: at their first saved answer, or at the submit when partial saves are off. |
| Survey submitted | encatch_survey_submitted | The user finished the survey. On a form that lets people edit their response, each edit they submit is sent again under the same response ID. |
| Survey partially submitted | encatch_survey_partial | A response left unfinished, with its answers so far. Sent once, when Encatch closes it: after the form's partial timer or edit window; for shareable links that identify the contact, when they come back or after 7 days. A partial submitted through the Admin API is sent at once. |
| Survey dismissed | encatch_survey_dismissed | The user closed the survey without finishing. In-app only: a shareable link has no close button. |
You can rename each event per connection. The name you type is the name the tool stores.
Survey partially submitted is off by default. Tick it only if you want unfinished responses in the tool. A response is sent as partial or as submitted, never both.
Who events are sent for
| Event | Identified users | Anonymous respondents |
|---|---|---|
| Survey shown, started | Yes: users your app identifies, and shareable links that identify the contact | No |
| Survey dismissed | Yes: users your app identifies | No |
| Survey submitted, partially submitted | Yes | Only with Include anonymous respondents on, where the tool supports it |
An identified user is one your app names when it identifies the user in the SDK, or a contact a shareable link identifies. An anonymous respondent is not signed in. With Include anonymous respondents on, their responses go out under the device ID the SDK gave them.
The connector page of each tool says whether it takes anonymous respondents.
Two kinds of tools
Tools take survey events in one of two ways.
Event tools
Analytics, engagement, CDP and audience tools take all five events as events on the user: Amplitude, Mixpanel, PostHog, Heap, Twilio Segment, RudderStack, Customer.io, Klaviyo, Vero, Braze, Iterable, MoEngage, Batch, Userlist and Permutive.
Every event carries these properties:
| Property | Meaning |
|---|---|
encatch_event | Which of the five events this is, for example encatch_survey_submitted. It stays the same when you rename the event. |
response_id | The response the event belongs to. Shown, started, submitted and dismissed events of one response share it. |
survey_id | The form's ID. You can also send the form's name and slug, and rename all three (Form details). |
answers | With Send answers on, on Survey submitted and partially submitted: one entry per question, named by the question's slug, ID or title (Answer keys). |
A few tools shape this differently, for example Vero takes each answer as its own text property. The connector page says so where it applies.
Response tools
CRM, warehouse, spreadsheet, automation and feedback analysis tools take each response as one record: HubSpot, Salesforce, Google BigQuery, Google Sheets, Zapier, n8n, Make, Power Automate, Webhook and Enterpret.
They get Survey submitted always, and Survey partially submitted when you tick it. Shown, started and dismissed are not sent to them. The answers always go with the response.
Edits, partial responses and repeats
- Edited responses. On a form that lets people edit their response, each edit they submit is sent again as Survey submitted under the same
response_id. In a table or sheet, that is one more row. - Partial responses. Sent once, when Encatch closes the response. If the person comes back and finishes in time, only Survey submitted is sent.
- Retries. When a tool is down, Encatch tries again. A retry can reach a tool twice, so use the response ID (or the event ID the automation tools get) to skip repeats where that matters.
- Admin API responses. Responses your servers submit with the Admin API are sent as Survey submitted too. You can leave them out per connection.
Next steps
- Connection settings — choose surveys, events and what each event carries
- Logs — see what was sent and what the tool answered
Was this page helpful?
