Merge branch 'master' into DOC-188_Deploy-Journeys

Author: markzegarelli

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2021-06-01 
+# destination categories last updated 2021-06-08 
 items:
 - display_name: Email Marketing
   slug: email-marketing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination data last updated 2021-06-04 
+# destination data last updated 2021-06-08 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -6234,6 +6234,17 @@ items:
     required: false
     description: 'If true, timestamps are converted to Unix Time.'
     settings: []
+  - name: datacenter
+    display_name: Customer.io Datacenter
+    type: SELECT
+    deprecated: false
+    required: false
+    select_validators:
+      select_options:
+      - us
+      - eu
+    description: Choose your Customer.io gateway for data residency.
+    settings: []
   - name: siteId
     display_name: Site ID
     type: STRING
@@ -13035,13 +13046,17 @@ items:
     deprecated: false
     required: false
     description: >-
-      If this option is enabled, we will never set $id field to your `userId`
-      when you call `.identify()` or `.track()`. Instead, we will only set a
-      custom attribute `id` and only set $email as the primary identifier with
-      your `traits.email` or `properties.email`. You should be careful when
-      enabling this option and understand its full implications. This should
-      only be enabled if you are experiencing an issue with duplicate profiles
-      being created inside Klaviyo.
+      This option is enabled by default to ensure duplicate profiles are not
+      being created inside of Klaviyo. When enabled, we will never set $id field
+      to your `userId` when you call `.identify()` or `.track()`. Instead, we
+      will only set a custom attribute `id` and only set $email as the primary
+      identifier with your `traits.email` or `properties.email`. 
+
+
+      Klaviyo will not record events/profiles if there isn’t an email address
+      associated with that customer.
+
+      Impact is fewer events/profiles recorded in Klaviyo as a result.
     settings: []
   - name: privateKey
     display_name: Enter your Private Key
@@ -21797,7 +21812,7 @@ items:
   url: connections/destinations/catalog/smartlook
   description: Qualitative analytics for websites
   hidden: false
-  status: PUBLIC_BETA
+  status: PUBLIC
   previous_names:
   - Smartlook
   logo:

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2021-06-01 
+# source cateogries last updated 2021-06-08 
 items:
   - display_name: Server
     slug: server

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# sources last updated 2021-06-01 
+# sources last updated 2021-06-08 
 items:
   - display_name: .NET
     slug: net

src/connections/destinations/catalog/amazon-kinesis-firehose/index.md

