Merge pull request #2160 from segmentio/develop

Release 21.46.3

Author: rchinn1

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2021-11-17 
+# destination categories last updated 2021-11-18 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2021-11-17 
+# destination data last updated 2021-11-18 
 items:
 - display_name: 2mee
   name: 2mee
@@ -2197,8 +2197,10 @@ items:
       URL Params, GLCID Once Per Session" setting isn't giving the desired
       behavior, this setting will fix it. Note: This setting may cause Amplitude
       to not fully respect the "Prefer Anonymous ID for Device ID" setting
-      (Amplitude may set the device ID once before it gets set to the proper
-      Anonymous ID).
+      (Amplitude may set the device ID upon initialization before it gets set to
+      the proper Anonymous ID) if using Analytics.js 1.0. Consider [updating to
+      Analytics.js 2.0]
+      (https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2/) 
     required: false
     label: Use Amplitude Referral
   - name: useCustomAmplitudeProperties
@@ -14017,15 +14019,6 @@ items:
       include the entire URL including the `//`.
     required: false
     label: Marketo Form URL
-  - name: privateKey
-    type: string
-    defaultValue: ''
-    description: >-
-      **Device Mode Only**: You can find your API Private Key under **Admin >
-      Integration > Munchkin > API Configuration** in your [Marketo
-      account](https://login.marketo.com/).
-    required: false
-    label: API Private Key
   - name: traits
     type: mixed
     defaultValue: []

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2021-11-17 
+# source cateogries last updated 2021-11-18 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2021-11-17 
+# sources last updated 2021-11-18 
 items:
   - display_name: .NET
     slug: net

src/_data/sidenav/main.yml

@@ -7,7 +7,7 @@ sections:
   - path: /getting-started/01-what-is-segment
     title: What is Segment?
   - path: /getting-started/02-simple-install
-    title: A Simple Segment Installation
+    title: A Basic Segment Installation
   - path: /getting-started/03-planning-full-install
     title: Planning a Full Installation
   - path: /getting-started/04-full-install

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

@@ -46,20 +46,19 @@ Actions define which events Segment sends to Google Enhanced Conversions, and th
 2. Click **Add Subscription**, and select **Post Conversion**.
 3. Configure the **Event Trigger**. For example, you can trigger the action whenever the source sends an Event named `Purchase`. Click **Continue** to configure the action fields, skip Testing for now. ![The action fires when it receives an event named Purchase](images/gec_trigger.png)
 4. Enter the Conversion Label. Find it using the instructions in the article [Google Ads conversions](https://support.google.com/tagmanager/answer/6105160?hl=en){:target="_blank"}.
-5. Configure the remaining properties. The **Email** field is not editable. In the default configuration, `properties.email` maps to the Email property in Google Enhanced Conversions. If `properties.email` is unavailable, the destination uses `traits.email` as a fallback.
+5. Configure the remaining properties. 
 6. When you're finished editing the action fields, click **Continue**. Click **Save**.
 7. To test your action, expand the **Test event trigger** section. Segment searches for recent events that match the trigger conditions. If there are no recent events that match the criteria, click **manually enter an event**, and replace the default event data with the following:
 ```json
 {
-	"messageId": "segment-test-message-hkz2b",
-	"timestamp": "2021-08-27T17:32:12.781Z",
+  "messageId": "segment-test-message-hkz2b",
+  "timestamp": "2021-08-27T17:32:12.781Z",
   "context" : {
     "userAgent": "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
   },
-	"type": "track",
-	"email": "[email protected]",
-	"properties": {
-		"email": "[email protected]",
+  "type": "track",
+  "properties": {
+    "email": "[email protected]",
     "orderId": "123",
     "firstName": "Bob John",
     "lastName": "Smith",
@@ -71,9 +70,9 @@ Actions define which events Segment sends to Google Enhanced Conversions, and th
       "postalCode": "94000",
       "country": "USA"
     }
-	},
-	"userId": "test-user-j75yud",
-	"event": "Purchase"
+  },
+  "userId": "test-user-j75yud",
+  "event": "Order Completed"
 }
 ```
 8. Click **Test Event**.
@@ -82,7 +81,7 @@ Actions define which events Segment sends to Google Enhanced Conversions, and th
 11. Click **Save**.
 12. Enable the action with the toggle at the top of the page.
 
+## Available Google Enhanced Conversions Actions
 
-
-
+- Post Conversion
 

src/connections/storage/catalog/aws-s3/index.md

@@ -5,9 +5,6 @@ redirect_from:
 hide-personas-partial: true
 ---
 
-> info "This document is about a destination which is in beta"
-> This means that the AWS S3 with IAM Role Support destination is in active development, and some functionality may change before it becomes generally available.
-
 
 ## Differences between the Amazon S3 destination and the AWS S3 destination
 
@@ -34,9 +31,9 @@ The Segment Tracking API processes data from your sources, and collects the Even
 
 ## Create a new destination
 
-Complete the following steps to configure the AWS S3 Destination with IAM Role Support.
+Complete either [Create an IAM role in the AWS console](#create-an-iam-role-in-the-aws-console) or [Create an IAM role using the AWS CLI](#create-an-iam-role-using-the-aws-cli) to configure the AWS S3 Destination with IAM Role Support.
 
-### Create an IAM role in AWS
+### Create an IAM role in the AWS console
 
 To complete this section, you need access to your AWS dashboard.
 
@@ -94,12 +91,105 @@ To complete this section, you need access to your AWS dashboard.
             ],
             "Resource": "<YOUR_KEY_ARN>"
         }
-    ]
+      ]
     }
     ```
 
 If you have server-side encryption enabled, see the [required configuration](#encryption).
 
+### Create an IAM role using the AWS CLI
+
+To create an IAM role with external ID and with S3 permissions using the AWS CLI, follow the steps below. 
+
+#### Prerequisites
+To create an S3 IAM role, you must first install and configure the AWS CLI on your local machine and create an S3 bucket. Refer to Amazon's documentation, [Getting started with the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html){:target="_blank"} for more information. 
+
+#### Procedure
+1. Copy the following code snippet and save it as a file on your local machine titled `trust-relationship-policy.json`. Replace `<YOUR_WORKSPACE_ID>` with your Segment workspace ID. 
+
+    ```json
+    {
+      "Version": "2012-10-17",
+      "Statement": [
+        {
+          "Sid": "",
+          "Effect": "Allow",
+          "Principal": {
+            "AWS": "arn:aws:iam::595280932656:role/segment-s3-integration-production-access"
+          },
+          "Action": "sts:AssumeRole",
+          "Condition": {
+            "StringEquals": {
+              "sts:ExternalId": "<YOUR_WORKSPACE_ID>"
+            }
+          }
+        }
+      ]
+    }
+    ```
+
+2. Navigate to the folder containing `trust-relationship-policy.json` and run the following command to create your IAM role and attach the trust relationship document, replacing `<YOUR_ROLE_NAME>` with the name you want to give this IAM role:
+
+    ``` python
+    aws iam create-role --role-name <YOUR_ROLE_NAME> --assume-role-policy-document file://trust-relationship-policy.json --description "IAM role for Segment to assume (AWS S3 destination)"
+    ```
+
+3. To verify that the IAM role is created, log into the AWS console and open the IAM Management Console. Under the Trust Relationship tab, there should be a key-value pair: a `sts:ExternalID` key with a value of `your Segment workspace ID`.
+
+4. Copy the following IAM policy, replacing `<YOUR_BUCKET_NAME>` with the name of your S3 bucket, and save it as a file on your local machine titled `iam-policy.json`.
+
+    ```json
+    {
+      "Version": "2012-10-17",
+      "Statement": [
+        {
+          "Sid": "PutObjectsInBucket",
+          "Effect": "Allow",
+          "Action": [
+            "s3:PutObject",
+            "s3:PutObjectAcl"
+          ],
+          "Resource": "arn:aws:s3:::<YOUR_BUCKET_NAME>/segment-logs/*"
+        }
+      ]
+    }
+    ```
+
+5. Navigate to the folder containing `iam-policy.json`, and run the following command to create the IAM policy:
+
+    ``` python
+    aws iam create-policy --policy-name segment-s3-putobject --policy-document file://iam-policy.json --description "Allow Segment to PutObject into S3 destination bucket"
+    ```
+
+6. A successful output has the following format. Take note of the `Arn`, as you'll need it in the next step.
+
+    ``` json
+    {
+        "Policy": {
+            "PolicyName": "segment-s3-putobject",
+            "PolicyId": "AABC1DE2F34GG567H",
+            "Arn": "arn:aws:iam::012345678912:policy/segment-s3-putobject",
+            "Path": "/",
+            "DefaultVersionId": "v1",
+            "AttachmentCount": 0,
+            "PermissionsBoundaryUsageCount": 0,
+            "IsAttachable": true,
+            "CreateDate": "2021-11-11T01:21:00+00:00",
+            "UpdateDate": "2021-11-11T01:21:00+00:00"
+        }
+    }
+
+    ```
+
+7. Run the following command to attach the IAM policy to the IAM role, replacing `<YOUR_ROLE_NAME>` with the name of your role and `<ARN_FROM_STEP_6_OUTPUT>` with the Arn output from the last step:
+
+    ``` python
+    aws iam attach-role-policy --role-name <YOUR_ROLE_NAME> --policy-arn <ARN_FROM_STEP_6_OUTPUT>
+    ```
+
+> info ""
+> To verify that the IAM role is created, navigate to the AWS console and open the IAM Management Console. On the Permissions tab, verify that there is a `segment-s3-putobject` Permissions policy.
+
 
 ### Add the AWS S3 with IAM Role Support Destination
 
@@ -126,7 +216,7 @@ To finish configuration, enable the AWS S3 Destination with IAM Role Support des
 
 To migrate an existing Amazon S3 destination to the AWS S3 with IAM Role Support Destination:
 
-1. Configure the IAM role and IAM policy permissions as described in steps 2 - 4 [above](#create-an-iam-role-in-aws).
+1. Configure the IAM role and IAM policy permissions as described in steps 2 - 4 [above](#create-an-iam-role-in-the-aws-console).
 2. Add the AWS S3 with IAM Role Support Destination and add the AWS Region and IAM role ARN. For the bucket name, enter `<YOUR_BUCKET_NAME>/segment-logs/test`. Enable the destination, and verify data is received at `<YOUR_BUCKET_NAME>/segment-logs/test/segment-logs`. If the folder receives data, continue to the next step. If you don't see log entries, check the trust relationship document and IAM policy attached to the role.
 3. Update the bucket name in the new destination to `<YOUR_BUCKET_NAME>`.
 4. After 1 hour, disable the original Amazon S3 destination.
@@ -158,7 +248,7 @@ Segment groups logs by day, and names them using the following format:
 
     s3://{bucket}/segment-logs/{source-id}/{received-day}/filename.gz
 
-The received-day refers to the UTC date unix timestamp, that the API receives the file, which makes it easy to find all calls received within a certain timeframe.
+The received-day refers to the UTC date Unix timestamp, that the API receives the file, which makes it easy to find all calls received within a certain timeframe.
 
 ## Encryption
 

src/connections/storage/catalog/google-cloud-storage/index.md

@@ -9,7 +9,8 @@ redirect_from: '/connections/destinations/catalog/google-cloud-storage/'
 
 The Google Cloud Storage (GCS) destination puts the raw logs of the data Segment receives into your GCS bucket. The data is copied into your bucket at least every hour. You might see multiple files over a period of time depending on how much data is copied.
 
-Keep in mind that GCS works differently from most of our destinations. Using a destinations selector like the [integrations object](https://segment.com/docs/connections/spec/common/#integrations) does not affect events in the case of GCS.
+> warning ""
+> The Google Cloud Storage destination works differently than other destinations in Segment. Segment sends **all** data from a Personas source to GCS during the sync process, not only the connected audiences and traits. Using a destinations selector like the [integrations object](/docs/connections/spec/common/#integrations) doesn't affect the events events sent to GCS.
 
 **Note**: The GCS destination is currently in beta, and does not support product features such as deletions, replays, or surfacing errors in the UI.
 

src/connections/storage/data-lakes/sync-history.md

@@ -23,7 +23,7 @@ To access the Sync History page from the Segment app, open the **My Destinations
 ## Health
 The health tab provides an overview of the rows that synced to your data lake both today and each day for the last 30 days. 
 
-The bar chart, 'Daily Synced Rows,' shows an overview of the rows synced for each of the last 30 days. Hovering over a date shows the number of rows that were synced for that day. Selecting a date from the bar chart opens the Daily Row Volume table, which provides a breakdown of which collections synced, how many rows from each collection synced, and the percentage of all synced rows from each collection .
+The bar chart, 'Daily Synced Rows,' shows an overview of the rows synced for each of the last 30 days. Hovering over a date shows the number of rows that were synced for that day. Selecting a date from the bar chart opens the Daily Row Volume table, which provides a breakdown of which collections synced, how many rows from each collection synced, and the percentage of all synced rows from each collection.
 
 The Daily Row Volume table contains the following information:
 * **Collections:** The name of each collection of properties synced to the data lake