Skip to content

Commit 53f26a4

Browse files
forstisabellaforstisabella
authored
Merge branch 'master' into develop
2 parents 885cc54 + 4fd074a commit 53f26a4

File tree

2 files changed

+109
-13
lines changed

2 files changed

+109
-13
lines changed

‎src/unified-profiles/create-sql-traits.md

Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
1+
---
2+
title: RETL Queries for Importing Salesforce Objects Into Unified Profiles in Flex
3+
hidden: true
4+
---
5+
You can use the following SQL 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). Unified Profiles in Flex requires phone numbers used for profile lookups to be in E.164 format.
6+
7+
Segment created three sample queries for Unified Profiles users to import common Salesforce objects:
8+
- [Accounts](#accounts)
9+
- [Contacts](#contacts)
10+
- [Leads](#leads)
11+
12+
To selectively import columns, replace the `a*`, `c*`, or `l*` with a list of fields to selectively import. For example, if you wanted to only import the ID, NAME, and ADDRESS fields for your Accounts, you'd replace `a*` with `a.ID, a.NAME, a.ADDRESS`.
13+
14+
> success ""
15+
> Segment creates a default database table (`segment_flex_unify`) during the [Segment for Flex](/docs/unified-profiles/segment-for-flex/){:target="_blank”} setup process.
16+
17+
## Accounts
18+
19+
To import Salesforce Accounts into Unified Profiles as Segment Unify profiles, create a RETL mapping with the following format.
20+
21+
Replace `<database_name.account_table>` with your database name and account table, `PHONE` with the name of the column in your warehouse that contains phone numbers, and `BILLING_COUNTRY` with the name of the column in your warehouse that contains the account's country. In this sample query, the `PHONE` column is the primary contact phone number and what you import as the Profile’s 'phone' trait.
22+
23+
The other phone fields for Salesforce Accounts are PersonHomePhone, PersonMobilePhone, & PersonOtherPhone, and could be substituted for `PHONE` in this query. **You can only import one phone number field as the identifier used for lookups in Unified Profiles.**
24+
25+
``` sql
26+
SELECT
27+
a.*,
28+
CASE
29+
WHEN a.PHONE REGEXP '^(\\([0-9]{3}\\) [0-9]{3}-[0-9]{4})$' AND a.BILLING_COUNTRY = 'US'
30+
THEN CONCAT('+1', REGEXP_REPLACE(a.PHONE, '[^0-9]',''))
31+
WHEN a.BILLING_COUNTRY != 'US'
32+
THEN REGEXP_REPLACE(a.PHONE, '[^0-9]','')
33+
ELSE a.PHONE
34+
END as phone,
35+
FROM
36+
<database_name.account_table> a
37+
WHERE
38+
a.PHONE IS NOT NULL
39+
AND a.BILLING_COUNTRY IS NOT NULL;
40+
```
41+
42+
After running this query, you can use ‘phone’ for lookups in Unified Profiles.
43+
44+
45+
## Contacts
46+
47+
To import Salesforce Contacts into Unified Profiles as Segment Unify profiles, create a RETL mapping with the following format.
48+
49+
Replace `<database_name.contact_table>` with your database name and account table, `PHONE` with the name of the column in your warehouse that contains phone numbers, and `BILLING_COUNTRY` with the name of the column in your warehouse that contains the contact's country.
50+
51+
Salesforce objects have several phone number-related fields. In this sample query, the `PHONE` column is the primary contact phone number and what you import as the Profile’s 'phone' trait.
52+
53+
The other phone fields for Salesforce Contacts are HomePhone, MobilePhone, & OtherPhone, and could be substituted for `PHONE` in this query. **You can only import one phone number field as the identifier used for lookups in Unified Profiles.**
54+
55+
``` sql
56+
SELECT
57+
c.*,
58+
CASE
59+
WHEN c.PHONE REGEXP '^(\\([0-9]{3}\\) [0-9]{3}-[0-9]{4})$' AND c.BILLING_COUNTRY = 'US'
60+
THEN CONCAT('+1', REGEXP_REPLACE(c.PHONE, '[^0-9]',''))
61+
WHEN c.BILLING_COUNTRY != 'US'
62+
THEN REGEXP_REPLACE(c.PHONE, '[^0-9]','')
63+
ELSE c.PHONE
64+
END as phone,
65+
FROM
66+
<database_name.contact_table> c
67+
WHERE
68+
c.PHONE IS NOT NULL
69+
AND c.BILLING_COUNTRY IS NOT NULL;
70+
```
71+
72+
After running this query, you can use ‘phone’ for lookups in Unified Profiles.
73+
74+
## Leads
75+
76+
To import Salesforce Leads into Unified Profiles as Segment Unify profiles, create a RETL mapping with the following format.
77+
78+
Replace `<database_name.lead_table>` with your database name and lead table, `PHONE` with the name of the column in your warehouse that contains phone numbers, and `BILLING_COUNTRY` with the name of the column in your warehouse that contains the lead's country.
79+
80+
Salesforce objects have several phone number-related fields. In this sample query, the `PHONE` column is the primary contact phone number and what you import as the Profile’s 'phone' trait.
81+
82+
The other phone fields for Salesforce Leads are HomePhone, MobilePhone, & OtherPhone, and could be substituted for `PHONE` in this query. **You can only import one phone number field as the identifier used for lookups in Unified Profiles.**
83+
84+
``` sql
85+
SELECT
86+
l.*,
87+
CASE
88+
WHEN l.PHONE REGEXP '^(\\([0-9]{3}\\) [0-9]{3}-[0-9]{4})$' AND l.BILLING_COUNTRY = 'US'
89+
THEN CONCAT('+1', REGEXP_REPLACE(l.PHONE, '[^0-9]',''))
90+
WHEN l.BILLING_COUNTRY != 'US'
91+
THEN REGEXP_REPLACE(l.PHONE, '[^0-9]','')
92+
ELSE l.PHONE
93+
END as phone,
94+
FROM
95+
<database_name.lead_table> l
96+
WHERE
97+
l.PHONE IS NOT NULL
98+
AND l.BILLING_COUNTRY IS NOT NULL;
99+
```
100+
101+
After running this query, you can use ‘phone’ for lookups in Unified Profiles.
102+
103+
## Troubleshooting
104+
If these queries don't return phone numbers in E.164 format, examine your existing data and change the REGEX patterns as appropriate.
105+
106+
Because the format in which an international phone number is saved in Salesforce largely depends on how users input them into the system, Salesforce administrators can add form validation methods, like input field validation rules with REGEXP functions, to guide users to input phone numbers in specific formats. These form validation methods may impact the format of the phone numbers in your database, and might require you to change the REGEXP patterns in the provided queries.

‎src/unified-profiles/segment-for-flex.md

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -38,12 +38,7 @@ You can add additional data sources after completing the setup process. <br>
3838
5. Give your destination a name and enter the account credentials for a user that has read and write permissions. Click **Save**.
3939
6. After you've given your destination a name and entered your credentials, click **Next**.
4040
7. On the Getting started with Segment page, click **Define Model**.
41-
8. Create a SQL query that defines your model. After you've created a model, Segment uses your model to map data to your Reverse ETL destinations. <br> Segment recommends a model with the following format:
42-
43-
``` sql
44-
SELECT * FROM salesforce_flex_unify.accounts
45-
```
46-
41+
8. [Create a SQL query that defines your model](/docs/unified-profiles/create-sql-traits){:target="_blank"}. After you've created a model, Segment uses your model to map data to your Reverse ETL destinations.
4742
<ol style="counter-reset: none;">
4843
<li value="9" markdown=1>
4944
Click **Preview** to return 10 records from your warehouse. When you've verified that your records return as expected, click **Next**.
@@ -64,12 +59,7 @@ SELECT * FROM salesforce_flex_unify.accounts
6459
3. Give your destination a name and enter the account credentials for a user that has read and write permissions. Click **Save**.
6560
4. After you've given your destination a name and entered your credentials, click **Next**.
6661
5. On the *Getting started with Segment* page, click **Define Model**.
67-
6. Create a SQL query that defines your model. After you've created a model, Segment uses your model to map data to your Reverse ETL destinations. <br> Segment recommends a model with the following format:
68-
69-
``` sql
70-
SELECT * FROM flex_unify.accounts
71-
```
72-
62+
6. [Create a SQL query that defines your model](/docs/unified-profiles/create-sql-traits){:target="_blank"} After you've created a model, Segment uses your model to map data to your Reverse ETL destinations.
7363
<ol style="counter-reset: none;">
7464
<li value="7" markdown=1>
7565
Click **Preview** to return 10 records from your warehouse. When you've verified that your records return as expected, click **Next**.
@@ -186,6 +176,6 @@ Your Segment for Flex workspace has the following entitlements:
186176
href="/docs/unified-profiles/connect-a-workspace"
187177
icon="api.svg"
188178
title="Connect an Existing Workspace to Flex"
189-
description="Flex customers without an existing Segment workspace that includes a Unify space can obtain a Segment for Flex workspace and configure a Unify space. A Segment for Flex workspace provides limited access to Segment."
179+
description="Flex customers with an existing Segment workspace that has a Unify space can connect their Unify space to Flex."
190180
%}
191181
</div>

0 commit comments

Comments
 (0)