@@ -12,8 +12,8 @@ This document was last updated on February 05, 2020. If you notice any gaps, out
 
   1. Create at least one Kinesis Firehose delivery stream. You can follow these [instructions](http://docs.aws.amazon.com/firehose/latest/dev/basic-create.html) to create a new delivery stream.
   2. Create an IAM policy.
-	  - Sign in to the [Identity and Access Management (IAM) console](https://console.aws.amazon.com/iam/).
-	  - Follow [these instructions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html#access_policies_create-json-editor) to create an IAM policy on the JSON to allow Segment permission to write to your Kinesis Firehose Stream.
+	  1. Sign in to the [Identity and Access Management (IAM) console](https://console.aws.amazon.com/iam/).
+	  2. Follow [these instructions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html#access_policies_create-json-editor) to create an IAM policy on the JSON to allow Segment permission to write to your Kinesis Firehose Stream.
      - Use the following template policy in the **Policy Document** field. Be sure to change the `{region}`, `{account-id}` and `{stream-name}` with the applicable values.
 
 
@@ -36,16 +36,16 @@ This document was last updated on February 05, 2020. If you notice any gaps, out
 
 
   3. Create an IAM role.
-	  - Follow [these instructions](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user.html#roles-creatingrole-user-console) to create an IAM role to allow Segment permission to write to your Kinesis Firehose Stream.
-	  - When prompted to enter an Account ID, enter `595280932656`.
-	  - Select the checkbox to enable **Require External ID**.
-	  - Enter your Segment Source ID as the **External ID**. This can be found in Segment by navigating to **Connections > Sources** and choosing the source you want to connect to your Kinesis Firehose destination. Click the **Settings** tab and choose **API Keys**.  
+	  1. Follow [these instructions](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user.html#roles-creatingrole-user-console) to create an IAM role to allow Segment permission to write to your Kinesis Firehose Stream.
+	  2. When prompted to enter an Account ID, enter `595280932656`.
+	  3. Select the checkbox to enable **Require External ID**.
+	  4. Enter your Segment Source ID as the **External ID**. This can be found in Segment by navigating to **Connections > Sources** and choosing the source you want to connect to your Kinesis Firehose destination. Click the **Settings** tab and choose **API Keys**.  
     - **Note:** If you have multiple sources using Kinesis, enter one of their source IDs here for now and then follow the procedure outlined in the [Multiple Sources](#best-practices) section at the bottom of this doc once you’ve completed this step and saved your IAM role.
-      - When adding permissions to your new role, find the policy you created in step 2 and attach it.
+      5. When adding permissions to your new role, find the policy you created in step 2 and attach it.
 
 4. Create a new Kinesis Firehose Destination.
-    - In the Segment source that you want to connect to your Kinesis Firehose destination, click **Add Destination**.
-    - Search and select the **Amazon Kinesis Firehose** destination and enter details for [these settings options](#settings).
+    1. In the Segment source that you want to connect to your Kinesis Firehose destination, click **Add Destination**.
+    2. Search and select the **Amazon Kinesis Firehose** destination and enter details for [these settings options](#settings).
 
 ## Page
 Take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:

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

@@ -14,7 +14,7 @@ Segment's Amplitude destination code is open source and available on GitHub. Fee
 - [Android](https://github.com/segment-integrations/analytics-android-integration-amplitude)
 
 > success ""
-> **New Amplitude destination available**: Segment's [Destination Actions](/docs/connections/destinations/actions/) allow you to explicitly set up your Amplitude mapping, and configure which events the mappings apply to. See [Amplitude Actions destination](/docs/connections/destinations/catalog/amplitude-actions/) for more information.
+> **New Amplitude destination available**: Segment's [Destination Actions](/docs/connections/destinations/actions/) allow you to explicitly set up your Amplitude mapping, and configure which events the mappings apply to. See [Amplitude Actions destination](/docs/connections/destinations/catalog/actions-amplitude/) for more information.
 
 
 

src/guides/duplicate-data.md

@@ -2,10 +2,10 @@
 title: How does Segment handle duplicate data?
 ---
 
-Segment has a special de-duplication service that sits just behind the `api.segment.com` endpoint, and attempts to drop duplicate data. However, that de-duplication api has to hold the entire set of events in memory in order to know whether or not it has seen that event already. Segment stores 24 hours worth of event `message_id`s. This means Segment can de-duplicate any data that appears within a 24 hour rolling window.
+Segment has a special de-duplication service that sits just behind the `api.segment.com` endpoint, and attempts to drop duplicate data. However, that de-duplication service has to hold the entire set of events in memory in order to know whether or not it has seen that event already. Segment stores 24 hours worth of event `message_id`s. This means Segment can de-duplicate any data that appears within a 24 hour rolling window.
 
-An important point remember is that Segment de-duplicates on the event's `message_id`, _not_ on the contents of an event payload. So if you aren't generating `message_id`s for each event, or are trying to deduplicate data over a longer period than 24 hours, Segment does not have a built-in way to de-duplicate data.
+An important point to remember is that Segment de-duplicates on the event's `message_id`, _not_ on the contents of an event payload. So if you aren't generating `message_id`s for each event, or are trying to de-duplicate data over a longer period than 24 hours, Segment does not have a built-in way to de-duplicate data.
 
-Since the api layer is de-duping during this window, duplicate events that are further than 24 hours apart from one another must be de-duped in the Warehouse. Segment also dedupes messages going into a Warehouse based on the `message_id`, which is the `id` column in a Segment Warehouse. Note that in these cases you will see duplications in end tools as there is no additional layer prior to sending the event to downstream tools.
+Since the API layer is de-duplicating during this window, duplicate events that are further than 24 hours apart from one another must be de-duplicated in the Warehouse. Segment also de-duplicates messages going into a Warehouse based on the `message_id`, which is the `id` column in a Segment Warehouse. Note that in these cases you will see duplications in end tools as there is no additional layer prior to sending the event to downstream tools.
 
 Keep in mind that Segment's libraries all generate `message_id`s for you for each event payload, with the exception of the Segment HTTP API, which assigns each event a unique `message_id` when the message is ingested. You can override these default generated IDs and manually assign a `message_id` if necessary.