Release 22.1.1 (#2307)

* Kameleoon updated their HackMD doc - updated docs accordingly

HackMD:https://hackmd.io/tp-iUR10TAqKSTcYi5Rd1g?view

* Apply suggestions from code review

* Apply suggestions from code review

* Fixed the image that appears in the Amazon S3 documentation

* [LiveIntent Audiences] new destination documentation

* Delete src/connections/destinations/catalog/tableau directory

Updating documentation because Tableau isn't a destination we support. Tableau is a BI tool that can be used on top of a warehouse to visualize and analyze data. Setting up Tableau to a warehouse would be configured directly through Tableau. Customer should reach out to Tableau for support.

* Update src/connections/destinations/catalog/kameleoon/index.md

I've verified with the customer to remove the api name`Kameleoon.API.Visitor.code`

Co-authored-by: stayseesong <[email protected]>

* fix(content): minor grammar / spelling suggestions while reviewing (#2299)

* Update index.md

* update incorrect description of a few fields (#2300)

The description of a few fields were incorrect, the description of the business hours were switched with out-of-business hours:
requester_wait_time_in_minutes_calendar
requester_wait_time_in_minutes_business
on_hold_time_in_minutes_calendar
on_hold_time_in_minutes_business
This was confirmed by looking at the examples here : https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_metrics/

* updates requested from partner (#2304)

* Display links for partner owned components (#2305)

* Add the NPM option to A.js quickstart (#2306)

Co-authored-by: charholt <[email protected]>
Co-authored-by: Charity Holt <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: forstisabella <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>
Co-authored-by: Yimeng Yu <[email protected]>
Co-authored-by: Jason Sooter <[email protected]>
Co-authored-by: Atif Javed <[email protected]>

Author: 8 people

src/_includes/content/destination-dossier.html

@@ -43,11 +43,11 @@ <h6>Destination Info</h6>
 <h6>Components</h6>
 <ul class="components-list">
 {%for component in components %}
-{% if component.code contains "/segment-integrations/" %}
+{% unless component.code contains "/segmentio/" %}
 <li><a href="{{component.code}}" target="_blank">{% if component.type == "IOS" %}iOS{%else%}{{component.type | capitalize}}{%endif%}</a></li>
 {% else %}
 <li>{% if component.type == "IOS" %}iOS{%else%}{{component.type | capitalize}}{%endif%}</li>
-{% endif %}
+{% endunless %}
 {% endfor %}
 </ul>
 

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

@@ -1,5 +1,6 @@
 ---
 title: ClientSuccess Destination
+hide-personas-partial: true
 ---
 
 This destination is maintained by ClientSuccess.
@@ -32,7 +33,7 @@ When you `identify` a user, Segment will pass that user's information to ClientS
 - `firstName` (`first_name`)
 - `lastName` (`last_name`)
 
-All other traits will be sent to ClientSuccess as custom attributes and may be ignored.
+ClientSuccess ignores all other traits sent as custom attributes.
 
 ## Track
 

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

@@ -3,7 +3,7 @@ title: Kameleoon Destination
 rewrite: true
 ---
 
-[Kameleoon](https://kameleoon.com/en) provides GDPR, CCPA, and HIPAA compliant A/B testing, full stack, and AI-powered personalization solutions to help marketers, product owners, and developers maximize customer engagement and conversion - all from a single platform.
+[Kameleoon’s](https://kameleoon.com/en) powerful and easy-to-use A/B testing, full stack, and AI-powered personalization solutions help marketers, product owners, and developers maximize customer engagement and conversion all from a single platform.
 
 This destination is maintained by Kameleoon. For any issues with the destination, [contact the Kameleoon Support team](mailto:[email protected]).
 
@@ -18,34 +18,37 @@ Segment’s Kameleoon destination supports the following Kameleoon products:
 * [Kameleoon AI Personalization](https://www.kameleoon.com/en/platform/personalization){:target="_blank"} (Web Client-side)
 
 
-To begin, request a Kameleoon API key from [[email protected]](mailto:[email protected]).
+In order to use the Kameleoon & Segment.io integration, you first need to request an API Key. Send your request it to [[email protected]](mailto:[email protected]), and be sure to specify your Kameleoon account login.
 
 You will also need the **sitecode** key. You can find it in your Kameleoon account, as described in [How do I find my site id?](https://help.kameleoon.com/question/how-do-i-find-my-site-id/){:target="_blank"}.
 
 To add the destination to your Segment workspace:
 
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
-2. Search for "Kameleoon" in the Destinations Catalog, and select the Kameleoon destination.
-3. Choose which Source should send data to the Kameleoon destination.
+2. Search for **Kameleoon** in the Destinations Catalog, and select the **Kameleoon** destination.
+3. Choose which Source should send data to the **Kameleoon** destination.
 4. Enter the **API Key** and the **sitecode** in the Kameleoon destination settings in Segment.
 
 ## Implementation pre-requisites: matching Users between Kameleoon and Segment
 
-The integration requires you to use the same system of identifiers for both tools, meaning the `userId` value you pass to Segment should be the same value that Kameleoon uses to identify a "visitor". If you use Kameleoon Experiment or Kameleoon AI Personalization on your website, Kameleoon places a cookie that contains an anonymous unique identifier, called the Kameleoon visitorcode, randomly assigned to a visitor. This ID is used to uniquely identify a browser.
+The integration requires you to use the same system of identifiers for both tools, meaning the `userId` value you pass to Segment should be the same value as Kameleoon uses to identify a “visitor”.
 
-Check with your engineers to ensure Kameleoon's `visitorcode` is passed in the `userId` property of the Segment calls to ensure Kameleoon can consolidate data and avoid any analytics discrepancies between the tools in your campaign results.
+If you use Kameleoon Experiment or Kameleoon AI Personalization on your website, Kameleoon places a cookie that contains an anonymous unique identifier, called the Kameleoon visitorcode. This ID is randomly assigned to a visitor and is used to uniquely identify a browser.
 
-To provide a consistent user identifier to Kameleoon, you may specify in Segment calls a user property, `k_visitorCode`, whose value is the Kameleoon visitorcode. You can retrieve the user visitorCode from the browser by using Kameleoon's [Activation API](https://developers.kameleoon.com/activation-api.html#visitor){:target="_blank"}.
+You can either pass Kameleoon's visitorcode in the userId property of the Segment calls to ensure Kameleoon can consolidate data and avoid any analytics discrepancies between the tools in your campaign results, OR you may specify in all Segment calls an additional user property, `k_visitorCode`, whose value is the Kameleoon visitorcode. You can retrieve the user visitorCode from the browser by using Kameleoon's [Activation API](https://developers.kameleoon.com/activation-api.html#visitor){:target="_blank"}.
 
-If you use Kameleoon Full Stack, please refer to the [Kameleoon SDK documentation](https://developers.kameleoon.com/sdks-overview.html){:target="_blank"}.
+If you are not able to update your existing Segment tracking plan, you can also pass Kameleoon's visitor code in an additional Segment call as follows: `analytics.track('Kameleoon identifier', {'k_visitorCode': Kameleoon.API.Visitor.code});Kameleoon`. This will automatically link your internal user ID or anonymous ID to Kameleoon's own visitorCode. Make sure to call it only once per session.
 
+If you use Kameleoon Full Stack, please refer to the [Kameleoon SDK documentation](https://developers.kameleoon.com/sdks-overview.html){:target="_blank"}. Kameleoon recommends you to use your own internal ID to identify users.
 
 ## Supported methods
 
 Kameleoon supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
 
+
 If the Segment event name matches exactly the name of an existing [goal](https://help.kameleoon.com/create-new-goal/){:target="_blank"} in your Kameleoon account, a conversion for this goal will be associated to the visitor. If the goal does not exist, Kameleoon will create a [custom goal](https://help.kameleoon.com/create-new-goal/#Custom_goal){:target="_blank"} by using the Segment event name and associate the conversion to the visitor. The goal will appear in the Kameleoon [goals page](https://help.kameleoon.com/manage-goals/){:target="_blank"} with the name convention 'SegmentIO eventType - eventName'. Once the goal has been created, you can use them in any of your [campaign](https://help.kameleoon.com/set-up-goal-campaign/){:target="_blank"}.
 
+
 ### Page
 
 Send [Page](/docs/connections/spec/page/) calls to record whenever a user sees a page of your website, along with any optional properties about the page. Calling page or screen in a source is one of the first steps to getting started with Segment.
@@ -82,5 +85,3 @@ analytics.track('Login Button Clicked', {"k_visitorCode": "oa16i4syt2ve3b0z"});
 ```
 
 Segment sends Track calls to Kameleoon as a `track` event.
-
-

src/connections/destinations/catalog/liveintent-audiences/index.md

@@ -0,0 +1,35 @@
+---
+title: LiveIntent Audiences Destination
+rewrite: true
+beta: true
+---
+
+LiveIntent Audiences supports audiences generated by Segment Personas as a user property. To use this destination, you need to have Segment’s Business Tier plan which gives you access to [Personas][/docs/personas/].
+
+If you don’t have access to Personas but still want to send data to LiveIntent, you can use the [Page][/docs/connections/spec/page], [Screen][/docs/connections/spec/screen/], [Track][/docs/connections/spec/track/], [Identify][/docs/connections/spec/identify/], and [Group][/docs/connections/spec/group/] calls. For more information about sending your data to LiveIntent via direct calls (to Page, Screen, Track, Identify, and Group), please reach out to your LiveIntent customer success representative.
+
+LiveIntent maintains this destination. For more information about this destination, [contact the LiveIntent Support team](mailto:[email protected]).
+
+## Getting Started
+
+{% include content/connection-modes.md %}
+
+Before getting started, you need to request an API Key and AppId by sending an email to LiveIntent support at `[email protected]`.
+
+Once you have your API Key and APP ID: 
+1. Navigate to the Destinations catalog page in the Segment App and click **Add Destination**.
+2. Search for **LiveIntent** in the Destinations Catalog, and select the LiveIntent Audiences destination.
+3. Choose which Source should send data to the LiveIntent Audiences destination.
+4. Enter the API Key and AppId that you received from LiveIntent in the LiveIntent Audiences destination settings page in Segment.
+
+When you set up this destination for a Segment Personas audience, provide the snake_cased version of the audience name in the Audience settings. You can send audiences generated using Segment Personas to this destination as a user property. If no corresponding audience exists in LiveIntent’s platform, one will automatically create.
+
+## Settings
+
+| Setting   | Description                                                                                                                                                                |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| API Key   | Request from LiveIntent                                                                                                                                                    |
+| AppId     | Request from Liveintent                                                                                                                                                    |
+| Audiences | If you use this destination for an audience generated using Segment Personas, specify the snake-cased name of the Segment audience; otherwise, the setting is invalid |
+
+---

src/connections/destinations/catalog/tableau/images/tableausetup1.png

@@ -483,19 +483,19 @@ In your warehouse, each collection gets its own table. Find below a list of the
    </tr>
    <tr>
      <td>requester_wait_time_in_minutes_calendar</td>
-     <td> Number of minutes the requester spent waiting during business hours.</td>
+     <td> Number of minutes the requester spent waiting outside of business hours.</td>
    </tr>
    <tr>
      <td>requester_wait_time_in_minutes_business</td>
-     <td> Number of minutes the requester spent waiting outside of business hours.</td>
+     <td> Number of minutes the requester spent waiting during business hours.</td>
    </tr>
    <tr>
      <td>on_hold_time_in_minutes_calendar</td>
-     <td> Number of minutes the ticket was on hold during business hours.</td>
+     <td> Number of minutes the ticket was on hold outside of business hours.</td>
    </tr>
    <tr>
      <td>on_hold_time_in_minutes_business</td>
-     <td> Number of minutes the ticket was on hold outside of business hours.</td>
+     <td> Number of minutes the ticket was on hold during business hours.</td>
    </tr>
    <tr>
      <td>created_at</td>

src/connections/destinations/catalog/tableau/images/tableausetup2.png

@@ -22,7 +22,10 @@ Next create an Analytics.js source from your Workspace:
 When you create a Source in the Segment web app, it tells the Segment servers that you'll be sending data from a specific source type. When you create (or change!) a Source in the Segment app, Segment generates a new Write Key for that source. You use the write key in your website code to tell Segment servers where the data is coming from, so Segment can route it to your Destinations and other tools.
 
 
-## Step 2: Copy the Segment Snippet
+## Step 2: Add the Segment Snippet
+
+> success "Install Segment as an NPM package"
+> You can add Segment to your project as an [NPM package](https://www.npmjs.com/package/@segment/snippet){:target="_blank"}. For more information, see the instructions on [GitHub](https://github.com/segmentio/analytics-next#-using-as-an-npm-package){:target="_blank"}.
 
 Paste this snippet into the `<head>` tag of your site to install Segment.