Merge pull request #2945 from segmentio/develop

Release 22.21.1

Author: stayseesong

src/connections/destinations/catalog/mouseflow/index.md

@@ -3,7 +3,7 @@ rewrite: true
 title: Mouseflow Destination
 id: 54521fd925e721e32a72eeda
 ---
-[Mouseflow](https://mouseflow.com/) is a session replay and heatmap tool that shows how visitors click, move, scroll, browse, and pay attention on websites. It helps clients simplify their analytics to make decisions that matter. The `analytics.js` Mouseflow Destination is open-source. You can browse the code [on GitHub](hhttps://github.com/segment-integrations/analytics.js-integration-mouseflow).
+[Mouseflow](https://mouseflow.com/) is a session replay and heatmap tool that shows how visitors click, move, scroll, browse, and pay attention on websites. It helps clients simplify their analytics to make decisions that matter. The `analytics.js` Mouseflow Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-mouseflow).
 
 ## Getting Started
 

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

@@ -31,7 +31,9 @@ Analytics.js sources will upgrade to Analytics.js 2.0 on the date below, accordi
 |--------------| -------------|
 | Free         | June 15, 2021|
 | Team         | July 6, 2021 |
-| Business     | June 2022    |
+| Business*    | June 2022    |
+
+*If you're on a business plan, please reach out to [[email protected]](mailto:[email protected]) to see if your account is part of the upgrade in June 2022.
 
 > info ""
 > The plans and dates listed above are subject to change.
@@ -50,7 +52,7 @@ If the source you intend to upgrade uses the in-domain instrumentation as well a
 
 ### Using a mix of Analytics.js Classic and 2.0 sources
 
-If you're using a mix of Analytics.js Classic and 2.0 sources, the classic source won't be able to use the anonymous ID set by Analytics.js 2.0. In order to fix this, update all sources to 2.0. 
+If you're using a mix of Analytics.js Classic and 2.0 sources, the classic source won't be able to use the anonymous ID set by Analytics.js 2.0. In order to fix this, update all sources to 2.0.
 
 ### Relying on Analytics.js Classic's `ajs_anonymous_id` cookie format  
 

src/connections/storage/catalog/azuresqldw/index.md

@@ -5,76 +5,86 @@ redirect_from:
   - '/connections/warehouses/catalog/azuresqldw/'
 ---
 
-Azure's [Azure Synapse Analytics](https://azure.microsoft.com/en-us/services/synapse-analytics/), previously known as Azure SQL Data Warehouse, is a limitless analytics service that brings together enterprise data warehousing and Big Data analytics.
+Azure's [Azure Synapse Analytics](https://azure.microsoft.com/en-us/services/synapse-analytics/){:target="_blank"}, previously known as Azure SQL Data Warehouse, is a limitless analytics service that brings together enterprise data warehousing and Big Data analytics.
 
 ## Getting Started
 
-There are four main steps to get started with Segment:
+Complete the following prerequisites in Microsoft Azure before connecting your Azure Synapse Analytics databases to Segment:
 
-1. Have an [Azure subscription](https://azure.microsoft.com/en-us/free/)
-2. Provision [SQL Data Warehouse (Dedicated SQL Pool)](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/create-data-warehouse-portal)
-3. Give Segment access to your SQL Data Warehouse
-4. Configure the Destination in Segment
+1. Sign up for an [Azure subscription](https://azure.microsoft.com/en-us/free/){:target="_blank"}.
+2. Provision a [Dedicated SQL Pool](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/create-data-warehouse-portal){:target="_blank"}.
 
-Follow the links above to follow Azure's documentation on setting up these prerequisites. Following that, the guide below should take you through the rest.
+## Connect your Azure database to Segment
 
-### Give Segment access to your SQL Data Warehouse
-
-First, create a server login for Segment to use. This can be accomplished by running the following SQL command on your SQL Server's `master` database.
-
-```sql
-CREATE LOGIN Segment WITH PASSWORD = '<strong password>';
-```
-
-Once this is done, no more action is needed for the `master` database. Next, connect to your Azure database in order to do some further configuration.
-
-Segment uses Azure Blob Storage to hold data that is being loaded into Azure Synapse Analytics. In order to facilitate this, a `MASTER KEY` is needed in order for credentials that Segment saves to the database to be encrypted.
+To connect your Azure database to Segment, [give Segment access to your SQL Data Warehouse](#give-segment-access-to-your-sql-data-warehouse) and [configure an Azure Synapse Analytics destination](#configure-an-azure-synapse-analytics-destination-in-segment).
 
-```sql
-CREATE MASTER KEY;
-```
-
-**NOTE:** If you are using your Azure Synapse Analytics for things besides Segment, it is possible this is already done. Either way, running the command another time will not hurt anything.
+### Give Segment access to your SQL Data Warehouse
 
-Next, create a new database user using the server login that was created previously:
+1. Create a server login for Segment to use. This can be accomplished by running the following SQL command on your SQL Server's `master` database:
+  ```sql
+  CREATE LOGIN Segment WITH PASSWORD = '<strong password>';
+  ```
 
-```sql
-CREATE USER Segment FOR LOGIN Segment;
-```
+2. Connect to your Azure database.
 
-This new user will need permissions to load data, and manage the resources it needs. Run the following command to accomplish this:
+3. Segment uses Azure Blob Storage to hold data that is being loaded into Azure Synapse Analytics. In order to facilitate this, a `MASTER KEY` is needed in order for credentials that Segment saves to the database to be encrypted. To create a master key, run the following command: 
+  ```sql
+  CREATE MASTER KEY;
+  ```
+  If you are using your Azure Synapse Analytics instance for more than just a Segment integration, it is possible you already have a master key. Running the command more than once will not create a new master key.
 
-```sql
-GRANT CONTROL TO Segment;
-```
+4. Create a new database user using the server login that you created in a previous step:
+  ```sql
+  CREATE USER Segment FOR LOGIN Segment;
+  ```
 
-Lastly, assign this new user a [resource allocation class](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/resource-classes-for-workload-management). The default (`smallrc`) likely will not give Segment enough memory to perform bulk loads, so we recommend starting with `largerc`. The larger "Dynamic Resource Classes" give more memory, while allowing fewer concurrent queries, which is a better fit for Segment's loading strategy:
+5. Run the following command to give your new user the permissions to load data and manage the resources in your database:
+  ```sql
+  GRANT CONTROL TO Segment;
+  ```
 
-```sql
-EXEC sp_addrolemember 'largerc', 'Segment';
-```
+6. Assign this new user a [resource allocation class](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/resource-classes-for-workload-management){:target="_blank"}:
+  ```sql
+  EXEC sp_addrolemember 'largerc', 'Segment';
+  ```
+  The default resource allocation class (`smallrc`) may not give Segment enough memory to perform bulk loads, so Segment recommends starting with `largerc`. The larger Dynamic Resource Classes give more memory and allow fewer concurrent queries, which is a better fit for Segment's loading strategy.
 
-By default, Azure Synapse Analytics cannot be connected to from the public internet. In order for Segment to connect, a [server-level firewall rule](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/create-data-warehouse-portal#create-a-server-level-firewall-rule) that allows connections from the [Segment IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-whitelist) is needed.
+7. By default, you cannot connect to Azure Synapse Analytics from the public internet. In order for Segment to connect to your instances, create a [server-level firewall rule](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/create-data-warehouse-portal#create-a-server-level-firewall-rule){:target="_blank"} that allows connections from the [Segment IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist):
+  ```sql
+  EXEC sp_set_firewall_rule N'<rule name>', '52.25.130.38', '52.25.130.38'; 
+  ```
 
-### Configure an Azure SQL Data Warehouse Destination in Segment
+### Configure an Azure Synapse Analytics Destination in Segment
 
-In order to set up the necessary destination in Segment, you'll need the following pieces of information:
+In order to set up the Azure Synapse Analytics destination in Segment, you'll need the following pieces of information:
 
  - **Server Name:** the name of the SQL Server resource that houses your SQL Data Warehouse
  - **Database:** the name of the SQL Data Warehouse database resource
  - **Username:** the name of the user you created above
  - **Password:** the password of the user you created above
 
-All of these fields are required in order for Segment to load data into your SQL Data Warehouse. The username and password can be obtained during steps of the previous section, while the server and database names can be found in the Azure Portal.
+To add a Azure Synapse Analytics destination in the Segment app: 
+1. Log in to Segment and select the **Connections** tab. Click **Add Destination**.
+2. Select the **Storage Destinations** tab and click the **Azure SQL Data Warehouse** destination. 
+3. Select the source(s) you want to sync with the Azure SQL Data Warehouse destination, and click **Next**. 
+4. Provide a name for your destination, and then enter data into each of the fields in the "Enter your Credentials" section. For the **Server Name** field, enter only the part of the server name prior to `.database.windows.net`. 
+5. Click **Connect**.
+
+> warning "Initial sync timeline"
+> The first sync after you configure your Azure Synapse destination with Segment can take up to 24 hours to complete.
 
 ## Best Practices
 
 ### Making sure Segment has enough resources to load your data
 
-The default [resource allocation class](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/resource-classes-for-workload-management) (ie: `smallrc`) likely will not give Segment enough memory to perform bulk loads, so we recommend using a larger class (eg: `largerc`). Larger classes allocate more memory, but limit the number of concurrent queries, which is a better fit for Segment's loading strategy.
+The default [resource allocation class](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/resource-classes-for-workload-management){:target="_blank"} (`smallrc`) may not give Segment enough memory to perform bulk loads, so Segment recommends using a larger class (`largerc`). Larger classes allocate more memory and limit the number of concurrent queries, which is a better fit for Segment's loading strategy.
+
+### Using Selective Sync
+
+Users with a Business Tier plan can enable Selective Sync for their Azure Synapse Analytics destination. With Selective Sync, you can customize which collections and properties from a source are sent to each warehouse, which leads to faster, more relevant syncs. To learn more about Selective Sync, review the [Warehouse Syncs](/docs/connections/storage/warehouses/warehouse-syncs/#warehouse-selective-sync) documentation.
 
 ## Troubleshooting
 
 ### Segment is not able to connect to Azure Synapse Analytics
 
-Make sure a [server-level firewall rule](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/create-data-warehouse-portal#create-a-server-level-firewall-rule) that allows connections from the [Segment IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-whitelist) is configured.
+If you encounter this error, create a [server-level firewall rule](https://docs.microsoft.com/en-us/azure/sql-data-warehouse/create-data-warehouse-portal#create-a-server-level-firewall-rule){:target="_blank"} that allows connections from the [Segment IPs](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist).

src/personas/identity-resolution/index.md

@@ -14,7 +14,7 @@ Identity Resolution sits at the core of Personas. The Segment Identity Graph mer
 ## Highlights
 1. **Supports existing data** — no additional code or set up required
 2. **Supports all channels** — stitches web + mobile + server + third party interactions into the same user
-3. **Supports anonymous identity stitching** — by using merging child sessions into parent sessions
+3. **Supports anonymous identity stitching** — by merging child sessions into parent sessions
 4. **Supports user:account relationships** - for b2b companies, generates a graph of relationships between users and accounts
 5. **Realtime** - merges realtime data streams, tested at 50,000 resolutions/second with a P95 resolve duration of 7ms