Issue
When using the Segment Profiles destination to send track events from a data warehouse via Reverse ETL, you may notice the events show as successfully loaded in the sync status page but do not appear in the live debugger or the source event tables. This issue is commonly encountered when attempting to route events to a standard Segment source without the required Unify or Engage plans.
Product
Twilio Segment
Environment
Segment Console
Cause
The Segment Profiles destination is designed to update user records in the Engage/Unify profile database and is only supported for workspaces with Engage or Unify plans. Without these plans, events sent to the Profiles destination will not be routed to standard sources or appear in the debugger.
Resolution
To send warehouse events back into a standard Segment source (such as a JavaScript or HTTP API source), use the Segment Connections destination instead of the Profiles destination. Follow these steps to set this up:
- In the Segment Console, navigate to Connections > Destinations and select the Reverse ETL tab.
- Add a new Reverse ETL destination and choose Segment Connections.
- Enter the Write Key for the target source.
- Create a mapping using the Send Track action and map your warehouse columns to the standard Segment Track fields.
- Enable the sync to generate real-time track events in the target source's debugger.
Additional Information
- The Segment Profiles destination is only functional for workspaces with Engage or Unify enabled.
- For standard event routing, always use the Segment Connections destination with the appropriate Write Key.