Merge branch 'master' into DOC-226

stayseesong · web-flow · commit 88773220e413 · 2021-07-20T17:04:32.000-07:00
diff --git a/src/_data/catalog/overrides-list.yml b/src/_data/catalog/overrides-list.yml
@@ -1,3 +1,4 @@
 items:
   - hubspot
   - iterable
+  - google-ads-gtag
diff --git a/src/_data/catalog/overrides.yml b/src/_data/catalog/overrides.yml
@@ -37,3 +37,6 @@ 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
diff --git a/src/_includes/content/destination-footer.md b/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 %}
 
diff --git a/src/_includes/content/whats-a-warehouse.md b/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.
diff --git a/src/connections/destinations/catalog/amazon-lambda/index.md b/src/connections/destinations/catalog/amazon-lambda/index.md
@@ -1,6 +1,7 @@
 ---
 title: Amazon Lambda Destination
 rewrite: true
+hide-personas-partial: true
 ---
 
 Segment makes it easy to send your data to AWS Lambda (and lots of other destinations). Once you collect your data using Segment's [open source libraries](/docs/connections/sources/catalog/), Segment translates and routes your data to AWS Lambda in the format it can use.
diff --git a/src/connections/destinations/catalog/google-ads-gtag/index.md b/src/connections/destinations/catalog/google-ads-gtag/index.md
@@ -3,9 +3,10 @@ title: 'Google Ads (Gtag) Destination'
 beta: true
 redirect_from: '/connections/destinations/catalog/google-adwords-new/'
 strat: google
+name-override: true
 ---
 
-## Before you begin...
+## Before you begin
 
 If you're using the [new Google Ads (Gtag) experience](https://support.google.com/adwords/answer/6095821?hl=en&ref_topic=3165803), you can enable the **Google Ads (Gtag)** Destination (previously called "Google Adwords New") in the Segment catalog. The new Google Ads uses a Global Site Tag (Gtag) and event snippets.
 
