Overview

Twilio Segment is a customer data platform used by organizations to collect, unify, and route customer event data to analytics, marketing, and data warehousing tools.

Common uses for the Alchemer Twilio Segment integration

• Send workflow-triggered events into Segment for downstream activation
• Identify users in Segment using workflow data
• Enrich Segment event streams with survey or workflow response data
• Automate event tracking without manual data exports
• Keep Segment customer profiles synchronized with Alchemer workflow outcomes

What can the Alchemer Twilio Segment integration do?

• Send event

You will need

• Twilio Segment Write Key. More details in the authentication how-to guide.
• An Alchemer plan that includes integrations and the Integration Manager permission enabled.
  • Contact us if you are unsure if your plan includes integrations.

Setup Alchemer Twilio Segment integration in workflow

Twilio Segment | Send Event

You will need:

• Twilio Segment Write Key. More details in the authentication how-to guide.
• Workflow fields containing the data you want to send as event properties

Configure the action

1. Open your workflow in Workflow Builder.
2. On the right side, drag and drop the Twilio connection where you want the action to trigger.
3. In the connection box, click the pencil icon in the top-right corner.
4. Select Twilio Segment | Send Event.
5. Twilio Segment | Authentication: Select an existing authentication or create a new authentication.
6. Twilio Segment | Map event fields: Enter a name for the event. Map a workflow field to userId, or leave it blank — an anonymous ID will be generated automatically.
7. Twilio Segment | Map optional fields: Map any additional fields you want to include with the event. All fields in this step are optional. Three mappers are available — properties, integrations, and context — each mapping independently.
   • In the left column, type and enter the key for the field you want to set.
   • In the right column, select the workflow field that contains the value for that key.
8. Save the action.

Status codes

• 200: Event was successfully sent to Twilio Segment
• 400: The external integration returned an error

Testing and Troubleshooting

Testing and Validation

How to test

• Trigger the workflow and monitor individual runs in the Monitor tab.
  • Click on individual workflow runs to see metadata outputs.
• Confirm the expected event appears in your Twilio Segment source debugger.
• Use metadata values returned to verify success or help debug issues.

How to verify results

• Check your Segment source debugger to confirm the event was received.
• Ensure event name, userId, and mapped property values match expectations.

Monitoring Integration Activity

Where to find logs

• Go to Results → Monitor.
• Select the integration step you want to inspect.

What logs display

• Input/Output

Troubleshooting

Authentication issues

• Incorrect or expired Write Key
• Write Key does not have access to the intended Segment source

Mapping errors

• Missing event name
• Key entered in left column does not match expected Segment field name
• Workflow field mapped in right column contains no value

API errors

• Segment validation failures
• Endpoint or runtime errors

FAQs