Customer.io
Send Encatch survey events to Customer.io - where to find the details in Customer.io and how to set up the connection
Overview
The Customer.io connector sends survey events to a Customer.io workspace as tracked events, so a survey answer can start a campaign or move someone into a segment.
| What it gets | Survey events as tracked events on the person |
| Events | Survey shown, started, submitted, partially submitted and dismissed |
| Anonymous respondents | Supported, with Include anonymous respondents on |
| User profile | Not updated yet: events only |
| Status | Available |
What You'll Need
Before you start, make sure you have:
- A Customer.io workspace — hosted in the United States or Europe
- A Private API key — created for Encatch (Step 1)
Step 1: Create a Private API key in Customer.io
- In Customer.io, open Settings and go to API credentials.
- Click Create API key and choose Private. Give it a name you'll recognise, for example
Encatch. - Copy the key. It starts with
sk_. Keep it server-side only. - Note where the workspace is hosted: United States or Europe. The address of the app does not always tell you; if you are not sure, Test connection will: a key sent to the wrong region is refused.
Step 2: Add the connection in Encatch
- In Encatch, open Data sync → Survey events and click Add connection.
- Choose Customer.io.
- Enter a Name you'll recognise in the list and in Logs.
- Fill in the Customer.io settings:
| Field | What to enter |
|---|---|
| Region | United States (default) or Europe. |
| Private API key | The Private API key (sk_…). |
- Press Test connection. Encatch shows what Customer.io answered.
Encatch keeps the keys encrypted and never shows them again. To change one later, press Replace.
Step 3: Choose what to send
- Under Surveys, choose All surveys or Only these surveys.
- Under What is sent, tick the events to send. A new connection starts with Survey shown, started, submitted and dismissed ticked. Survey partially submitted is off until you tick it.
- Rename an event if you want another name in Customer.io. The defaults are
encatch_survey_shown,encatch_survey_started,encatch_survey_submitted,encatch_survey_partialandencatch_survey_dismissed. - To also send responses of people who are not signed in, turn on Include anonymous respondents.
- Open Advanced options to choose how users are identified, whether answers are sent and the rate limit.
Every option is explained in Connection settings.
Step 4: Save and start sending
Click Save. Saving does not start sending: press Start sending when you are ready. From then on events go out as they happen, and every delivery is listed in Logs.
Check it in Customer.io
Test connection sends one event named encatch_test_event. In Customer.io, open a person and look at their Activity: survey events appear there under the names you chose. Events of anonymous respondents are listed with anonymous activity.
Good to know
- New people. Customer.io adds a person for any user ID it does not have yet; people count toward your Customer.io profiles.
- Events only. Customer.io gets the events; Encatch does not set person attributes in Customer.io yet, so Update the user's profile is shown off.
- Rate limit. Customer.io's Track API has no fixed limit (its guideline is 3,000 requests per 3 seconds), so a limit is rarely needed.
Troubleshooting
| What you see | What it means | What to do |
|---|---|---|
| Key refused | The key is wrong, or the region does not match the workspace | Switch Region and test again; if it still fails, create a new Private API key |
Was this page helpful?
