From 625f2043d777fb4647dd5aa8c11735c5afa3bee9 Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Wed, 20 Apr 2022 13:47:22 -0700 Subject: [PATCH 1/2] Add Vidora to allow list --- .github/Vocab/Docs/accept.txt | 2 ++ vale-styles/Vocab/Docs/accept.txt | 1 + 2 files changed, 3 insertions(+) diff --git a/.github/Vocab/Docs/accept.txt b/.github/Vocab/Docs/accept.txt index 0db37ab47f..e5d5815d6a 100644 --- a/.github/Vocab/Docs/accept.txt +++ b/.github/Vocab/Docs/accept.txt @@ -7,6 +7,7 @@ (?:L|l)ookback (?:P|p)ageviews?\b (?:P|p)endo +(?:P|p)odfile (?:P|p)ostgres (?:R|r)emarketing (?:U|u)nlinks?\b @@ -69,6 +70,7 @@ upsert US utm Vero +Vidora viewability WebKit Wootric diff --git a/vale-styles/Vocab/Docs/accept.txt b/vale-styles/Vocab/Docs/accept.txt index 49ff236065..e5d5815d6a 100644 --- a/vale-styles/Vocab/Docs/accept.txt +++ b/vale-styles/Vocab/Docs/accept.txt @@ -70,6 +70,7 @@ upsert US utm Vero +Vidora viewability WebKit Wootric From d97ba7d98051cd7f12456482b97c5fffe1614e20 Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Wed, 20 Apr 2022 16:54:05 -0700 Subject: [PATCH 2/2] Remove section about actions --- src/connections/destinations/catalog/salesforce/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/salesforce/index.md b/src/connections/destinations/catalog/salesforce/index.md index 89bbf41c86..a1d0219b7d 100644 --- a/src/connections/destinations/catalog/salesforce/index.md +++ b/src/connections/destinations/catalog/salesforce/index.md @@ -27,7 +27,7 @@ This destination supports the most important pain point for Salesforce users: ge ### Identifying a Lead -Let's go through a quick javascript example of identifying a lead: +The example below demonstrates identifying a lead: ```javascript analytics.identify('YOUR_USERS_ID', { @@ -91,7 +91,7 @@ By default Segment does not send identify calls to Salesforce, given their stric ## Group -`.group()` calls create or update **Account Objects** inside Salesforce. When Segment receives a group call, similar to the `.identify()` call, it first checks using the `groupId` to see if the Account Object already exists in your Salesforce account. Depending on the response, Segment updates that object or create a new one. Creating/updating Accounts is the default behavior of `group` events. If you would like to customize this you can do so using [Actions](#custom-actions) +`.group()` calls create or update **Account Objects** inside Salesforce. When Segment receives a group call, similar to the `.identify()` call, it first checks using the `groupId` to see if the Account Object already exists in your Salesforce account. Depending on the response, Segment updates that object or create a new one. Creating/updating Accounts is the default behavior of `group` events. Take this sample `.group()` call that you might send to Segment: