Merge branch 'master' into DOC-318_fullstory-actions

markzegarelli · markzegarelli · commit bad057bc628e · 2021-09-21T10:22:09.000-07:00
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2021-09-17 
+# destination categories last updated 2021-09-21 
 items:
 - display_name: A/B Testing
   slug: a-b-testing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2021-09-17 
+# destination data last updated 2021-09-21 
 items:
 - display_name: 2mee
   name: 2mee
@@ -14638,21 +14638,21 @@ items:
     type: string
     defaultValue: ''
     description: >-
-      **(Private Beta) Device Mode Only**: The ID of the form you will use to
-      capture your .identify() traits. You can find the form ID under *Design
-      Studio > Forms > Select Form > Form Actions > Embed Code*. Only include
-      the digits after `mktoForm_`.
+      **Device Mode Only**: The ID of the form you will use to capture your
+      Segment Identify traits. You can find the form ID under **Design Studio >
+      Forms > Select Form > Form Actions > Embed Code**. Only include the digits
+      after `mktoForm_`.
     required: false
     label: Marketo Form ID
   - name: marketoHostUrl
     type: string
     defaultValue: ''
     description: >-
-      **(Private Beta) Device Mode Only**: The URL of the form you will use to
-      capture your .identify() traits. You can find the form URL under *Design
-      Studio > Forms > Select Form > Form Actions > Embed Code*. It will be the
-      first argument in the `MktoForms2.loadForm` script, starting with `//`.
-      Please include the entire URL including the `//`.
+      **Device Mode Only**: The URL of the form you will use to capture your
+      Segment Identify traits. You can find the form URL under **Design Studio >
+      Forms > Select Form > Form Actions > Embed Code**. It will be the first
+      argument in the `MktoForms2.loadForm` script, starting with `//`. Please
+      include the entire URL including the `//`.
     required: false
     label: Marketo Form URL
   - name: privateKey
@@ -14669,7 +14669,7 @@ items:
     defaultValue: []
     description: >-
       Use these fields for Marketo Lead fields that you'd like mapped to your
-      Segment Identify Traits.
+      Segment Identify traits.
     required: false
     label: Marketo Custom Fields
 - display_name: Markettailor
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2021-09-17 
+# source cateogries last updated 2021-09-21 
 items:
   - display_name: A/B Testing
     slug: a-b-testing
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2021-09-17 
+# sources last updated 2021-09-21 
 items:
   - display_name: .NET
     slug: net
diff --git a/src/_data/catalog/warehouse_papi.yml b/src/_data/catalog/warehouse_papi.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# warehouse data last updated 2021-09-17 
+# warehouse data last updated 2021-09-21 
 items:
 - display_name: Azure SQL Data Warehouse
   slug: azuresqldw
diff --git a/src/connections/destinations/catalog/amazon-kinesis-firehose/index.md b/src/connections/destinations/catalog/amazon-kinesis-firehose/index.md
@@ -187,7 +187,7 @@ If you have many sources using Kinesis that it's impractical to attach all of th
 To set this value for a Secret ID:
 1. Go to the Kinesis Firehose destination settings from each of your Segment sources.
 2. Click **Secret ID** and enter your Workspace ID.
-    * **NOTE:** For security purposes, Segment recommends you to use your Segment Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to:  **Settings > Workspace Settings > ID** from the Segment dashboard.
+    * **NOTE:** For security purposes, Segment sets your Segment Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it to make your account more secure.
 3. Once all of your sources are updated to use this value, find the IAM role you created for this destination in the AWS Console in **Services > IAM > Roles**.
 4. Select the role and navigate to the **Trust Relationships** tab.
 5. Click **Edit trust relationship**. You should see a snippet that looks something like this:
