Merge pull request #2102 from segmentio/develop

stayseesong · web-flow · commit 2844fa430308 · 2021-11-04T09:38:02.000-07:00
Release 21.44.2
diff --git a/src/connections/destinations/catalog/actions-customer-io/index.md b/src/connections/destinations/catalog/actions-customer-io/index.md
@@ -15,7 +15,7 @@ redirect_from:
 
 
 > success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Customer.io destination](/docs/connections/destinations/catalog/customer-io/). Both of these destinations receives data _from_ Segment. There's also the [Customer.io source](/docs/connections/sources/catalog/cloud-apps/customer-io/), which sends data _to_ Segment!
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Customer.io Segment destination. There's also a page about the [non-Actions Customer.io destination](/docs/connections/destinations/catalog/customer-io/). Both of these destinations receives data _from_ Segment. There's also the [Customer.io source](/docs/connections/sources/catalog/cloud-apps/customer-io/), which sends data _to_ Segment!
 
 ## Benefits of Customer.io (Actions) vs Customer.io classic
 
@@ -54,4 +54,4 @@ Build your own subscription. Combine the supported [triggers](/docs/connections/
 ## Migration from Customer.io classic
 
 Keep the following in mind if you plan to move to Customer.io (Actions) from the classic Customer.io destination.
-{% include components/actions-map-table.html name="customer-io" %}
+{% include components/actions-map-table.html name="customer-io" %}
diff --git a/src/connections/regional-segment-eu.md b/src/connections/regional-segment-eu.md
@@ -14,6 +14,7 @@ As Schrems II restricts the transfer of personal data to any processors establis
 > info ""
 > [Cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources aren't supported in EU workspaces. 
 
+
 > info ""
 > Regional Segment for Europe is currently in beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
 
@@ -27,6 +28,7 @@ To create a workspace with a different data processing region:
 > info ""
 > Once you create a workspace with a specified data processing region, you can't change the region. You must create a new workspace to change the region.
 
+
 ## Regional Data Ingestion
 Regional Data Ingestion enables you to send data to Segment from both Device-mode and Cloud-mode sources through regionally hosted API ingest points. The regional infrastructure can fail across locations within a region, but never across regions.
 
@@ -41,6 +43,7 @@ To set your Data Ingestion Region:
     * If you’re in the *US West* data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney.
     * If you're in the *EU West* data processing region, Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
 
+
 ### Client-side sources
 You can configure Segment’s client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you’ve updated the Data Ingestion Region in that source’s settings.
 
diff --git a/src/connections/sources/catalog/cloud-apps/regal-voice/index.md b/src/connections/sources/catalog/cloud-apps/regal-voice/index.md
@@ -29,6 +29,14 @@ The table below lists events that Regal Voice sends to Segment. These events app
    <td>Event Name</td>
    <td>Description</td>
   </tr>
+  <tr>
+   <td>agent.activity.updated</td>
+   <td>An agent’s activity status was changed.</td>
+  </tr>
+  <tr>
+   <td>call.completed</td>
+   <td>An inbound or outbound call with a contact was completed. This includes calls that were not answered</td>
+  </tr>
   <tr>
    <td>contact.subscribed</td>
    <td>A contact was subscribed to a marketing channel</td>
@@ -45,6 +53,10 @@ The table below lists events that Regal Voice sends to Segment. These events app
     <td>contact.experiment.assigned</td>
     <td>A contact was assigned to an experiment</td>
   </tr>
+  <tr>
+   <td>sms.conversation.completed</td>
+   <td>An SMS conversation between a contact and an agent was completed in the Regal Voice agent desktop</td>
+  </tr>
   <tr>
    <td>sms.queued</td>
    <td>An sms was queued to be sent from RegalVoice to contact</td>
@@ -61,21 +73,13 @@ The table below lists events that Regal Voice sends to Segment. These events app
    <td>sms.received</td>
    <td>An sms was received from a contact</td>
   </tr>
-  <tr>
-   <td>task.created</td>
-   <td>A call or sms task was created</td>
-  </tr>
   <tr>
     <td>task.canceled</td>
     <td>A call or sms task was canceled</td>
   </tr>
   <tr>
-   <td>sms.conversation.completed</td>
-   <td>An SMS conversation between a contact and an agent was completed in the Regal Voice agent desktop</td>
-  </tr>
-  <tr>
-   <td>call.completed</td>
-   <td>An inbound or outbound call with a contact was completed. This includes calls that were not answered</td>
+   <td>task.created</td>
+   <td>A call or sms task was created</td>
   </tr>
 </table>
 
@@ -86,10 +90,30 @@ The table below lists events that Regal Voice sends to Segment. These events app
    <td>Property Name</td>
    <td>Description</td>
   </tr>
+  <tr>
+   <td>`agent_activity_name`</td>
+   <td>Name of agent’s new availability status.</td>
+  </tr>
+  <tr>
+   <td>`agent_availability`</td>
+   <td>Availability of agent’s previous activity status. Can be true or false.</td>
+  </tr>
   <tr>
    <td>`agent_email`</td>
    <td>Email of the agent who took an action</td>
   </tr>
+  <tr>
+   <td>`agent_previous_activity_name`</td>
+   <td>Name of agent’s previous availability status.</td>
+  </tr>
+  <tr>
+   <td>`agent_previous_availability`</td>
+   <td>Availability of agent’s previous activity status. Can be true or false.</td>
+  </tr>
+  <tr>
+   <td>`agent_time_in_previous_activity`</td>
+   <td>Time (in seconds) agent spent in previous activity status.</td>
+  </tr>
   <tr>
    <td>`call_id`</td>
    <td>Task Id for the call</td>
diff --git a/src/connections/sources/catalog/cloud-apps/salesforce/index.md b/src/connections/sources/catalog/cloud-apps/salesforce/index.md
@@ -2,28 +2,26 @@
 title: Salesforce Source
 strat: salesforce
 ---
-Salesforce is a leader in on-demand customer relationship management. [Visit Website](http://salesforce.com)
+[Salesforce](http://salesforce.com){:target="_blank"} is a leader in on-demand customer relationship management.
 
-Take your company's analysis to the next level by **adding Salesforce as a Source to Segment.** Segment automatically  collects objects like `Accounts`, `Campaigns`, and `Tasks` and load them into your data warehouse. 
+Take your company's analysis to the next level by **adding Salesforce as a Source to Segment.** Segment automatically collects objects like `Accounts`, `Campaigns`, and `Tasks` and loads them into your data warehouse. 
 
 ## Getting Started
 > info ""
-> You can add multiple instances of this destination if you have more than one SalesForce account. 
+> You can add multiple instances of this destination if you have more than one Salesforce account. 
 
-1. From your workspace's `/sources` page, click `add source`.
+1. From your workspace's `/sources` page, click `Add Source`.
 
 2. Choose Salesforce.
 
-3. Give the source a name.
+3. Give the source a name, add labels, if applicable, and select the Salesforce environment you'd like to pull data from. To use data from a Salesforce sandbox environment, select **Sandbox** from the Salesforce Environment dropdown and [contact Segment Support](https://segment.com/help/contact/). Our Support team will then configure your source to use sandbox data.
 
-4. Connect Segment to your Salesforce environment and authorize Segment to connect to it. In order for Segment to collect and sync your Salesforce data, you must enable API access for the user that you are connecting to Segment with. For more information on how to confirm or change API access for a Salesforce user, follow Salesforce's [recommended documentation](https://help.salesforce.com/articleView?id=admin_userperms.htm).
+4. Connect Segment to your Salesforce environment and authorize Segment to connect to it. In order for Segment to collect and sync your Salesforce data, you must enable API access for the user that you are connecting to Segment with. For more information on how to confirm or change API access for a Salesforce user, follow Salesforce's [recommended documentation](https://help.salesforce.com/articleView?id=admin_userperms.htm){:target="_blank"}.   
 
 5. Choose a data warehouse to connect Salesforce to.
 
 6. In the Salesforce source settings you can customize the source nickname and schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. Both can be whatever you like, but Segment recommends that you use something that reflects the source itself, like `Salesforce` for nickname and `sfdc`, `salesforce`, or `sfdc_prod` for the schema name. Configure Selective Sync to retrieve only specific objects and properties from Salesforce.
 
-
-
 ## Components
 
 ### Sync
@@ -115,3 +113,7 @@ Segment performs a one-to-one mapping of all publicly available fields (standard
 ## Adding Destinations
 
 Warehouses are the only supported destination for object-cloud sources.
+
+## Troubleshooting
+
+If you are syncing data from a Salesforce sandbox environment and see an "Invalid credentials" error, [contact our support team](https://segment.com/help/contact/), who will configure your Segment source to use sandbox data. 
diff --git a/src/connections/sources/catalog/cloud-apps/sendgrid/index.md b/src/connections/sources/catalog/cloud-apps/sendgrid/index.md
@@ -70,10 +70,10 @@ Collections are the groupings of resources we pull from your source. In your war
 |  deferred | Event | Recipient's email server temporarily rejected message. |
 |  unsubscribe | Event | Recipient clicked on message's subscription management link. You need to enable Subscription Tracking for getting this type of event. |
 |  spam_report | Event | Recipient marked message as spam. |
-|  lists | Object | [Groups of contacts](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html). **Will only return data if you're using Marketing Campaign featurs of SendGrid.** |
-|  segments | Object | [Slices of lists](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html). **Will only return data if you're using Marketing Campaign featurs of SendGrid.** |
-|  recipients | Object | All contacts who have received an email, with information about their last activities and custom activities. [More Info](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html).  **Will only return data if you're using Marketing Campaign featurs of SendGrid.** |
-|  campaigns | Object | All campaigns you've created in Sendgrid. [More Info](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/campaigns.html).  **Will only return data if you're using Marketing Campaign featurs of SendGrid.** |
+|  lists | Object | [Groups of contacts](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html). **Will only return data if you're using Marketing Campaign features of SendGrid.** |
+|  segments | Object | [Slices of lists](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html). **Will only return data if you're using Marketing Campaign features of SendGrid.** |
+|  recipients | Object | All contacts who have received an email, with information about their last activities and custom activities. [More Info](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html).  **Will only return data if you're using Marketing Campaign features of SendGrid.** |
+|  campaigns | Object | All campaigns you've created in Sendgrid. [More Info](https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/campaigns.html).  **Will only return data if you're using Marketing Campaign features of SendGrid.** |
 
 ## Troubleshooting 
 
diff --git a/src/connections/storage/warehouses/schema.md b/src/connections/storage/warehouses/schema.md
@@ -258,7 +258,7 @@ analytics.track('Register', {
 Then you can expect to see columns named `plan` and `account_type` as well as the default `event`, `id`, and so on. That way, you can write queries against any of the custom data sent in track calls.
 
 > info "Note"
-> Because `properties` and `traits` are added as un-prefixed columns to your tables, there is a chance of collision with our reserved column names. For this reason, properties with the same name as reserved column name (for example. `user_id`) are discarded.
+> Because Segment adds `properties` and `traits` as un-prefixed columns to your tables, there is a chance the names can collide with the reserved column names. For this reason, Segment discards properties with the same name as the reserved column name (for example, `user_id`).
 
 Your event tables are one of the more powerful datasets in Segment SQL. They allow you to see which actions users perform when interacting with your product.
 
