Merge branch 'master' into DOC-240_actions-migration-proto

Author: markzegarelli

src/connections/destinations/catalog/salesforce-marketing-cloud/index.md

@@ -29,7 +29,7 @@ Segment sends data to SFMC using [Data Extensions](https://help.salesforce.com/a
 
 - **Data Extensions** are tables that contain your data. When this data arrives in SFMC, you can use it to create targeted marketing campaigns using push notifications and emails. You can view and query Data Extensions using the Journey Builder in SFMC. During the set up process, you will create a Data Extensions for Identify calls, and one for each unique Track call.
 
-- **API Events** can trigger an email or push notification campaign immediately when they receive data from Segment.
+- **API Events** can trigger an email or push notification c ampaign immediately when they receive data from Segment.
 
 
 ## SFMC prerequisites
@@ -280,8 +280,9 @@ In order to do this, you must have access to **Personas**. To learn more, [conta
 > info ""
 > **Tip**: We recommend that you use [SFMC batching](#optional-set-up-sfmc-batching) with Personas to help reduce the number of API calls that you send to SFMC, but this is optional. If you choose to set up batching, do this _before_ you set up the SFMC destination in your Segment workspace.
 
-1. In your Personas space, add the SFMC destination to a computed trait or audience.
-2. Enter the Data Extension External Key for the existing Data Extension. When your audience syncs to it, Segment adds a new column which stores the computed trait or audience membership.
+Personas sends audience membership and computed trait values to SFMC using Identify calls. To integrate Personas with SFMC:
+1. [Create a Data Extension to store Identify calls](#create-a-data-extension-in-sfmc-to-store-identify-calls) if you haven't already. 
+2. [Configure SFMC as a Personas Destination](#configure-the-salesforce-marketing-cloud-destination-in-segment)
 
 When you sync to an existing Data Extension, note these additional requirements:
 - The table cannot have an existing **Primary Key**, unless it is the `Contact Key` field, and the field type is `Text`.
@@ -293,7 +294,12 @@ When you sync to an existing Data Extension, note these additional requirements:
 
 ### Syncing Personas Audiences to SFMC
 
-When you add an audience to SFMC, the first sync contains all the users in that audience. A user is added as a new row to the Data Extension the first time they enter an audience. For example, let’s say you have an "Active Users" audience. When you send this audience to SFMC, all the users in the audience are added to a Data Extension, with a column that indicates their audience membership with `true`.  **To work correctly**, the Personas audience name should be Title Cased in the Data Extension column. Segment automatically creates the column name in Title Case. Do not change the column casing.
+Use the following process when syncing audiences to SFMC:
+
+1. Create a boolean field on the SFMC Data Extension to store audience membership information. The name of the field must match the name of the Segment audience you will create, and must be Title Cased.
+2. In your Personas space, add the SFMC destination to an audience, ensuring you specify the same name assigned to the SFMC field.
+
+When you add an audience to SFMC, the first sync contains all the users in that audience. A user is added as a new row to the Data Extension the first time they enter an audience. For example, let’s say you have an "Active Users" audience. When you send this audience to SFMC, all the users in the audience are added to a Data Extension, with a field value that indicates their audience membership with `true`.  **To work correctly**, the Personas audience name should be Title Cased in the Data Extension field.
 
 If a user leaves that audience, the value is automatically updated to `false`, but the user is not removed from the Extension. This allows you to see all users who have ever been in the audience, and then optionally create a filtered Data Extension if you want a subset. See the SFMC documentation for more details:
 
@@ -302,8 +308,10 @@ If a user leaves that audience, the value is automatically updated to `false`, b
 
 ### Syncing Personas Computed Traits to SFMC
 
-When you send a computed trait to SFMC, Segment creates a new column named after the computed trait,  and which contains the computed trait calculated by Personas value for each user.
+Use the following process when syncing Computed Traits to SFMC:
 
+1. Create a field on the SFMC Data Extension to store Computed Trait values. The name of the field must match the name of the Segment Computed Trait you'll create, and must be Title Cased. Choose a matching data type (for example, `text` for traits which produce string values, `number` or `decimal` for traits which produce numeric values).  
+2. In your Personas space, add the SFMC destination to a Computed Trait, ensuring you specify the same name assigned to the SFMC field.
 
 ## Troubleshooting and Tips
 

src/partners/subscriptions/index.md

@@ -22,11 +22,6 @@ Review the steps outlined in the [Developer Center Overview](/docs/partners). Th
 ## Build & Test
 
 > note ""
-> **NOTE:** On July 31, 2021 support for building Subscription Functions will be removed from Developer Center. You may continue building a Subscription Webhook. Segment is committed to improving the Developer Center experience with Developer Center 2.0, which will offer a more holistic approach to building on Segment. If you’re interested in joining the beta in the coming months, please fill out [this form](https://airtable.com/shrvZzQ6NTTwsc6rQ){:target="_blank"}.
+> **NOTE:** On July 31, 2021 support for building Subscription Functions was removed from Developer Center. You may continue building [Subscription Webhooks](/docs/partners/subscriptions/build-webhook) in place of Subscription Functions. Work has begun on Developer Center 2.0 which will offer a more holistic approach to building on Segment. If you’re interested in joining the beta in the coming months, please fill out [this form](https://airtable.com/shrvZzQ6NTTwsc6rQ){:target="_blank"}!
 
-You can subscribe to customer data in two ways:
-
-1. **[Webhook](/docs/partners/subscriptions/build-webhook)**: Build a new HTTP service that receives Webhook POSTs from Segment.
-2. **[Functions](/docs/partners/subscriptions/build-functions)**: Write JavaScript functions that run on Segment to translate and send data to your existing API. [Get started...](/docs/partners/subscriptions/build-functions)
-
-See the [Webhook](/docs/partners/subscriptions/build-webhook) and [Functions](/docs/partners/build-functions/) docs in-depth technical details about building.
+[Subscription Webhooks](/docs/partners/subscriptions/build-webhook) allow you to build a new HTTP service that receives Webhook POSTs from Segment. Read more in-depth technical details about building in [our documentation here](/docs/partners/subscriptions/build-webhook).

src/personas/sql-traits.md

@@ -61,18 +61,18 @@ To use SQL Traits, you need the following:
 
 ### Step 1. Set up a warehouse source
 
-Segment supports Redshift, Postgres, Snowflake, Azure, and BigQuery as data warehouse sources for SQL Traits. The setup process for BigQuery is a bit different as it _requires_ a service user.
+Segment supports Redshift, Postgres, Snowflake, Azure SQL, and BigQuery as data warehouse sources for SQL Traits. The setup process for BigQuery is a bit different as it _requires_ a service user.
 
 > info "Safeguard your data"
 > For any warehouse, we recommend that you create a separate read-only user for building SQL Traits.
 
-#### Redshift, Postgres, Snowflake Setup
+#### Redshift, Postgres, Snowflake, Azure SQL Setup
 
 If you don't already have a data warehouse, follow one of the guides here first:
 - [Redshift Getting Started](/docs/connections/storage/catalog/redshift/#getting-started)
 - [Postgres Getting Started](/docs/connections/storage/catalog/postgres/#getting-started)
 - [Snowflake Getting Started](/docs/connections/storage/catalog/snowflake/#getting-started)
-- [Azure Getting Started](/docs/connections/storage/catalog/azuresqldw/#getting-started)
+- [Azure SQL Getting Started](/docs/connections/storage/catalog/azuresqldw/#getting-started)
 
 Remember to create a read-only service user!