diff --git a/src/connections/destinations/catalog/amazon-kinesis/index.md b/src/connections/destinations/catalog/amazon-kinesis/index.md
@@ -48,7 +48,7 @@ To get started:
 4. Create a new Kinesis destination.
    1. In the Segment source that you want to connect to your Kinesis destination, click **Add Destination**. Search and select the **Amazon Kinesis** destination.
    2. Enter the **Role Address**, **Stream Region**, **Stream Name**, and **Secret ID**.
-   * **NOTE:** For security purposes, Segment recommends you to use your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to: **Settings > Workspace Settings > ID**.
+   * **NOTE:** For security purposes, Segment sets your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it to make your account more secure.
 
 ## Page
 If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
@@ -217,7 +217,7 @@ After you update the IAM policy, Segment systems default to use PutRecords for m
 If you have many sources using Kinesis that it's impractical to attach all of their IDs to your IAM role, you can instead opt to set a secret ID. To set this value:
 1. Go to **Connections > Destinations > Amazon Kinesis** for each of your Segment sources.
 2. Click **Secret ID** and enter your Workspace ID.
-    * **NOTE:** For security purposes, Segment recommends you to use your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to:  **Settings > Workspace Settings > ID**.
+    * **NOTE:** For security purposes, Segment sets your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
 3. Once all of your sources have been updated to use this value, find the IAM role you created for this destination in the AWS Console in **Services > IAM > Roles**.
 4. Click on the role and navigate to the **Trust Relationships** tab.
 5. Click **Edit trust relationship**. You should see a snippet that looks something that looks like this:
diff --git a/src/connections/destinations/catalog/amazon-lambda/index.md b/src/connections/destinations/catalog/amazon-lambda/index.md
@@ -76,8 +76,8 @@ Using CloudFormation minimizes the setup steps needed, and is Segment's recommen
       ![](images/CloudFormationUploadTemplate.png)
 
    5. Give your stack a name.
-   6. For the **ExternalId** parameter, enter the "External ID" setting in your Segment Lambda destination settings. This should be your **Workspace ID**.
-      * **NOTE:** For security purposes, Segment recommends you to use your Workspace ID as your External ID. If you’re currently using an External ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to:  **Settings > Workspace Settings > ID**.
+   6. For the **ExternalId** parameter, enter the "External ID" setting in your Segment Lambda destination settings.
+      * **NOTE:** For security purposes, Segment will set your Workspace ID as your External ID. If you’re currently using an External ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
    7. The **LambdaARN** parameter corresponds to the **Lambda** setting in your Segment Lambda destination settings.
 
       ![](images/CloudFormationStackDetails.png)
diff --git a/src/connections/destinations/catalog/amazon-personalize/index.md b/src/connections/destinations/catalog/amazon-personalize/index.md
@@ -201,7 +201,7 @@ The following examples show how to configure an AWS Glue job to convert Segment
 **Create AWS Glue ETL Job**
 
 To create an AWS Glue ETL Job:
-1. Navigate to the Glue service in your AWS console.  
+1. Navigate to the Glue service in your AWS console.
 2. Click **Get started** and then click **Jobs** in the left navigation on the Glue console page.
 
     ![](images/GlueJobs.png)
@@ -627,7 +627,7 @@ To create a Personlize campaign:
 
     ![](images/PersonalizeCreateCampaignDash.png)
 
-2. Enter the name for your campaign.  
+2. Enter the name for your campaign.
 3. Select the solution you created above and click **Create campaign**.
 
     ![](images/PersonalizeCreateCampaign.png)
@@ -694,7 +694,7 @@ To create an IAM role:
 > note ""
 > **NOTE:** Your Source ID can be found by navigating to **Settings > API Keys** from your Segment source homepage.
 >
