Skip to content

Commit 96406ac

Browse files
Apply suggestions from code review [netlify-build]
1 parent 2514de7 commit 96406ac

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Segment created three sample queries for Unified Profiles users to import common
99
- [Contacts](#contacts)
1010
- [Leads](#leads)
1111

12-
To create a query that selects a different field, replace the `a`, `c`, or `l` with a list of fields to selectively import.
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`.
1313

1414
> success ""
1515
> Segment creates a default database table (`segment_flex_unify`) during the [Segment for Flex](/docs/unified-profiles/segment-for-flex/){:target="_blank”} setup process.
@@ -18,7 +18,7 @@ To create a query that selects a different field, replace the `a`, `c`, or `l` w
1818

1919
To import Salesforce Accounts into Unified Profiles as Segment Unify profiles, create a RETL mapping with the following format.
2020

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 billing country.
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.
2222

2323
``` sql
2424
SELECT
@@ -39,14 +39,14 @@ WHERE
3939

4040
Salesforce objects have several phone number-related fields. In this example query, the “PHONE” column is the primary contact phone number and what you import as the Profile’s 'phone' trait. The other phone fields for Salesforce Accounts are PersonHomePhone, PersonMobilePhone, & PersonOtherPhone, and could be substituted for "PHONE" in this query.
4141

42-
After running this query, 'phone' would be an Identity used for lookups in Unified Profiles.
42+
After running this query, phone’ can be used as an identifier used for lookups in Unified Profiles.
4343

4444

4545
## Contacts
4646

4747
To import Salesforce Contacts into Unified Profiles as Segment Unify profiles, create a RETL mapping with the following format.
4848

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 billing country.
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.
5050

5151
``` sql
5252
SELECT
@@ -67,13 +67,13 @@ WHERE
6767

6868
Salesforce objects have several phone number-related fields. In this example query, the “PHONE” column is the primary contact phone number and what you import as the Profile’s 'phone' trait. The other phone fields for Salesforce Contacts are HomePhone, MobilePhone, & OtherPhone, and could be substituted for "PHONE" in this query.
6969

70-
After running this query, 'phone' would be an Identity used for lookups in Unified Profiles.
70+
After running this query, phone’ can be used as an identifier used for lookups in Unified Profiles.
7171

7272
## Leads
7373

7474
To import Salesforce Leads into Unified Profiles as Segment Unify profiles, create a RETL mapping with the following format.
7575

76-
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 billing country.
76+
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.
7777

7878
``` sql
7979
SELECT
@@ -94,7 +94,7 @@ WHERE
9494

9595
Salesforce objects have several phone number-related fields. In this example query, the “PHONE” column is the primary contact phone number and what you import as the Profile’s 'phone' trait. The other phone fields for Salesforce Leads are HomePhone, MobilePhone, & OtherPhone, and could be substituted for "PHONE" in this query.
9696

97-
After running this query, 'phone' would be an Identity used for lookups in Unified Profiles.
97+
After running this query, phone’ can be used as an identifier used for lookups in Unified Profiles.
9898

9999
## Troubleshooting
100100
If these queries don't return phone numbers in E.164 format, examine your existing data and change the REGEX patterns as appropriate.

0 commit comments

Comments
 (0)