Twilio Segment
Send Encatch survey events to Twilio Segment - where to find the details in Twilio Segment and how to set up the connection
Overview
The Twilio Segment connector sends survey events to a Segment source. From there Segment passes them on to every destination you connect to that source, so one connection reaches your whole stack.
| What it gets | Survey events on a source, passed on to every tool connected to it |
| Events | Survey shown, started, submitted, partially submitted and dismissed |
| Anonymous respondents | Supported, with Include anonymous respondents on |
| User profile | Updated with the user's traits when Update the user's profile is on |
| Status | Available |
What You'll Need
Before you start, make sure you have:
- A Twilio Segment workspace — with permission to add a source
- An HTTP API source — made for Encatch (Step 1)
- The source's Write Key
Step 1: Create a source and copy its Write Key in Segment
- In Segment, open Connections → Sources and click Add Source.
- Search for HTTP API, select it and click Add Source. Give it a name you'll recognise, for example
Encatch. - Open the source's Settings → API Keys and copy the Write Key.
- Note your region. Choose Europe only if the workspace was created in Segment's EU region.
Check the Debugger. Segment answers success even for a wrong Write Key, so Test connection cannot tell. The source's Debugger is the proof that events arrive.
Step 2: Add the connection in Encatch
- In Encatch, open Data sync → Survey events and click Add connection.
- Choose Twilio Segment.
- Enter a Name you'll recognise in the list and in Logs.
- Fill in the Twilio Segment settings:
| Field | What to enter |
|---|---|
| Region | United States (default) or Europe. |
| Source write key | The Write Key of the HTTP API source. |
- Press Test connection. Encatch shows what Twilio Segment 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 Twilio Segment. 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 Twilio Segment
Open the source's Debugger in Segment. Test connection shows there as a TRACK encatch_test_event call. Survey events show as TRACK calls under the names you chose and, with Update the user's profile on, an IDENTIFY call carries the user's traits. Then connect the destinations that should get them.
Good to know
- Anonymous respondents arrive with an anonymous ID and no user ID.
- Rate limit. Segment takes 1,000 requests a second per workspace, so a limit is rarely needed.
- Events count toward your Segment plan.
Troubleshooting
| What you see | What it means | What to do |
|---|---|---|
| Delivered, but nothing in the Debugger | The Write Key is wrong, or the region does not match the workspace | Copy the Write Key again; check Region |
Was this page helpful?
