-
Notifications
You must be signed in to change notification settings - Fork 393
Salesforce Unify Direct Integration GA [DOC-960] #6982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
bb6a062
add new page and structure
pwseg 98f11af
add screenshot to placate people [netlify-build]
pwseg 00999d7
Update src/unify/salesforce-unify.md
pwseg d4b907c
Update src/unify/salesforce-unify.md
pwseg 96e7ffa
Update src/unify/salesforce-unify.md
pwseg 696676a
clarify best practices
pwseg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,86 @@ | ||
--- | ||
title: Salesforce Unify Direct Integration Guide | ||
plan: unify | ||
--- | ||
|
||
This guide outlines the process for setting up Salesforce as a data source with Segment Profiles. | ||
|
||
Once configured, this integration lets you send Salesforce data directly to Segment Profiles, eliminating the need for a data warehouse and enabling faster data synchronization and profile enrichment. | ||
|
||
## Prerequisites | ||
|
||
Before you begin, make sure that you have the following: | ||
|
||
- a Segment workspace with [Unify](/docs/unify/) enabled and [Identity Resolution](/docs/unify/identity-resolution/) set up | ||
- Administrator access to your Salesforce account | ||
- Salesforce Unify Direct Integration enabled for your workspace. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if you don't yet have the integration enabled. | ||
|
||
## Integration steps | ||
|
||
Follow the steps in this section to set up the Salesforce Unify Direct Integration. | ||
|
||
### 1. Add Salesforce as a source | ||
|
||
Start by setting up Salesforce as a source: | ||
|
||
1. From your Segment workspace, go to **Connections > Catalog > Cloud App Objects**. | ||
2. Select Salesforce as your source. | ||
3. Name your Salesforce source and authenticate with your Salesforce credentials. | ||
4. Once connected, use Selective Sync to choose the Salesforce collections and columns you want to sync. | ||
|
||
After successful authentication, Segment adds the source but disables it by default. You'll enable it later. | ||
|
||
### 2. Add a Segment Profiles destination | ||
|
||
Next, add a Segment Profiles destination: | ||
|
||
1. From the overview tab of your new Salesforce source, click **Add destination**. | ||
2. From the catalog destination page, click **Segment Profiles**, then click **Add destination**. | ||
3. Name your destination, then click **Create**. | ||
|
||
### 3. Create a data model | ||
|
||
1. In the Salesforce source you created, navigate to the Models tab and click **Create Model**. | ||
3. Select the fields you want to map to the Segment Profiles destination. | ||
4. Preview and validate the schema with real-time Salesforce data. | ||
5. Name your model and save it. | ||
|
||
### 4. Configure mapping | ||
|
||
1. In the Salesforce source, navigate to **Models > Add mapping**. | ||
2. Segment returns you to the Segment Profiles Destination. Click **Add mapping**. | ||
2. Select your data model and map your selected Salesforce data to fields in Segment Profiles (typically "Identify" for profile updates). | ||
- Select the Profile space you want to update. | ||
- Map Salesforce fields to Segment Profile fields. **You must map either a User ID or Anonymous ID field.** | ||
4. Test your mapping with real data from Salesforce. | ||
5. Save your mapping configuration. | ||
|
||
 | ||
|
||
### 5. Enable the destination mapping and Salesforce source | ||
|
||
Finish by enabling the destination mappings and the source: | ||
|
||
1. From the overview tab of the Segment Profiles destination you created, toggle the **Mapping Status** switch to **Enabled**. | ||
2. Return to your Salesforce source and navigate to **Settings > Basic settings.** | ||
2. Toggle the **Enable source** switch to on. | ||
|
||
Data now begins syncing between Salesforce and Segment. | ||
|
||
## Data synchronization | ||
|
||
After you've connected Salesforce and the Segment Profiles destination, the integration begins syncing data: | ||
|
||
- New or updated records in Salesforce get sent to Segment Profiles based on your mapping configuration. | ||
- The initial sync includes historical data within the range specified in your Selective Sync settings. | ||
- Further syncs take place at regular intervals (typically hourly). | ||
|
||
## Best practices | ||
|
||
Keep the following in mind as you work with the Salesforce Unify Direct Integration: | ||
|
||
- Start with a subset of data to test your integration before expanding to all Salesforce objects. | ||
- Regularly review your mapping to ensure it reflects any changes in your Salesforce schema or Segment Profile needs. | ||
- Monitor both your Salesforce source and Segment Profiles destination for errors and data discrepancies. | ||
|
||
The Salesforce Unify Direct Integration supports mapping from a single Salesforce collection per data model. For complex use cases requiring data from multiple collections, you may need to create multiple data models and mappings. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