-> If you're using an External ID, for security purposes, Segment recommends you to use your Segment Workspace ID as your External ID. If you use an External ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to:  **Settings > Workspace Settings > ID** in the Segment dashboard.
+> For security purposes, Segment will set your Workspace ID as your External ID. If you are currently using an External ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
 
 ```json
 {
diff --git a/src/connections/destinations/catalog/marketo-v2/images/form-info.png b/src/connections/destinations/catalog/marketo-v2/images/form-info.png
diff --git a/src/connections/destinations/catalog/marketo-v2/index.md b/src/connections/destinations/catalog/marketo-v2/index.md
@@ -59,7 +59,20 @@ Next, create a Service and get Client Secret and Client ID from that Service.
 ----------
 ## Identify
 
-When you call [`Identify`](/docs/connections/spec/identify/), Segment uses [Marketo's REST API](http://developers.marketo.com/rest-api/lead-database/leads/#create_and_update) to upsert leads. We'll map the following spec'd Segment traits to Marketo's standard fields:
+### Cloud-mode
+When you call [`Identify`](/docs/connections/spec/identify/) in Cloud-mode, Segment uses [Marketo's REST API](http://developers.marketo.com/rest-api/lead-database/leads/#create_and_update) to create and update leads server-side.
+
+### Device-mode
+When you call [`Identify`](/docs/connections/spec/identify/) in Device-mode, Segment uses [Marketo's Background Form Submission](https://developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/) to create and update leads client-side.
+
+There are additional steps you must take to send `.identify()` calls in Device-mode.
+
+1. Create an empty form in Marketo. This form will always be hidden and can remain empty as long as the traits you need downstream are mapped in the **Marketo Custom Fields** Destination setting. 
+2. Input the associated **Marketo Form ID** and **Marketo Form URL** in your Marketo V2 Destination settings. This information can be found in Form Actions > Embed Code in the Marketo Design Studio:
+![](images/form-info.png)
+
+### Traits
+Regardless of connection mode, we'll map the following spec'd Segment traits to Marketo's standard fields:
 
 | **Segment Traits**    | **Marketo Standard Fields** |
 | --------------------- | --------------------------- |
@@ -96,15 +109,17 @@ analytics.identify('1234', {
 });
 ```
 
-If you'd like any other traits from your `.identify()` call to update a field in Marketo, you must map them in your Destination settings. **Note:** Custom `address` traits must go in the top level `traits` object, not in the `address` object.
+If you'd like any other traits from your `.identify()` call to update a field in Marketo, you must create custom fields in Marketo and map them in the **Marketo Custom Fields** Destination setting.
 
 ![](images/c1X7nf6wDIX+.png)
 
 - **Segment Trait**. The name of the trait sent in your `.identify()` call.
-- **Marketo Field Name**. The Marketo REST API name for the field. To get the REST API name for your fields in Marketo, click Field Management, then Export Field Names. A spread sheet will download and the first column is the REST API name for your Marketo fields. **Make sure to copy and paste the REST API name exactly. This is case sensitive.**
+- **Marketo Field Name**. The Marketo REST API name for the field. To get the REST API name for your fields in Marketo, click Field Management, then Export Field Names. A spreadsheet will download and the first column is the REST API name for your Marketo fields. **Make sure to copy and paste the REST API name exactly. This is case sensitive.**
 - **Marketo Field Type**. When you are in Field Management, click on the field name in the bar on the right and you'll see the field type.
 ![](images/cubJQKkGLfF+.png)
 
