Merge branch 'master' into fix-typoo

Author: markzegarelli

.vale.ini

@@ -4,3 +4,4 @@ Vocab = Docs
 
 [*.md]
 BasedOnStyles = write-good, segment
+TokenIgnores = ({% .* %})

scripts/ignore.sh

@@ -23,7 +23,7 @@ elif echo "$log" | grep -q 'dependabot'; then
 echo "Ignoring dependabot update"
 exit
 # ignore when master is merged into a branch
-elif echo "$log" | grep -q 'Merge branch \SMaster\S'; then
+elif echo "$log" | grep -q 'Merge branch \Smaster\S'; then
 echo "Build ignored because it's only an update from the main branch."
 exit
 else

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/_data/sidenav/main.yml

@@ -266,21 +266,21 @@ sections:
         title: Overview
       - path: /personas/audiences/account-audiences
         title: Account-level Audiences
-  # - section_title: Journeys
-  #   slug: /personas/journeys
-  #   section:
-  #     - path: /personas/journeys
-  #       title: Journeys Overview
-  #     - path: /personas/journeys/build-journey
-  #       title: Build a Journey
-  #     - path: /personas/journeys/send-data
-  #       title: Send Data to Destinations
-  #     - path: /personas/journeys/faq-best-practices
-  #       title: Journeys Best Practices and FAQ
-  #     - path: /personas/journeys/use-cases
-  #       title: Example Journeys Use Cases
-  #     - path: /personas/journeys/key-terms
-  #       title: Journeys Glossary
+  - section_title: Journeys
+    slug: /personas/journeys
+    section:
+      - path: /personas/journeys
+        title: Journeys Overview
+      - path: /personas/journeys/build-journey
+        title: Build a Journey
+      - path: /personas/journeys/send-data
+        title: Send Data to Destinations
+      - path: /personas/journeys/faq-best-practices
+        title: Journeys Best Practices and FAQ
+      - path: /personas/journeys/use-cases
+        title: Example Journeys Use Cases
+      - path: /personas/journeys/key-terms
+        title: Journeys Glossary
   - path: /personas/using-personas-data
     title: Using Personas data
   - path: /personas/warehouses

src/connections/destinations/catalog/amplitude-actions/index.md renamed to src/connections/destinations/catalog/actions-amplitude/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/amazon-kinesis-firehose/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.