Merge pull request #3168 from segmentio/develop

Release 22.27.1

Author: forstisabella

.github/styles/Vocab/Docs/accept.txt

@@ -63,6 +63,7 @@ Kameleoon
 Kissmetrics
 Lightbox
 Littledata
+Mailchimp
 Mailmodo
 markdownify
 Marketo

.github/styles/segment/headings.yml

@@ -31,6 +31,7 @@ exceptions:
 - Amberflo
 - Amplitude
 - Amplitude (Actions)
+- Analytics.js
 - Anodot
 - Appcues
 - AppNexus
@@ -375,3 +376,4 @@ exceptions:
 - Zendesk
 - Zendesk Connect
 - Zopim
+- JavaScript

src/_includes/content/destination-dossier.html

@@ -43,7 +43,12 @@
 <h6>Destination Info</h6>
 <ul class="qi">
   {% if destMethods.size > 0 %}<li>Accepts {% for method in destMethods%}{% if destMethods.size == 1 %}{{method}} calls.{% else %}{% unless forloop.last == true %}{{method}}, {% endunless %}{% if forloop.last == true%}and {{method}} calls{%endif%}{% endif %}{% endfor %}</li>{% endif %}
-  <li>Referred to as <strong>{{previous_names | join: '</strong>, or <strong>' }}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>
+  {% if previous_names.size == 1 or components.size == 0 %}
+    <li>Refer to it as <strong>{{previous_names | join: '</strong>, or <strong>' }}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>
+  {% else %}
+   {% if connectionModes.cloud.web == true or connectionModes.cloud.mobile == true or connectionModes.cloud.server == true %} <li>In Cloud-mode, refer to it as <strong>{{previous_names | join: '</strong>, or <strong>' }}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a></li>{%endif%}
+   {% if connectionModes.device.web == true or connectionModes.device.mobile == true or connectionModes.device.server == true %} <li>In Device-mode, refer to it as <strong>{{previous_names | first}}</strong> in the <a href="/docs/guides/filtering-data/#filtering-with-the-integrations-object">Integrations object</a> </li>{%endif%}
+  {% endif %}
   {% if destinationInfo.status == "PUBLIC_BETA" %}<li>This destination is in <span class="release-pill">Beta</span></li>{% endif %}
 </ul>
 {% if components.size > 0%}

src/_includes/content/destination-footer.md

@@ -46,19 +46,7 @@ Segment lets you change these destination settings from the Segment app without
 {% endunless %}
 {% if currentIntegration.previous_names.size > 1 %}
 
-{% unless page.hide-integrations-object == true %}
-## 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 %}
 
 {% endif %}

src/_includes/content/functions/runtime.md