+**Note:** Custom `address` traits must go in the top level `traits` object, not in the `address` object.
+
 ## Track
 
 When you call [`Track`](/docs/connections/spec/track/), Segment maps the event to a pre-defined [Marketo Custom Activity](http://docs.marketo.com/display/public/DOCS/Understanding+Custom+Activities). There are two important things to note when sending `.track()` calls to Marketo:
@@ -233,7 +248,7 @@ There are a few necessary steps that have to be taken to migrate from Segment's
 1. Your Marketo credentials in your Segment Destination settings need to be updated. Our Marketo Destination used Marketo's SOAP API and Marketo V2 uses Marketo's REST API which requires different credentials. Check out the [Getting Started](/docs/connections/destinations/catalog/marketo-v2/#getting-started) guide for what credentials you'll need.
 2. Two custom fields must be created in Marketo: userId and anonymousId. Check out [Getting Started](/docs/connections/destinations/catalog/marketo-v2/#2-you-must-create-a-user-id-and-an-anonymous-id-field-in-marketo) for exact details on how to create these custom fields in Marketo.
 3. `Track` calls must be mapped in your Destination settings. Our Marketo Destination sent `track` calls as a Munchkin Visit WebPage event in Marketo. In Marketo V2, we'll send your track calls to your Marketo Custom Activities. Detailed instructions [here](/docs/connections/destinations/catalog/marketo-v2/#track).
-4. If there are any custom Lead fields that you'd like sent to Marketo in your `Identify` calls, you must add them in your Destination settings. Detailed instructions [here](/docs/connections/destinations/catalog/marketo-v2/#identify).
+4. If there are any custom Lead fields that you'd like sent to Marketo in your `Identify` calls, you must create custom fields in Marketo and add them in your Destination settings. In addition, if you are connecting Marketo V2 in Device-mode, an empty form must be created in Marketo to create and update leads. Detailed instructions [here](/docs/connections/destinations/catalog/marketo-v2/#identify).
 5. Update anything in Marketo that rely on the way V1 sends `.track()` events to be triggered by your custom activities. For example, our V1 Marketo destination sent track events as a "Visit Web Page" event with `/event/<your_event_name>`. So if you a workflow that is triggered by a "Visit Web Page" event where the web page contains `/event/<your_event_name>`, you'll have to swap out the "Visit Web Page" event trigger you have with your Custom Attribute Trigger. In the right side bar, click the "Custom" folder under "Triggers" and select the trigger that you set for your custom activity:
    ![](images/cPD4kP65buG+.png)
 
diff --git a/src/connections/sources/catalog/cloud-apps/regal-voice/index.md b/src/connections/sources/catalog/cloud-apps/regal-voice/index.md
@@ -38,9 +38,13 @@ The table below lists events that Regal Voice sends to Segment. These events app
    <td>A contact was unsubscribed from a marketing channel</td>
   </tr>
   <tr>
-    <td>contact.attribute_edited</td>
+    <td>contact.attribute.edited</td>
     <td>A contact's attributes were edited by an agent</td>
   </tr>
+  <tr>
+    <td>contact.experiment.assigned</td>
+    <td>A contact was assigned to an experiment</td>
+  </tr>
   <tr>
    <td>sms.queued</td>
    <td>An sms was queued to be sent from RegalVoice to contact</td>
@@ -150,6 +154,18 @@ The table below lists events that Regal Voice sends to Segment. These events app
    <td>`ended_at`</td>
    <td>UTC timestamp when the conversation was ended</td>
   </tr>
+  <tr>
+    <td>`experiment_id`</td>
+    <td>Experiment ID</td>
+  </tr>
+  <tr>
+    <td>`experiment_name`</td>
+    <td>Name of experiment</td>
+  </tr>
+  <tr>
+   <td>`experiment_variant`</td>
+   <td>Variant a contact was assigned to in an experiment</td>
+  </tr>
   <tr>
    <td>`from_number`</td>
    <td>Phone number that sent the message</td>
@@ -212,8 +228,9 @@ The table below lists events that Regal Voice sends to Segment. These events app
    <td>`talk_time`</td>
    <td>Duration of conversation (ended_at - started_at)</td>
   </tr>
-  <td>`target_agent_fullname`</td>
-   <td>Full name of the agent who contact (and all contact’s tasks) are assigned to</td>
+  <tr>
+    <td>`target_agent_fullname`</td>
+    <td>Full name of the agent who contact (and all contact’s tasks) are assigned to</td>
   </tr>
   <tr>
    <td>`target_agent_id`</td>
