Data sync
Send survey events from Encatch to your analytics, engagement, CDP, CRM, warehouse and automation tools as they happen
Data sync is in beta. It is being switched on account by account. If you don't see Data sync in your project menu, contact support and we'll turn it on for you.
Overview
Data sync connects Encatch to the tools your team already works in. Today it covers Survey events: every time a survey is shown, started, submitted or dismissed, Encatch can send that as an event, a row or a record to the tool you choose. No code, no export files.
You set it up once per tool, from the dashboard:
- Pick a tool — analytics, engagement, CDP, CRM, warehouse, spreadsheet or automation.
- Paste its keys — each connector page tells you where to find them in the tool.
- Choose what to send — which surveys, which events, with or without the answers.
- Test, save and start sending — every delivery is listed in Logs.
Data sync or Destinations?
Both send feedback out of Encatch. They are built for different jobs.
| Destinations | Data sync | |
|---|---|---|
| Built for | Telling people about a response: a Slack message, an email, a Jira issue | Feeding your data tools: events, profiles, rows and records |
| Scope | One form per destination | All surveys, or the ones you pick, per connection |
| What is sent | A message you write with a template | A structured event with the user, the form and the answers |
| Events | Survey submitted | Survey shown, started, submitted, partially submitted and dismissed |
| Controls | Custom and AI filters | User identity, rate limit, retries, delivery logs, send again |
Use Destinations when a person should see the response. Use Data sync when a tool should store it.
Supported tools
Tools marked Available were set up and tested on a live account of the tool. Tools marked Beta are built from the tool's public API documentation and are waiting for their first confirmation on a live account, so their guides stay high level.
Analytics
| Tool | What it gets | Status |
|---|---|---|
| Amplitude | Survey events as tracked events | Available |
| Mixpanel | Survey events as tracked events | Available |
| PostHog | Survey events as captured events | Available |
| Heap | Survey events as server-side events | Available |
Customer data platforms
| Tool | What it gets | Status |
|---|---|---|
| Twilio Segment | Survey events on a source, passed on to every tool connected to it | Available |
| RudderStack | Survey events on a source, passed on to every destination connected to it | Available |
Engagement and marketing
| Tool | What it gets | Status |
|---|---|---|
| Customer.io | Survey events as tracked events | Available |
| Klaviyo | Survey events as metrics on the profile | Available |
| Vero | Survey events as tracked events on the user | Available |
| Braze | Survey events as custom events | Beta |
| Iterable | Survey events as custom events | Beta |
| MoEngage | Survey events as user events | Beta |
| Batch | Survey events on profiles | Beta |
| Userlist | Survey events as user events | Beta |
CRM
| Tool | What it gets | Status |
|---|---|---|
| HubSpot | A record created or updated from each response | Available |
| Salesforce | A record created or updated from each response | Available |
Warehouse and spreadsheet
| Tool | What it gets | Status |
|---|---|---|
| Google BigQuery | One row per response in a table | Available |
| Google Sheets | One row per response in a spreadsheet | Available |
Automation
| Tool | What it gets | Status |
|---|---|---|
| Zapier | Each response starts a Zap | Available |
| n8n | Each response starts a workflow | Available |
| Make | Each response starts a scenario | Available |
| Power Automate | Each response starts a flow | Beta |
| Webhook | Each response as JSON to your own HTTPS endpoint | Beta |
Audience and feedback analysis
| Tool | What it gets | Status |
|---|---|---|
| Permutive | Survey events on the user | Beta |
| Enterpret | Each response as a survey record | Beta |
How a connection works
Open Data sync — In your project, open Data sync from the menu. The Survey events tab lists your connections.
Add a connection — Click Add connection, pick the tool and paste its keys. The connector page of each tool shows where to find them.
Choose what to send — Pick the surveys and tick the events. Advanced options decide what each event carries. See Connection settings.
Test connection — Sends one sample to the tool with the settings in the form, saved or not.
Save, then Start sending — Saving does not start sending. Press Start sending when you are ready; Pause stops it at once.
Watch Logs — Every delivery, its outcome and the tool's answer. See Logs.
Good to know
- Only new events are sent. A connection sends what happens after you start it. Past responses are not sent.
- Keys stay private. Encatch keeps keys encrypted and never shows them again. The form shows a key as saved, with Replace to paste a new one.
- Up to 20 connections per project. You can connect the same tool more than once, for example one connection per region or per set of surveys.
- Your tool's own limits still apply. Events count toward your plan in the tool (events, profiles, API calls). Each connector page lists what to watch.
Next steps
- Survey events — the five events, who they are sent for and what they carry
- Connection settings — every field of the connection form
- Logs — outcomes, retries and sending again
Was this page helpful?
