Merge branch 'master' into DOC-270

stayseesong · web-flow · commit 9794ac916716 · 2021-07-23T11:15:30.000-07:00
diff --git a/src/_data/catalog/overrides-list.yml b/src/_data/catalog/overrides-list.yml
@@ -2,3 +2,4 @@ items:
   - hubspot
   - iterable
   - google-ads-gtag
+  - klaviyo
diff --git a/src/_data/catalog/overrides.yml b/src/_data/catalog/overrides.yml
@@ -40,3 +40,23 @@ items:
 - slug: google-ads-gtag
   previous_names:
   - Google AdWords New
+- slug: klaviyo
+  display_name: Klaviyo
+  components:
+  - code: 'https://github.com/segment-integrations/analytics.js-integration-klaviyo'
+    type: browser
+  - code: 'https://github.com/segmentio/integrations/tree/master/integrations/klaviyo'
+    type: server
+  connection_modes:
+    device:
+      web: true
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: true
+      server: true
+    summary: >-
+      accepts data in cloud-mode from web and mobile sources, and can accept data in device-mode from Analytics.js sources.
+    cmode_type: mixed
+    case: '10'
diff --git a/src/_sass/components/_markdown.scss b/src/_sass/components/_markdown.scss
@@ -293,7 +293,7 @@
 
 }
 
