Merge branch 'master' into littledata-docs-update

Author: markzegarelli

src/_data/catalog/overrides-list.yml

@@ -1,3 +1,5 @@
 items:
   - hubspot
   - iterable
+  - google-ads-gtag
+  - klaviyo

src/_data/catalog/overrides.yml

@@ -16,7 +16,7 @@ items:
       mobile: true
       server: true
     summary: >-
-      is available in device-mode for Analytics.js only, and is availble in cloud-mode for Mobile and Server sources.
+      is available in device-mode for Analytics.js only, and is availble in cloud-mode for Mobile and Server sources. Page calls are supported from Device-mode connections only.
     cmode_type: mixed
     case: '6'
 - slug: iterable
@@ -37,3 +37,26 @@ items:
       accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.
     cmode_type: mixed
     case: '5'
+- 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'

src/_data/catalog/warehouse.yml

@@ -89,7 +89,7 @@ items:
   name: catalog/warehouse/data-lakes
   description: ''
   url: connections/storage/catalog/data-lakes
-  status: PUBLIC_BETA
+  status: PUBLIC
   logo:
     url: 'https://cdn.filepicker.io/api/file/YR7dKXAiQWyYvBiVOZNX'
   mark:

src/_data/sidenav/main.yml

@@ -226,8 +226,6 @@ sections:
     title: Locate Your Write Key
   - path: /connections/integration_error_codes
     title: Integration Error Codes
-  - path: /connections/schema-unique-limits
-    title: Segment Schema Limits
   - path: /connections/rate-limits
     title: Rate Limits and SLA
   - path: /connections/data-residency

src/_includes/content/destination-footer.md

@@ -5,6 +5,8 @@
 
 {% if currentIntegration.platforms.server == true %}
 {% unless page.hide-personas-partial == true %}
+{% assign overridesList = site.data.catalog.overrides-list.items %}
+
 
 ## Personas
 
@@ -69,10 +71,14 @@ Segment lets you change these destination settings from the Segment app without
 ## Adding {{ currentIntegration.display_name }} to the integrations object
 
 To add {{ currentIntegration.display_name }} to the `integrations` JSON object (for example, [to filter data from a specific source](/docs/guides/filtering-data/#filtering-with-the-integrations-object)), use one of the following valid names for this integration:
+{% if page.name-override %}
+{% assign currentIntegration = site.data.catalog.overrides.items | where: "slug", currentSlug | first %}
+{% endif %}
 
 {% for valid_name in currentIntegration.previous_names %}
 - {{ valid_name }}
 {% endfor %}
+
 {% endunless %}
 {% endif %}
 

src/_includes/content/whats-a-warehouse.md

@@ -1,3 +1,3 @@
-A warehouse is a central repository of data collected from one or more sources. This is what commonly comes to mind you think about a relational database: structured data that fits neatly into rows and columns.
+A warehouse is a central repository of data collected from one or more sources. This is what commonly comes to mind when you think about a relational database: structured data that fits neatly into rows and columns.
 
-In Segment, a Warehouse is a special type destination. Instead of streaming data to the destination all the time, we load data to them in bulk at a regular intervals. When we load data, we insert and update events and objects, and automatically adjust their schema to fit the data you've sent to Segment.
+In Segment, a Warehouse is a special type of destination. Instead of streaming data to the destination all the time, we load data to them in bulk at regular intervals. When we load data, we insert and update events and objects, and automatically adjust their schema to fit the data you've sent to Segment.

src/_sass/components/_markdown.scss

@@ -293,7 +293,7 @@
 
 }
 
-a[target="_blank"]:after{
+a[target="_blank"]:not(.reference-button):after{
   content: url("/docs/images/external-link-alt-solid.svg");
   margin-left: 4px;
 }

src/config-api/api-design.md

@@ -43,7 +43,7 @@ You can manage each resource using standard methods:
 | PermissionDenied   | 403 Forbidden             | 7    | An access token with `write` scope is required for the Create, Update and Delete methods              |
 | Not Found          | 404 Not Found             | 5    | The request or resource could not be found. Either the request method or path is incorrect, or the resource does not exist in this workspace (sometimes because of a typo). |
 | Already Exists     | 409 Conflict              | 6    | A resource (e.g. source) already exists with the given name                                           |
-| Resource Exhausted | 429 Too Many Requests     | 8    | The 60 req / sec rate limit was exhausted                                                             |
+| Resource Exhausted | 429 Too Many Requests     | 8    | The 200 req / min rate limit was exhausted                                                             |
 | Internal           | 500 Internal Server Error | 13   | Segment encountered an error processing the request                                                   |
 | Unimplemented      | 501 Not Implemented       | 12   | The method is not supported or implemented                                                            |
 | Unavailable        | 503 Service Unavailable   | 14   | The API is down                                                                                       |

src/connections/destinations/add-destination.md

@@ -88,14 +88,8 @@ Each destination can also have destination settings. These control how Segment t
 
 ## Connecting one source to multiple instances of a destination
 
-<!-- LR: 03/04/21 - hiding this for now since it's in limited rollout.
 > note ""
 > Multiple-destination support is available for all Segment customers on all plan tiers.
--->
-
-
-> info ""
-> Support for connecting to multiple instances of a destination is in public preview. To use this, you must agree to the [(1) Segment First Access](https://segment.com/legal/first-access-beta-preview/) and Beta Terms and Conditions and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/). The feature is being released to different tiers over time. If you see an error message that you can’t connect to multiple instances of the same destination, it is not available yet in your workspace but is coming soon.
 
 Segment allows you to connect a source to multiple instances of a destination. You can use this to set up a single Segment source that sends data into different instances of your analytics and other tools.
 
@@ -187,7 +181,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/)