-
Notifications
You must be signed in to change notification settings - Fork 367
Add "RETL Scripts For Importing Salesforce Objects Into Unified Profiles" documentation #6166
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
Conversation
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
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
cherylj
reviewed
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
cmastr
reviewed
Mar 4, 2024
cmastr
reviewed
Mar 4, 2024
cmastr
reviewed
Mar 4, 2024
cmastr
reviewed
Mar 4, 2024
cmastr
approved these changes
Mar 4, 2024
cherylj
approved these changes
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
title: RETL Scripts For Importing Salesforce Objects Into Unified Profiles | ||
hidden: true | ||
--- | ||
Unified Profiles users can convert Salesforce objects with US phone number patterns (typically (555) 231-7654) into Segment Unify profiles with E.164 phone number formats (+15552317654) to support Unified Profiles lookup. |
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.
Suggested change
Unified Profiles users can convert Salesforce objects with US phone number patterns (typically (555) 231-7654) into Segment Unify profiles with E.164 phone number formats (+15552317654) to support Unified Profiles lookup. | |
You can use the following queries to convert Salesforce objects with US phone number patterns (typically (555) 231-7654) into Segment Unify profiles with E.164 phone number formats (+15552317654). When you update the number patterns, you support Unified Profiles lookup. |
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
forstisabella
commented
Mar 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Added a new page with more detailed RETL scripts for Unified Profiles in Flex users who are using Salesforce.
Merge timing
as a fast follow to Unified Profiles in Flex beta - trying to release this as soon as possible
Related issues (optional)
DOC-806
#6059