-a[target="_blank"]:after:not(.reference-button){
+a[target="_blank"]:not(.reference-button):after{
   content: url("/docs/images/external-link-alt-solid.svg");
   margin-left: 4px;
 }
diff --git a/src/connections/destinations/add-destination.md b/src/connections/destinations/add-destination.md
@@ -187,7 +187,6 @@ For the following destinations, a single source can connect to up to 10 instance
 - [ActiveCampaign](/docs/connections/destinations/catalog/activecampaign/)
 - [Akita](/docs/connections/destinations/catalog/akita/)
 - [All Aboard](/docs/connections/destinations/catalog/all-aboard/)
-- [Amazon EventBridge](/docs/connections/destinations/catalog/amazon-eventbridge/)
 - [Amazon Kinesis](/docs/connections/destinations/catalog/amazon-kinesis/)
 - [Amazon Kinesis Firehose](/docs/connections/destinations/catalog/amazon-kinesis-firehose/)
 - [Amazon Lambda](/docs/connections/destinations/catalog/amazon-lambda/)
diff --git a/src/connections/destinations/catalog/klaviyo/index.md b/src/connections/destinations/catalog/klaviyo/index.md
@@ -1,41 +1,41 @@
 ---
 title: Klaviyo Destination
 rewrite: true
+cmode-override: true
 ---
 
 [Klaviyo](https://www.klaviyo.com/features/overview) is a powerful email platform focused on ecommerce that helps companies make more money. It supports segmentation based on category and event triggers like product bought, page viewed, email engagement, or amount spent.
 
-It measures opens, clicks, revenue generated, breakdown of generated revenue based on custom attributes (like type of campaign or amount gained per recipient), and provides trend reports, cohort analysis, and subscriber growth
+It measures opens, clicks, revenue generated, breakdown of generated revenue based on custom attributes (like campaign type or amount gained per recipient), and provides trend reports, cohort analysis, and subscriber growth
 
-Ultimately, Klaviyo lets you send personalized newsletters, automates triggered emails, product recommendations, welcome campaigns, order announcements, push notifications and sync your data to facebook custom audiences.
+Ultimately, Klaviyo lets you send personalized newsletters, automates triggered emails, product recommendations, welcome campaigns, order announcements, push notifications and sync your data to Facebook custom audiences.
 
-Are you trying to set up Klaviyo as an Event Source to get data into your warehouse or other downstream tools? Go [here](https://segment.com/docs/connections/sources/catalog/cloud-apps/klaviyo/).
-
-This document was last updated on September 6, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
+To configure Klaviyo as an Event Source to get data into your warehouse or other downstream tools, see the [Klaviyo Source](/docs/connections/sources/catalog/cloud-apps/klaviyo/) documentation.
 
 ## Getting Started
 
 {% include content/connection-modes.md %}
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Klaviyo" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Navigate to your [Account > Settings > API Keys](https://www.klaviyo.com/account#api-keys-tab) in the Klaviyo's UI and copy your "API Key" into the Segment Settings UI.
-5. **Note:** Private API Key is required to use the List API. You can find this by going to Klaviyo's UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab) in order to generate a Private API Key and copy it into the Segment Settings UI.
+3. Navigate to your [Account > Settings > API Keys](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"} in the Klaviyo's UI and copy your "API Key" into the Segment Settings UI.
+4. **Note:** Klaviyo requires the Private API Key to use the List API. You can find this by going to Klaviyo's UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab){:target="_blank"}  to generate a Private API Key and copy it into the Segment Settings UI.
 
 
 ## 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:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 
 ```
 analytics.page();
 ```
 
-**NOTE**: `page` calls are only supported client-side on analytics.js.
+> info ""
+> `page` calls are supported client-side on analytics.js.
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```
 analytics.identify({
@@ -49,41 +49,42 @@ analytics.identify({
 
 ### Client side Identify
 
-When you call `identify` on analytics.js, we call Klaviyo's `identify` with the `traits` object. We augment the `traits` object to have `traits.$id` be the `userId` since Klaviyo takes the user ID on the `traits` object itself.
+When you call `identify` on analytics.js, Segment calls Klaviyo's `identify` with the `traits` object. Segment then augments the `traits` object to have `traits.$id` be the `userId` since Klaviyo takes the user ID on the `traits` object itself.
 
-**Note:** When sending data to Klaviyo using `analytics.js`, an initial `page` call is required. By default, this is already added in your [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet).
+> info ""
+> When you send data to Klaviyo using `analytics.js`, an initial `page` call is required. By default, this is already added in your [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet).
 
-We will map the following Segment spec'd traits to Klaviyo [special people properties](http://www.klaviyo.com/docs):
+The following Segment spec'd traits map to Klaviyo [special people properties](http://www.klaviyo.com/docs):
 
-| **Segment Traits | Klaviyo Traits** |
-|  ------ | ------- |
-| `userId` | `$id` |
-| `email` | `$email` |
-| `phoneNumber` | `$phone_number` |
-| `firstName` | `$first_name` |
-| `lastName` | `$last_name` |
-| `title` | `$title` |
+| Segment Traits | Klaviyo Traits  |
+| -------------- | --------------- |
+| `userId`       | `$id`           |
+| `email`        | `$email`        |
+| `phoneNumber`  | `$phone_number` |
+| `firstName`    | `$first_name`   |
+| `lastName`     | `$last_name`    |
+| `title`        | `$title`        |
 
 ### Server side Identify
 
-When you call `identify` from one of our mobile or server-side libraries, we will create/update a Klaviyo person with the `traits` you provide in the `identify`.
-
-If your `userId` is an email, or you provide an email in `traits.email`, we'll send it as the `$email` property to Klaviyo. We will map the following Segment spec'd traits to Klaviyo [special people properties](http://www.klaviyo.com/docs):
-
-| **Segment Traits | Klaviyo Properties** |
-|  ------ | ------- |
-| `userId` | `$id` |
-| `email` | `$email` |
-| `phoneNumber` | `$phone_number` |
-| `organization` | `$organization` |
-| `firstName` | `$first_name` |
-| `lastName` | `$last_name` |
-| `title` | `$title` |
-| `city` | `$city` |
-| `region` or `state` | `$region` |
-| `country` | `$country` |
-| `timezone` | `$timezone` |
-| `zip` | `$zip` |
+When you call `identify` from a mobile or server-side library, Segment creates or updates a Klaviyo person with the `traits` you provide in the `identify`.
+
+If your `userId` is an email, or you provide an email in `traits.email`, Segment sends it as the `$email` property to Klaviyo. The following Segment spec'd traits map to Klaviyo [special people properties](http://www.klaviyo.com/docs):
+
+| Segment Traits      | Klaviyo Properties |
+| ------------------- | ------------------ |
+| `userId`            | `$id`              |
+| `email`             | `$email`           |
+| `phoneNumber`       | `$phone_number`    |
+| `organization`      | `$organization`    |
+| `firstName`         | `$first_name`      |
+| `lastName`          | `$last_name`       |
+| `title`             | `$title`           |
+| `city`              | `$city`            |
+| `region` or `state` | `$region`          |
+| `country`           | `$country`         |
+| `timezone`          | `$timezone`        |
+| `zip`               | `$zip`             |
 
 #### Enforce Email as Primary Identifier
 
@@ -161,15 +162,15 @@ We will also map the following Segment spec'd properties to Klaviyo's [special p
 The below table shows the out of the box mappings in our integration between our e-commerce spec and Klaviyo's spec:
 
 | **Segment Ecommerce Spec | Klaviyo Standard Event** |
-|  ------ | ------- |
-| `Order Completed` | `Ordered Product` |
+| ------------------------ | ------------------------ |
+| `Order Completed`        | `Ordered Product`        |
 
 The below table shows the parameter mappings in our integration between Order Completed properties and and Klaviyo's standard properties:
 
-| **Segment Properties | Klaviyo Properties** |
-|  ------ | ------- |
-| `revenue` | `$value` |
-| `eventId` or `orderId` | `$event_id` |
+| **Segment Properties   | Klaviyo Properties** |
+| ---------------------- | -------------------- |
+| `revenue`              | `$value`             |
+| `eventId` or `orderId` | `$event_id`          |
 
 #### Order Completed
 
diff --git a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md
@@ -3,7 +3,7 @@ title: Upgrade to Analytics.js 2.0
 strat: ajs
 ---
 
-Analytics.js 2.0 is fully backward compatible with Analytics.js Classic when using the default Segment snippet. To upgrade your sources, follow the manual upgrade steps below, or see the schedule for automatic migration. As with all upgrades, Segment recommends that you start development on a non-production source to test the upgrade process and outcome, prior to upgrading your production sources.
+Analytics.js 2.0 is fully backward compatible with Analytics.js Classic when you use the default Segment snippet in a standard implementation. To upgrade your sources, follow the manual upgrade steps below, or see the schedule for automatic migration. As with all upgrades, Segment recommends that you start development on a non-production source to test the upgrade process and outcome, prior to upgrading your production sources.
 
 ## Manual upgrade
 
diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md
@@ -255,7 +255,7 @@ Other libraries only collect `context.library`, any other context variables must
 | library.name             |     √        |     √         |      √            |
 | library.version          |     √        |     √         |      √            |
 | ip*                      |     √        |     √         |      √            |
-| locale                   |              |     √         |      √            |
+| locale                   |     √        |     √         |      √            |
 | location.latitude        |              |               |                   |
 | location.longitude       |              |               |                   |
 | location.speed           |              |               |                   |
@@ -282,7 +282,7 @@ Other libraries only collect `context.library`, any other context variables must
 
 ## Integrations
 
-A dictionary of destination names that the message should be sent to. `'All'` is a special key that applies when no key for a specific destination is found.
+A dictionary of destination names that the message should be sent to. `'All'` is a special key that applies when no key for a specific destinatio n is found.
 
 Integrations defaults to the following:
 
diff --git a/src/partners/subscriptions/build-functions.md b/src/partners/subscriptions/build-functions.md
@@ -5,6 +5,10 @@ redirect_from: '/partners/build-functions/'
 
 Subscription Functions allow you to write custom JavaScript code that sends Segment Event Data to existing APIs. This guides explains how to write custom functions.
 
+> note ""
+> **NOTE:** On July 31, 2021 support for building Subscription Functions will be removed from Developer Center. You may continue building a Subscription Webhook. Segment is committed to improving the Developer Center experience with Developer Center 2.0, which will offer a more holistic approach to building on Segment. If you’re interested in joining the beta in the coming months, please fill out [this form](https://airtable.com/shrvZzQ6NTTwsc6rQ){:target="_blank"}.
+
+
 ## Getting Started
 
 Review the steps outlined in the [Developer Center Overview](/docs/partners). This document outlines specific details for Step 4 as it relates to building a Subscription Function.
diff --git a/src/partners/subscriptions/index.md b/src/partners/subscriptions/index.md
@@ -21,6 +21,9 @@ Review the steps outlined in the [Developer Center Overview](/docs/partners). Th
 
 ## Build & Test
 
+> note ""
+> **NOTE:** On July 31, 2021 support for building Subscription Functions will be removed from Developer Center. You may continue building a Subscription Webhook. Segment is committed to improving the Developer Center experience with Developer Center 2.0, which will offer a more holistic approach to building on Segment. If you’re interested in joining the beta in the coming months, please fill out [this form](https://airtable.com/shrvZzQ6NTTwsc6rQ){:target="_blank"}.
+
 You can subscribe to customer data in two ways:
 
 1. **[Webhook](/docs/partners/subscriptions/build-webhook)**: Build a new HTTP service that receives Webhook POSTs from Segment.
diff --git a/vale-styles/Vocab/Docs/accept.txt b/vale-styles/Vocab/Docs/accept.txt
@@ -46,3 +46,4 @@ measurability
 Lightbox
 gmail
 (?:P|p)endo
+(?:K|k)laviyo

Original file line number	Diff line number	Diff line change
`@@ -293,7 +293,7 @@`
`293`	`293`
`294`	`294`	`}`
`295`	`295`
`296`		`-a[target="_blank"]:after:not(.reference-button){`
	`296`	`+a[target="_blank"]:not(.reference-button):after{`
`297`	`297`	`content: url("/docs/images/external-link-alt-solid.svg");`
`298`	`298`	`margin-left: 4px;`
`299`	`299`	`}`