diff --git a/src/connections/destinations/catalog/pendo/index.md b/src/connections/destinations/catalog/pendo/index.md
@@ -5,7 +5,7 @@ title: Pendo Destination
 
 [Pendo](http://www.pendo.io/) is a product cloud that helps product teams deliver software users love. With Pendo, product teams can understand product usage, collect feedback, measure NPS, onboard users, and announce new features in app—all without requiring engineering resources.
 
-This destination is maintained by Pendo. For any issues with the destination, [contact the Pendo Support team](https://help.pendo.io/).
+Pendo maintains this destination. For any issues with the destination, [contact the Pendo Support team](https://help.pendo.io/).
 
 ## Getting Started
 
@@ -19,21 +19,21 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j
 
  This pulls in all page and click events without needing to make additional method calls.
 
-### Server
+### Cloud-mode configuration
 
-If you are implementing server-side, follow the steps above to add Pendo continue with steps below to add a Webhook destination:
+To add the Pendo destination using Cloud-mode, use the [Webhooks](/docs/connections/destinations/catalog/webhooks) destination to enable Segment to send data to Pendo through a webhook.
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Webhooks" in the Catalog, select it, and choose which of your Javascript sources to connect the destination to.
+2. Search for **Webhooks** in the Catalog, select it, and choose which of your Javascript sources to connect the destination to.
 3. Add the following as your Webhook URL: `https://pendo-io.appspot.com/data/segmentio/YOUR_PENDO_API_KEY` and replace `YOUR_PENDO_API_KEY` with your actual Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key.
 4. Headers are not required in Webhook configuration. Once you're done adding in your URL, save changes.
 5. Using Track method also requires a setting enabled on your Pendo subscription. contact Pendo to enable this feature flag for your account.
 
-To learn more about server-side data to Pendo, check out their [support documentation](https://help.pendo.io/resources/support-library/integrations/segment-integration.html#send-server-side-data-to-pendo).
+To learn more about server-side data to Pendo, see Pendo's [support documentation](https://help.pendo.io/resources/support-library/integrations/segment-integration.html#send-server-side-data-to-pendo){:target = "_blank"}.
 
 ## 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:
 
 ```javascript
 analytics.identify("userId1", {
@@ -44,12 +44,12 @@ analytics.identify("userId1", {
 });
 ```
 
-When you send an Identify call, we will pass that user's information to Pendo with `userId` as Pendo's visitor ID. User traits that you pass are mapped to visitor metadata in Pendo.
+When you send an Identify call, Segment passes that user's information to Pendo with `userId` as Pendo's visitor ID. User traits that you pass are mapped to visitor metadata in Pendo.
 
 
 ## Group
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like:
 
 ```javascript
 analytics.group("0e8c78ea9d97a7b8185e8632", {
@@ -60,11 +60,11 @@ analytics.group("0e8c78ea9d97a7b8185e8632", {
 });
 ```
 
-When you send a Group call, we will send `groupId` as the Pendo as account ID. Group traits are mapped to account metadata in Pendo. If you are using Pendo account data, group calls (fields `groupId` & `traits`) are required.
+When you send a Group call, Segment sends `groupId` as the Pendo as account ID. Group traits are mapped to account metadata in Pendo. If you are using Pendo account data, group calls (fields `groupId` & `traits`) are required.
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```javascript
 analytics.track("Registered", {
@@ -74,6 +74,6 @@ analytics.track("Registered", {
 });
 ```
 
-When you send a Track call, we will send it as a Pendo Track Event. Note that `groupId` is not included by default in a Track call, but it is highly recommended to add as a property.
+When you send a Track call, Segment sends it as a Pendo Track Event. Note that `groupId` is not included by default in a Track call, but it is highly recommended to add as a property.
 
-Pendo will map `groupId` to an account ID. For more information on Pendo's Track Events, check out their [support documentation](https://help.pendo.io/resources/support-library/integrations/track-events.html).
+Pendo maps `groupId` to an account ID. For more information on Pendo's Track Events, check out their [support documentation](https://help.pendo.io/resources/support-library/integrations/track-events.html).
diff --git a/src/connections/destinations/catalog/webhooks/index.md b/src/connections/destinations/catalog/webhooks/index.md
@@ -4,8 +4,6 @@ title: Webhooks Destination
 ---
 Segment Webhooks submit real-time user data to your own HTTP endpoints. A Webhook is an HTTP callback: a simple event-notification using HTTP POST. A web application implementing Webhooks will POST a message to a URL when certain things happen.
 
-This document was last updated on January 28, 2018. If you notice any gaps, out-dated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
-
 ## Getting Started
 
 {% include content/connection-modes.md %}
@@ -14,17 +12,18 @@ This document was last updated on January 28, 2018. If you notice any gaps, out-
 2. Search for "Webhooks" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Specify up to five different Webhook URLs, you would like to forward data to.
 4. Add in any header values you would like to add to the HTTP requests
-5. If you require authentication, add in a [shared secret](https://segment.com/docs/connections/destinations/catalog/webhooks/#authentication).
-6. Toggle on Webhooks and we will start sending all the requests received by Segment's API.
+5. If you require authentication, add in a [shared secret](/docs/connections/destinations/catalog/webhooks/#authentication).
+6. Once enabled, Segment sends data to the configured webhook
 
-**Note:** We'll send you HTTP(s) POST requests that look like the below for each type. Note with each call, you'll also receive a [`context`](/docs/connections/spec/common/#context) object that provides information about the user's device, IP address, etc. As you start experimenting, we recommend trying the Webhooks destination with [RequestBin.com](https://requestbin.com/) and [ultrahook](http://www.ultrahook.com) to immediately start seeing requests coming through.
+> info ""
+> **Note:** With each call, Segment sends receive a [`context`](/docs/connections/spec/common/#context) object that provides information about the user's device, IP address, etc. As you start experimenting, test the Webhooks destination with [RequestBin.com](https://requestbin.com/) and [ultrahook](http://www.ultrahook.com) to see requests as they come through.
 
 ## Webhooks timeouts
 
 When Segment sends an event to a webhook endpoint, the service must respond within 5 seconds. If Segment does not receive a response within that period, the system logs a timeout error and [retries the event later](/docs/connections/destinations/#retries-between-segment-and-destinations).
 
 ## 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:
 ```
 POST https://your-webhook-url.com/x
 ```
@@ -48,7 +47,7 @@ Content-Type: application/json
 ```
 ## Screen
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like:
 ```
 POST https://your-webhook-url.com/x
 ```
@@ -82,7 +81,7 @@ Content-Type: application/json
 ```
 ## 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:
 ```
 POST https://your-webhook-url.com/x
 ```
@@ -106,7 +105,7 @@ Content-Type: application/json
 ```
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 ```
 POST https://your-webhook-url.com/x
 ```
@@ -129,7 +128,7 @@ Content-Type: application/json
 ```
 ## Alias
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](/docs/connections/spec/alias/) does. An example call would look like:
 ```
 POST https://your-webhook-url.com/x
 ```
@@ -148,7 +147,7 @@ Content-Type: application/json
 ```
 ## Group
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like:
 
 ```
 POST https://your-webhook-url.com/x
@@ -176,7 +175,7 @@ Content-Type: application/json
 
 ## Delete
 
-When you create a deletion request, for each affected source that has webhooks enabled we will forward a notification so that you can kick off any automations needed on your side. An example call would look like:
+When you create a deletion request, for each affected source that has webhooks enabled, Segment forwards a notification so that you can kick off any automations needed on your side. An example call would look like:
 
 ```
 POST https://your-webhook-url.com/x
@@ -196,7 +195,7 @@ Content-Type: application/json
 ## Appendices
 ### Authentication
 
-If you want to authenticate the requests being sent to your webhook endpoint, you can input a `sharedSecret` in the advanced option settings. If you provide this, we will sign your requests using the shared secret and the body of the request, and add that as the ​`X-Signature`​ header. We calculate a SHA1 digest using the shared secret and the JSON-stringified body of the request.
+If you want to authenticate the requests being sent to your webhook endpoint, you can input a `sharedSecret` in the advanced option settings. If you provide this, Segment signs your requests using the shared secret and the body of the request, and add that as the ​`X-Signature`​ header. Segment calculates a SHA1 digest using the shared secret and the JSON-stringified body of the request.
 
 An example of how one might authenticate the requests would be:
 
diff --git a/vale-styles/Vocab/Docs/accept.txt b/vale-styles/Vocab/Docs/accept.txt
@@ -45,3 +45,4 @@ viewability
 measurability
 Lightbox
 gmail
+(?:P|p)endo

-Original file line number
+Diff line change
@@ @@ -1,3 +1,4 @@ @@
 items:
   - hubspot
   - iterable
 +  - google-ads-gtag