Merge pull request #7769 from segmentio/unify-direct-integrations

Moving the pages for the direct Segment Profiles integrations

Author: forstisabella

src/connections/sources/catalog/cloud-apps/hubspot-profiles/index.md renamed to src/connections/destinations/catalog/actions-segment-profiles/hubspot-source.md

@@ -1,6 +1,7 @@
 ---
 title: Connect HubSpot to Segment Profiles
-plan: unify
+redirect_from: 
+   - '/connections/sources/catalog/cloud-apps/hubspot-profiles/'
 ---
 
 This guide explains how to set up HubSpot as a source and connect it to Segment Profiles. 

src/connections/destinations/catalog/actions-segment-profiles/index.md

@@ -4,22 +4,22 @@ hide-boilerplate: true
 hide-dossier: false
 id: 639c2dbb1309fdcad13951b6
 ---
-The Segment Profiles destination allows you to send your warehouse data back to Segment to create and update [Profiles](/docs/profiles/) that can then be accessed through [Profile API](/docs/profiles/profile-api/) and activated within [Twilio Engage](/docs/engage). 
+The Segment Profiles destination allows you to send your warehouse data back to Segment to create and update [Profiles](/docs/unify/) that can then be accessed through [Profile API](/docs/profiles/profile-api/) and activated within [Twilio Engage](/docs/engage). 
 
 > success "Source compatibility"
-> This destination supports connections from Reverse ETL warehouse sources, and is not compatible with other source types.
+> This destination supports connections from Reverse ETL warehouse sources, [HubSpot](/docs/connections/destinations/catalog/actions-segment-profiles/hubspot-source), and [Salesforce](/docs/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 Profile space. If you have not yet created a Segment Profile space, please follow the steps in the [Profiles Onboarding Guide](/docs/profiles/quickstart/).
+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/profiles/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/reverse-etl/#getting-started).
+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/reverse-etl/#getting-started). For information on how to set up HubSpot or Salesforce, see the [HubSpot](/docs/connections/destinations/catalog/actions-segment-profiles/hubspot-source) and [Salesforce](/docs/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).
@@ -30,11 +30,11 @@ To use this destination, you must have an active Segment Profile space. If you h
 ## 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 will not count towards your API call or MTU usage.
+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.
 
-### Succesful syncs but no changes on profiles
+### 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/){:target="_blank"}.
 
 ### 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](https://segment.com/docs/unify/debugger/). For a more comprehensive analysis of the events received in Unify & Engage, consider utilizing [Profiles Sync](https://segment.com/docs/unify/profiles-sync/overview/) connected to your Data Warehouse.
+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/unify/debugger/). For a more comprehensive analysis of the events received in Unify & Engage, consider using [Profiles Sync](/docs/unify/profiles-sync/overview/) connected to your Data Warehouse.

src/connections/sources/catalog/cloud-apps/salesforce-unify/index.md renamed to src/connections/destinations/catalog/actions-segment-profiles/salesforce-source.md

@@ -1,8 +1,8 @@
 ---
 title: Salesforce Unify Direct Integration Guide
-plan: unify
 redirect_from:
   - '/unify/salesforce-unify'
+  - '/connections/sources/catalog/cloud-apps/salesforce-unify/'
 ---
 
 This guide outlines the process for setting up Salesforce as a data source with Segment Profiles. 
@@ -60,7 +60,7 @@ Next, add a Segment Profiles destination:
 4. Test your mapping with real data from Salesforce.
 5. Save your mapping configuration.
 
-![A screenshot of the "Select Mappings" interface in Segment, showing fields for mapping event data from a source to a destination. The interface includes options for selecting objects, customizing objects, and mapping fields such as Profile Space, User ID, Anonymous ID, Group ID, Traits, and Timestamp.](../../../images/select_mappings.png)
+![A screenshot of the "Select Mappings" interface in Segment, showing fields for mapping event data from a source to a destination. The interface includes options for selecting objects, customizing objects, and mapping fields such as Profile Space, User ID, Anonymous ID, Group ID, Traits, and Timestamp.](/docs/connections/sources/images/select_mappings.png)
 
 ### 5. Enable the destination mapping and Salesforce source
 

src/connections/sources/catalog/cloud-apps/b222test/index.md

@@ -8,6 +8,9 @@ id: 2baks93o
 
 Are you trying to set up HubSpot as a destination to receive data from Segment? Go here [HubSpot Destination](/docs/connections/destinations/catalog/hubspot/).
 
+> success ""
+> Want to connect your HubSpot source directly to the Segment Profiles destination? See the [Connect HubSpot to Segment Profiles](/docs/connections/destinations/catalog/actions-segment-profiles/hubspot-source/) documentation. 
+
 ## Getting Started
 
 1. From your workspace's `/sources` page, click `add source`.

src/connections/sources/catalog/cloud-apps/hubspot/index.md

@@ -8,6 +8,9 @@ id: 2baks93n
 
 Take your company's analysis to the next level by **adding Salesforce as a Source to Segment.** Segment automatically collects objects like `Accounts`, `Campaigns`, and `Tasks` and loads them into your data warehouse. 
 
+> success ""
+> Want to connect your Salesforce source directly to the Segment Profiles destination? See the [Salesforce Unify Direct Integration Guide](/docs/connections/destinations/catalog/actions-segment-profiles/salesforce-source/) documentation.
+
 > info "Salesforce version upgrade to 58.0"
 > On March 25, 2024, the Salesforce source upgraded to use Salesforce's API version 58.0. See the [version upgrade changes](#version-upgrade-changes) to learn more.