# Segment Profiles Destination ## Destination Info * Accepts [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Segment Profiles** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) The Segment Profiles destination allows you to send your warehouse data back to Segment to create and update [Profiles](/docs/segment/unify/) that can then be accessed through [Profile API](/docs/segment/unify/profile-api) and activated within [Twilio Engage](/docs/segment/engage). > \[!TIP] > > This destination supports connections from Reverse ETL warehouse sources, [HubSpot](/docs/segment/connections/destinations/catalog/actions-segment-profiles/hubspot-source), and [Salesforce](/docs/segment/connections/destinations/catalog/actions-segment-profiles/salesforce-source), and is not compatible with other sources. ## Getting started ### Create a Profile space 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](/docs/segment/unify/quickstart). ### Connect and configure the Segment Profiles destination 1. From the Segment web app, navigate to **Reverse ETL > Destinations**. 2. Click **Add Destination**. 3. 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](/docs/segment/connections/reverse-etl#getting-started). For information on how to set up HubSpot or Salesforce, see the [HubSpot](/docs/segment/connections/destinations/catalog/actions-segment-profiles/hubspot-source) and [Salesforce](/docs/segment/connections/destinations/catalog/actions-segment-profiles/salesforce-source) direct integration documentation. 4. 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. 5. 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. 6. Enable the configured mapping(s). 7. On the **Settings** tab, click the **Enable Destination** toggle, and then click **Save Changes** to enable the Segment Profiles destination. ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Segment Profiles-supported actions: > \[!NOTE] > > Individual destination instances have support a maximum of 50 mappings. * [Send Identify](#send-identify) * [Send Group](#send-group) * [Send Subscriptions](#send-subscriptions) * [Send Track](#send-track) ### Send Identify 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"` | Field | Description | Required | Type | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | | Profile Space | 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.\* | Yes | STRING | | User ID | Unique identifier for the user in your database. A userId or an anonymousId is required. | No | STRING | | Anonymous ID | 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. | No | STRING | | Group ID | The group or account ID a user is associated with. | No | STRING | | Traits | Free-form dictionary of traits that describe the user or group of users. | No | OBJECT | | Timestamp | The timestamp of the event. | No | DATETIME | ### Send Group 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"` | Field | Description | Required | Type | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | | Profile Space | 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.\* | Yes | STRING | | User ID | Unique identifier for the user in your database. A userId or an anonymousId is required. | No | STRING | | Anonymous ID | 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. | No | STRING | | Group ID | The group or account ID a user is associated with. | Yes | STRING | | Traits | Free-form dictionary of traits that describe the user or group of users. | No | OBJECT | | Timestamp | The timestamp of the event. | No | DATETIME | ### Send Subscriptions 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"` | Field | Description | Required | Type | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | | Profile Space | 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.\* | Yes | STRING | | User ID | Unique identifier for the user in your database. | No | STRING | | Anonymous ID | A pseudo-unique substitute for a User ID, for cases when you don’t have an absolutely unique identifier. | No | STRING | | Email | Email of the user | No | STRING | | Email Subscription Status | Global status of the email subscription. True is subscribed, false is unsubscribed, and did\_not\_subscribe is did\_not\_subscribe. | No | STRING | | Email Subscription Groups | 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. | No | OBJECT | | Phone | Phone number of the user | No | STRING | | SMS Subscription Status | Global status of the SMS subscription. True is subscribed, false is unsubscribed, and did\_not\_subscribe is did\_not\_subscribe. | No | STRING | | WhatsApp Subscription Status | Global status of the WhatsApp subscription. True is subscribed, false is unsubscribed, and did\_not\_subscribe is did\_not\_subscribe. | No | STRING | | Android Push Token | Android Push Token of the user | No | STRING | | Android Push Subscription Status | Global status of the android push subscription. True is subscribed, false is unsubscribed, and did\_not\_subscribe is did\_not\_subscribe. | No | STRING | | Ios Push Token | Ios Push Token of the user | No | STRING | | Ios Push Subscription Status | Global status of the ios push subscription. True is subscribed, false is unsubscribed, and did\_not\_subscribe is did\_not\_subscribe. | No | STRING | | Traits | Free-form dictionary of traits that describe the user or group of users. | No | OBJECT | | Timestamp | The timestamp of the event. | No | DATETIME | ### Send Track Send a track call to Segment’s tracking API. This is used to record actions your users perform. Send Track is a **Cloud** action. | Field | Description | Required | Type | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | | Profile Space | 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.\* | Yes | STRING | | User ID | Unique identifier for the user in your database. A userId or an anonymousId is required. | No | STRING | | Anonymous ID | 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. | No | STRING | | Timestamp | The timestamp of the event. | No | DATETIME | | Event Name | Name of the action that a user has performed. | Yes | STRING | | Group ID | The group or account ID a user is associated with. | No | STRING | | Properties | Free-form dictionary of properties that describe the event. | No | OBJECT | ## FAQ & Troubleshooting ### API Calls and MTUs 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. ### Successful syncs but no changes on profiles 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](https://segment.com/help/contact/). ### Can I view samples of events received in Engage by the Segment Profiles Destination? 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](/docs/segment/unify/debugger/). For a more comprehensive analysis of the events received in Unify & Engage, consider using [Profiles Sync](/docs/segment/unify/profiles-sync/overview/) connected to your Data Warehouse.