Merge branch 'master' into DOC-207

Author: stayseesong

.vale.ini

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

scripts/ignore.sh

@@ -6,8 +6,13 @@ log=$(env -i git log -1 --pretty=%B)
 # run a series of checks for common reasons that we shouldn't preview build.
 # if no checks match, exit with code 1 to run the build
 
+# Force a build
+if echo $log | grep -1 'netlify\-build'; then
+echo "Force build becuase Netlify is a benevolent overseer"
+exit 1
+
 # ignore for simple typo fixes
-if echo "$log" | grep -q 'typo'; then
+elif echo "$log" | grep -q 'typo'; then
 echo "Build ignored because 'typo' is in the commit message."
 exit
 # ignore link / url updates
@@ -23,7 +28,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/products.yml

@@ -106,3 +106,11 @@ items:
     team: true
     business: false
     add-on: false
+- product_display_name: Journeys
+  slug: journeys
+  plan-note: "Journeys is available to Personas Advanced customers"
+  plans:
+    free: false
+    team: false
+    business: true
+    add-on: true

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/actions.md

@@ -46,9 +46,9 @@ You can add or remove, disable and re-enable, and rename individual actions from
 
 From the edit screen you can change the action’s name, subscription criteria, and mapping, and toggle it on or off. See [Customizing mappings](#customizing-mappings) for more information.
 
-<!-- TODO screenshot-->
+![](/docs/connections/destinations/catalog/actions-amplitude/images/amplitude-actions-tab.png)
 
-## Disable a destination actioon
+## Disable a destination action
 If you find that you need to stop an action from running, but don’t want to delete it completely, you can click the action to select it, then click the toggle next to the action’s name to disable it. This takes effect within minutes, and disables the action until you reenable it.
 
 ## Delete a destination action