@@ -15,6 +15,7 @@ The following dependencies are installed in the function environment by default.
 - [`@google-cloud/functions v1.1.0`](https://www.npmjs.com/package/@google-cloud/functions) exposed as `google.cloud.functions`
 - [`@google-cloud/pubsub v2.6.0`](https://www.npmjs.com/package/@google-cloud/pubsub) exposed as `google.cloud.pubsub`
 - [`@google-cloud/storage v5.3.0`](https://www.npmjs.com/package/@google-cloud/storage) exposed as `google.cloud.storage`
+- [`jsforce v1.11.0`](https://www.npmjs.com/package/jsforce) exposed as `jsforce`
 - [`jsonwebtoken v8.5.1`](https://www.npmjs.com/package/jsonwebtoken) exposed as `jsonwebtoken`
 - [`lodash v4.17.15`](https://www.npmjs.com/package/lodash) exposed as `_`
 - [`moment v2.26.0`](https://www.npmjs.com/package/moment/v/2.26.0) exposed as `moment`

src/connections/destinations/catalog/algolia-insights/index.md

@@ -1,7 +1,6 @@
 ---
 title: Algolia Insights Destination
 rewrite: true
-layout: dest-test
 beta: true
 redirect_from: '/connections/destinations/catalog/algolia/'
 id: 5d373a350abf930001a6b70f

src/connections/destinations/catalog/google-ads-classic/index.md

@@ -6,14 +6,11 @@ hide-personas-partial: true
 cmode-override: true
 id: 54521fd525e721e32a72ee92
 ---
-> info ""
-> The Google Ads (Classic) destination code is available on GitHub [here](https://github.com/segment-integrations/analytics.js-integration-adwords){:target="_blank"}.
+> warning "The Google Ads (Classic) destination is outdated."
+> For website tracking, Google released a new version of Google Ads that uses [a global site tag (gtag.js)](https://support.google.com/google-ads/answer/7548399?hl=en){:target="_blank"}. Segment supports the global site tag in the [Google Ads (Gtag) destination](/docs/connections/destinations/catalog/google-adwords-new/). For mobile tracking, Google recommends using their [Firebase SDKs](https://support.google.com/google-ads/answer/6397604?hl=en){:target="_blank"}. Segment supports a Firebase implementation with the [Google Firebase destination](/docs/connections/destinations/catalog/firebase/).
 
 ## Getting Started
 
-> info ""
-> Google released a new version of Google Ads that uses [a Global Site Tag (or Gtag)](https://support.google.com/adwords/answer/7548399?hl=en). Segment supports this using a different version of the destination - see the documentation for [Google Ads (Gtag)](/docs/connections/destinations/catalog/google-adwords-new/) for more details.
-
 With Segment, you can use your events to fire a Google Ads conversion pixel from your website **in client-side JavaScript.**
 You can also trigger Google Ads (Classic) conversion from your mobile app using the **Server to Server** destination, so you don't need to include the SDK in your app. The server to server connection requires mobile device specific details to forward the events to Google Ads (Classic). Google Ads (Classic) **does not work with any server-side libraries**. Make sure when you're setting up your Google Ads (Classic) conversions that you choose the appropriate tracking method.
 
@@ -47,7 +44,7 @@ To find a conversion ID look inside of your Google Ads (Classic) account and nav
 
 If you select "Website," click through to the "Review and Install" step in the Google Ads (Classic) dashboard. Scroll down to the "Install your tag" section and look for `w.google_conversion_id`. Copy the string directly to the right of it, and paste it into the Google Ads (Classic) section of your Segment destination tab.
 
-If you select "App" you can choose to track conversions from Firebase, Google Play, or first opens and in-app actions. For more on setting up moble tracking, see [Server to Server Destination for Mobile Apps](#mobile--server) further down on this page.
+If you select "App" you can choose to track conversions from Firebase, Google Play, or first opens and in-app actions. For more on setting up mobile tracking, see [Server to Server Destination for Mobile Apps](#mobile--server) further down on this page.
 
 > info ""
 > If using the New Adwords Experience, the Conversion ID can now be found in a different location. Navigate to Tools, Billing, and Settings menu and, then, select "Measurement: Conversions", which opens to the "Conversion Actions" table. From here you can drill down to the conversion "Tag setup" to view the tag details. From here, select Use Google Tag Manager card in order to expose the Conversion ID.
@@ -135,7 +132,7 @@ All `track` events are by default sent to your Google Ads (Classic) account and
  8. ecommerce_purchase
  9. custom
 
-Segment integrates with these event types using the use of the [Semantic Event Spec](/docs/connections/spec/semantic/). Each individual mapping Segment supports is documented in the sections below. Any event Segment recieves that is not a mapped semantic event will be sent to Google Ads (Classic) as a `custom` event type.
+Segment integrates with these event types using the use of the [Semantic Event Spec](/docs/connections/spec/semantic/). Each individual mapping Segment supports is documented in the sections below. Any event Segment receives that is not a mapped semantic event will be sent to Google Ads (Classic) as a `custom` event type.
 
 ### Application Installed
 

src/connections/destinations/catalog/google-ads-gtag/index.md

@@ -6,22 +6,19 @@ strat: google
 name-override: true
 id: 5a03bfe73156760001ab34ec
 ---
-## 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.
+The [Google global site tag (gtag.js)](https://support.google.com/google-ads/answer/7548399?hl=en){:target="_blank"} is a JavaScript tagging framework and API that allows you to send web conversions to Google Ads. With the Segment Google Ads (Gtag) destination, Segment loads gtag.js for you so you can make efficient use of your existing tracking implementation.
 
-> info "Info message."
-> **IMPORTANT**: Only use this destination if your Google Ads account is using the _New_ (Gtag) Experience. If you're using Google Tag Manager (a separate product) as well, don't add the global site tag again in your GTM containers. You should also disable any [Google Ads (Classic)](/docs/connections/destinations/catalog/adwords/) destinations within the same source, since **Google Ads (Classic)** can't load at the same times as **Google Ads (Gtag)**.
+> info ""
+> Only use this destination if your Google Ads account is using Gtag. If you're using Google Tag Manager, don't add the global site tag (gtag.js) in your GTM containers. You should also disable any [Google Ads (Classic)](/docs/connections/destinations/catalog/adwords/) destinations within the same source, since **Google Ads (Classic)** can't load at the same time as **Google Ads (Gtag)**.
 
 ## Getting Started
 
-You can use this destination to map your `.page()` calls to **Page Load Conversions** or `.track()` calls to **Click Conversions**.
-
-Currently this is only supported on the browser.
+You can use this destination to map your `.page()` calls to **Page Load Conversions** or `.track()` calls to **Click Conversions**. Currently this is only supported on the browser.
 
 ## Page
 
-If you want to map all your unnamed `.page()` calls to a default Page Load Conversion, you can enter the AdWords Conversion ID in **Settings > Default Page Conversion**. However, if you created specific Page Load Conversions in Google Ads that you'd like to map your named `.page()` calls in Segment, you can map the events in **Settings > Page Load Conversions**.
+If you want to map all your unnamed `.page()` calls to a default Page Load Conversion, you can enter the Conversion ID in **Settings > Default Page Conversion**. However, if you created specific Page Load Conversions in Google Ads that you'd like to map your named `.page()` calls in Segment, you can map the events in **Settings > Page Load Conversions**.
 
 Segment forwards all the `properties` of the page call, such as `path`, `title`, `url`, because by default, Google Ads (Gtag) makes these available in your remarketing campaigns.
 
@@ -48,9 +45,9 @@ If you pass `properties.value`, `properties.currency`, or `properties.order_id`,
 
 The only exception is that for `Order Completed` events, Segment will map Google's semantic `value` field to your `properties.revenue`.
 
-## Troubleshooting AdWords Conversions
-To figure out if an event is flagged for Conversion by the AdWords SDK, follow these steps:
-1. Confirm that the events mapped to Google Ads Conversion are being sent in device-mode while using the Segment Analytics.js library. To do this:
+## Troubleshooting Google Ads Conversions
+To figure out if an event is flagged for conversion, follow these steps:
+1. Confirm that the events mapped to a Google Ads conversion are being sent in device-mode while using the Segment Analytics.js library. To do this:
     1. Go to **Connections > Sources** in your workspace and choose your Source.
     2. Go to the **Debugger** tab.
     3. Click on an event and look at the **Raw** view to make sure the events have a library name of `analytics.js`. There should be a snippet of code that looks like this:
@@ -66,16 +63,16 @@ To figure out if an event is flagged for Conversion by the AdWords SDK, follow t
 
       ![Network tab](../../images/network-tab.png)
 
-5. Go to the **Settings** tab for your Gtag destination in Segment on a new webpage and choose **Click Conversions** to look at the mapped `track()` events and make sure the events are mapped to the correct **Adwords Conversion Label**.
+5. Go to the **Settings** tab for your Gtag destination in Segment on a new webpage and choose **Click Conversions** to look at the mapped `track()` events and make sure the events are mapped to the correct **Conversion Label**.
 
       ![Edit Settings](../../images/conversion-settings.png)
 
 6. Go back to your website and trigger the event mapped to the conversion. For example, as shown in the image above, it would be `Order Completed`.
-7. Go to the Network tab in your browser and enter the **Adwords Conversion Label** linked to the event you triggered in the **Filter** field.
+7. Go to the Network tab in your browser and enter the **Conversion Label** linked to the event you triggered in the **Filter** field.
 
       ![Network tab](../../images/network-tab-search.png)
 
-8. See if the value for the `ct_cookie_present` changed to `true`. If `true`, it means that Adwords counts the event as a conversion.  
+8. See if the value for the `ct_cookie_present` changed to `true`. If `true`, it means that Google Ads counts the event as a conversion.  
 
 ## Multiple Google Ads Accounts
 

src/connections/destinations/catalog/hotjar/index.md

@@ -3,41 +3,36 @@ title: Hotjar Destination
 rewrite: true
 id: 5913371070a3e552b9561a4e
 ---
-[Hotjar](https://help.hotjar.com/hc/en-us) is the fast & visual way to understand your users. It offers a full set of user experience tools: heatmaps, session recordings, forms reporting, funnels, and feedback tools, giving you everything your team needs to uncover user insights and make the right changes.
+[Hotjar](https://hotjar.com){:target="_blank"} enables you to understand your users in a fast and visual way. Hotjar offers a full set of tools such as analytics, page heatmaps, session recordings, feedback tools, and more. Hotjar provides you with everything your team needs to uncover user insights and make the right product changes.
 
-The Segment Hotjar Destination allows you to both easily install Hotjar on your pages, and send [User Attributes](https://help.hotjar.com/hc/en-us/articles/360038394053-How-to-Setup-User-Attributes-in-4-Steps) information over Hotjar's [Identify API](https://help.hotjar.com/hc/en-us/articles/360033640653) using the Segment Identify Spec. As of February 3rd, 2020, this allows you to:
-
-* [Target Polls and Incoming Feedback to users based on their User Attributes](https://help.hotjar.com/hc/en-us/articles/360022688554)
-* [Lookup and Delete user data based on their User ID](https://help.hotjar.com/hc/en-us/articles/360001749014)
-
-In time, most or all Hotjar features will use User Attributes in some way, with filtering Recordings planned in the first half of 2020.
-
-This destination is maintained by Segment.
+The Segment Hotjar Destination allows you to get started with Hotjar and its core APIs. You can:
+1. Automatically install the [Hotjar Tracking Code](https://help.hotjar.com/hc/en-us/articles/115011639927){:target="_blank"}.
+2. Automatically send [user attributes](https://help.hotjar.com/hc/en-us/articles/360033640653-Identify-API-Reference){:target="_blank"} to Hotjar by connecting your Segment `identify` calls with Hotjar's own Identify API.
+3. Automatically send [custom events](https://help.hotjar.com/hc/en-us/articles/4405109971095-Events-API-Reference){:target="_blank"} to Hotjar by connecting your Segment `track` calls with Hotjar's own Events API.
 
+Knowing who your users are and what they're doing unlocks more advanced filtering and targeting capabilities across all of Hotjar's tools, helping you find meaningful insights faster.
 
 ## Getting Started
 
 {% include content/connection-modes.md %}
 
-1. From the Segment web app, click **Catalog**.
+1. Navigate to **Connections** and click **Add Destination** From the Segment web app.
 
-2. Search for "Hotjar" in the Catalog, select it, and choose which of your Javascript sources to connect the destination to.
+2. Search for *Hotjar* in the Catalog, select it, and choose the Javascript source you want to connect the destination to.
 
-3. Add your Hotjar Site ID to your Destination settings. You can find this under Settings and Sites & Organizations in your Hotjar dashboard. It should be a whole number (e.g. 123456).
+3. Add your **Hotjar Site ID** to your Destination settings. You can find this ID in Account settings > Sites & Organizations.
 
-4. Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Hotjar's tracking snippet, along with your Site ID, onto the page. If you are already using Hotjar, remove Hotjar's snippet from your code.
-
-Hotjar automatically starts tracking visitors based on the tools you have enabled in your Hotjar dashboard.
+Your changes will appear in the Segment CDN after 45 minutes, and then Analytics.js will start to asynchronously load Hotjar's tracking snippet and send data. If you're already using Hotjar, remove Hotjar's snippet from your code.
 
 ## Identify
 
-The Hotjar destination will automatically ingest a User ID, as well as values sent over your Identify spec as [traits](/docs/connections/spec/identify/#traits), as long as [User Attributes are enabled in Hotjar](https://help.hotjar.com/hc/en-us/articles/360038394053-How-to-Setup-User-Attributes-in-4-Steps#step-2-review-your-privacy-requirements-and-enable-user-attributes).
+The Hotjar destination will automatically ingest a User ID and any values sent over your Identify spec as [traits](/docs/connections/spec/identify/#traits), as long as session capture is enabled in Hotjar.
 
 Identify calls that do not have a User ID value will not be sent to Hotjar.
 
 ### Nested values or lists
 
-The Hotjar Identify API is unable to ingest values passed as nested objects or lists over your `identify` Spec:
+Currently, the Hotjar Identify API **does not** support ingesting values passed as nested objects or lists over your identify Spec:
 
 ```js
 "traits": {
@@ -54,6 +49,23 @@ The Hotjar Identify API is unable to ingest values passed as nested objects or l
     }
 ```
 
-In this example, Hotjar would reject all the values in the `address` field.
+In the example above, Hotjar rejects all the values in the `address` field.
+
+## Track
+
+The Hotjar destination automatically ingests any user actions tracked over your Track spec as [events](/docs/connections/spec/track/), as long as session capture is enabled in Hotjar.
+
+### Event properties
+
+Currently, the Hotjar Events API **does not** support ingesting event properties:
+
+```js
+analytics.track("Experiment Viewed", {
+  experiment_id: "1234",
+  experiment_name: "new_upsell_UX"
+  variation_id: "1234b"
+  variation_name: "variant"
+});
+```
 
-This is a recognized limitation of this version of the Hotjar Identify API, and as of February 3rd, 2020, is in the improvements backlog for the API.
+In the example above, Hotjar only ingests the event name, `Experiment Viewed`. All of its event properties are rejected.

src/connections/destinations/catalog/variance/index.md

@@ -85,6 +85,16 @@ analytics.group("groupId123", {
 
 Segment sends Group calls to Variance as an `Account` if you've chosen the "Group" Account Mapping method during setup.
 
+### Alias
+
+If you're not familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like this:
+
+```js
+analytics.alias('123456')
+```
+
+If there is an existing user with that `userId` in Variance that matches the `previousId` passed with the alias, that user will be merged into the "123456" user identified in the alias. If there is only one user with the `previousId` and no user with the `userId`, that user will have their Variance `externalId` updated to match the current `userId` passed in the alias.
+
 ## Account Mapping
 
 Variance offers several ways to map your users to accounts or companies, including the following.