Segment Profiles Destination
Destination Info
- Accepts Group, Identify and Track calls.
- Refer to it as Segment Profiles in the Integrations object
The Segment Profiles destination allows you to send your warehouse data back to Segment to create and update Profiles that can then be accessed through Profile API and activated within Twilio Engage.
Source compatibility
This destination supports connections from Reverse ETL warehouse sources, HubSpot, and Salesforce, and is not compatible with other sources.
To use this destination, you must have an active Segment Unify space. If you have not yet created a Segment Unify space, please follow the steps in the Unify Onboarding Guide.
- From the Segment web app, navigate to Reverse ETL > Destinations.
- Click Add Destination.
- Select the Segment Profiles destination, click Next, and select the warehouse source that will send data to the Segment Profiles destination. If you have not set up a warehouse source, follow the steps in the Reverse ETL documentation on Getting started. For information on how to set up HubSpot or Salesforce, see the HubSpot and Salesforce direct integration documentation.
- On the Settings tab, name your destination, select an endpoint region, and click Save Changes. It is recommended to configure and enable all mappings before enabling the Segment Profiles destination.
- On the Mappings tab, click Add Mapping. Select a data model and the API call type you want to map. Identify calls will create and update user profiles and Group calls will create and update account profiles. Fill in the fields on screen to create the desired mappings, and click Create Mapping to complete the configuration. Repeat this step to configure multiple mappings.
- Enable the configured mapping(s).
- On the Settings tab, click the Enable Destination toggle, and then click Save Changes to enable the Segment Profiles destination.
Build your own Mappings. Combine supported triggers with the following Segment Profiles-supported actions:
Mapping limits per destination
Send an identify call to Segment’s tracking API. This is used to tie your users to their actions and record traits about them.
Send Identify is a Cloud action. The default Trigger is type = "identify"
The Profile Space to use for creating a record. Note: This field shows list of internal sources associated with the Profile Space. Changes made to the Profile Space name in Settings will not reflect in this list unless the source associated with the Profile Space is renamed explicitly.
Optional
Unique identifier for the user in your database. A userId or an anonymousId is required.
Optional
A pseudo-unique substitute for a User ID, for cases when you don’t have an absolutely unique identifier. A userId or an anonymousId is required.
Optional
The group or account ID a user is associated with.
Optional
Free-form dictionary of traits that describe the user or group of users.
Optional
The timestamp of the event.
Send a group call to Segment’s tracking API. This is used to associate an individual user with a group
Send Group is a Cloud action. The default Trigger is type = "group"
The Profile Space to use for creating a record. Note: This field shows list of internal sources associated with the Profile Space. Changes made to the Profile Space name in Settings will not reflect in this list unless the source associated with the Profile Space is renamed explicitly.
Optional
Unique identifier for the user in your database. A userId or an anonymousId is required.
Optional
A pseudo-unique substitute for a User ID, for cases when you don’t have an absolutely unique identifier. A userId or an anonymousId is required.
The group or account ID a user is associated with.
Optional
Free-form dictionary of traits that describe the user or group of users.
Optional
The timestamp of the event.
Send an identify call to Segment’s tracking API. This is used to get user channel subscription data into Engage.
Send Subscriptions is a Cloud action. The default Trigger is type = "identify"
The Profile Space to use for creating a record. Note: This field shows list of internal sources associated with the Profile Space. Changes made to the Profile Space name in Settings will not reflect in this list unless the source associated with the Profile Space is renamed explicitly.
Optional
Unique identifier for the user in your database.
Optional
A pseudo-unique substitute for a User ID, for cases when you don’t have an absolutely unique identifier.
Optional
Email of the user
Optional
Global status of the email subscription. True is subscribed, false is unsubscribed, and did_not_subscribe is did_not_subscribe.
Optional
Group Subscription statuses are supported for the email channel. This object contains group names as keys and statuses as values. True is subscribed, false is unsubscribed, and did_not_subscribe is did_not_subscribe.
Optional
Phone number of the user
Optional
Global status of the SMS subscription. True is subscribed, false is unsubscribed, and did_not_subscribe is did_not_subscribe.
Optional
Global status of the WhatsApp subscription. True is subscribed, false is unsubscribed, and did_not_subscribe is did_not_subscribe.
Optional
Android Push Token of the user
Optional
Global status of the android push subscription. True is subscribed, false is unsubscribed, and did_not_subscribe is did_not_subscribe.
Optional
Ios Push Token of the user
Optional
Global status of the ios push subscription. True is subscribed, false is unsubscribed, and did_not_subscribe is did_not_subscribe.
Optional
Free-form dictionary of traits that describe the user or group of users.
Optional
The timestamp of the event.
Send a track call to Segment’s tracking API. This is used to record actions your users perform.
Send Track is a Cloud action.
The Profile Space to use for creating a record. Note: This field shows list of internal sources associated with the Profile Space. Changes made to the Profile Space name in Settings will not reflect in this list unless the source associated with the Profile Space is renamed explicitly.
Optional
Unique identifier for the user in your database. A userId or an anonymousId is required.
Optional
A pseudo-unique substitute for a User ID, for cases when you don’t have an absolutely unique identifier. A userId or an anonymousId is required.
Optional
The timestamp of the event.
Name of the action that a user has performed.
Optional
The group or account ID a user is associated with.
Optional
Free-form dictionary of properties that describe the event.
The Segment Profiles destination is not subject to API call or MTU costs. Any users or accounts created and updated by the Segment Profiles destination do not count towards your API call or MTU usage.
Make sure that the Endpoint Region setting matches the region of your workspace. If the region is correct and you don't see any profile changes, contact Segment.
Records sent to the Segment Profiles Destination are managed through a Unify Spaces' Profile Sources. Samples of these events may be reviewed in a Profile Source Debugger. For a more comprehensive analysis of the events received in Unify & Engage, consider using Profiles Sync connected to your Data Warehouse.