resolve intercom-kotlin edits

alanjcharles · alanjcharles · commit 68bda531aabb · 2024-01-29T13:05:32.000-07:00
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md
@@ -54,7 +54,7 @@ Open your Package.swift file and add the following to the `dependencies` section
 
 ## Using the Plugin in your App
 
-Open the file where you setup and configure the Analytics-Swift library.  Add this plugin to the list of imports.
+Open the file where you set up and configured the Analytics-Swift library.  Add this plugin to the list of imports.
 
 ```
 import Segment
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/intercom-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/intercom-swift.md
@@ -48,7 +48,7 @@ Open your Package.swift file and add the following to the `dependencies` section
 
 ## Using the plugin in your app
 
-Open the file where you setup and configure the Analytics-Swift library.  Add this plugin to the list of imports.
+Open the file where you set up and configured the Analytics-Swift library.  Add this plugin to the list of imports.
 
 ```
 import Segment
@@ -151,7 +151,7 @@ analytics.track(name: "Product Purchased", properties: OrderCompletedProperties(
 When you make a Track call from any of the server-side libraries or mobile sources in cloud-mode (for example, without the beta Segment mobile Intercom SDK installed), you must include either the `userId` or `email` of a user already recorded in Intercom.
 
 
-### Revenue and currency
+### Revenue and currency properties
 If you send `properties.revenue` and `properties.currency` to Intercom, Segment formats those properties according to [Intercom's Monetary Amount](https://developers.intercom.com/intercom-api-reference/reference/submit-a-data-event#metadata-object){:target="_blank"} and sends them to Segment as:
 
 ```js
@@ -216,7 +216,7 @@ When you call Group from any of any server-side libraries or mobile sources in c
 > Intercom supports NSString, NSNumber or NSNull type values on iOS.
 
 ## Reset
-When `reset` is called The bundled mobile SDK `reset` method un-registers a user in Intercom. When users want to log out of your app and you call Segment's `reset` method, Segment calls:
+The bundled mobile SDK `reset` method un-registers a user in Intercom. When users want to log out of your app and you call Segment's `reset` method, Segment calls:
 
 ```swift
   Intercom.logout()
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/intercom-kotlin-android.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/intercom-kotlin-android.md
@@ -2,21 +2,19 @@
 title: Analytics Kotlin Intercom Plugin
 id: 54521fd725e721e32a72eec6
 ---
-[Intercom](https://www.intercom.com/){:target="_blank"} makes customer messaging apps for sales, marketing, and support, connected on one platform. The Intercom Destination Plugin is open-source.You can browse the Kotlin code for [Android](https://github.com/segment-integrations/analytics-kotlin-intercom/tree/main){:target="_blank"} on GitHub.
+[Intercom](https://www.intercom.com/){:target="_blank"} makes customer messaging apps for sales, marketing, and support, connected on one platform. The Intercom Destination Plugin is open-source. You can browse the Kotlin code for [Android](https://github.com/segment-integrations/analytics-kotlin-intercom/tree/main){:target="_blank"} on GitHub.
 
 ## Getting Started
 
 1.  From the Segment Destinations page click **Add Destination**.
 2.  Search for "Intercom" and select it in the results that appear.
-3.  Choose which Source to connect Intercom to.
+3.  Select a source to connect to your Intercom destination.
 4.  Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
-5. [Find your "App ID" in the Intercom UI](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id){:target="_blank"} or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.
-
-This means you should remove Intercom's snippet from your page.
+5. [Find your "App ID" in the Intercom UI](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id){:target="_blank"} or by navigating to the Gear Menu and selecting App Settings > API Keys. It should look something like `9iefb489`.
 
 ## Adding the dependency
 
-To install the Segment-Intercom integration, simply add this line to your gradle file:
+To install the Segment-Intercom integration, add this line to your gradle file:
 
 ```
 implementation com.segment.analytics.kotlin.destinations:intercom:<latest_version>
@@ -29,9 +27,9 @@ implementation(com.segment.analytics.kotlin.destinations:intercom:<latest_versio
 ```
 
 
-## Using the Plugin in your App
+## Using the plugin in your app
 
-Open the file where you setup and configure the Analytics-Kotlin library.  Add this plugin to the list of imports.
+Open the file where you set up and configured the Analytics-Kotlin library.  Add this plugin to the list of imports.
 
 ```
 import com.segment.analytics.kotlin.destinations.intercom.IntercomDestination
@@ -47,11 +45,11 @@ Just under your Analytics-Kotlin library setup, call `analytics.add(plugin = ...
     analytics.add(plugin = IntercomDestination(applicationContext))
 ```
 
-Your events will now begin to flow to Intercom in Device mode.
+Your events will now begin to flow to Intercom in device-mode.
 
 ## Identify
 
-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:
+If you're not familiar with the Segment Spec, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```java
 analytics.identify("user-123", buildJsonObject {
@@ -65,20 +63,18 @@ analytics.identify("user-123", buildJsonObject {
 });
 ```
 
-When you call Identify, Segment creates or updates the user in Intercom using their [Users API](https://developers.intercom.com/reference#users){:target="_blank"}. Segment does not currently support creation of leads.
+When you call Identify, Segment creates or updates the user in Intercom using their [Contacts API](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/Contacts/contact/){:target="_blank"}. Segment does not currently support creating [leads](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/Contacts/MergeContact)
 
 > info ""
-> Intercom associates Track events with known users. An Identify call with a `userId` is required before Track events are associated properly. Segment's bundled mobile SDKs also require that `identify` be called prior to `track`, but accepts setting an unknown user in Intercom using the `anonymousId`.
-
-Keep reading for more information about the Identify call depending on the source type you send it from.
+> Intercom associates Track events with known users. An Identify call with a `userId` is required before Track events are associated properly. Segment's bundled mobile SDKs also require that Identify be called prior to Track, but accepts setting an unknown user in Intercom using the `anonymousId`.
 
-- Passing `traits.company` creates a new Intercom Company if the `company_id` does not match a known company. See the [Intercom contact model documentation](https://developers.intercom.com/intercom-api-reference/reference/the-contact-model){:target="_blank"} for more details.
+-  Passing `traits.company` creates a new Intercom Company if the `company_id` does not match an existing `company_id`. See the [Intercom contact model documentation](https://developers.intercom.com/intercom-api-reference/reference/the-contact-model){:target="_blank"} for more details.
 - Trait values must be no longer than 255 characters
 
 
 Intercom supports both logged-in or logged-out users. You must register your users with Intercom before you can talk to them or see what they do in your app. This means that Identify must be called before Track.
 
-Intercom allows users to choose to track only known or only unknown users, as well as both. Segment supports the ability to track both by checking for logged in users (determined by the `userId`) and falling back to setting the user as "Unidentified" when this is not present.
+Intercom allows you to track only known or only unknown users, or all users regardless of identification status. Segment supports the ability to track all users regardless of identification status by checking for logged in users (determined by the `userId`) and falling back to setting the user as "Unidentified" when this is not present.
 
 Intercom knows when your app is backgrounded and comes alive again, so you won't need to re-register your users.
 
@@ -97,7 +93,7 @@ Segment maps the following Intercom standard attributes on Identify.
 | remaining `traits`                        | `customAttributes`       | Custom attributes for this user.     |
 
 > info ""
-> Intercom supports values of type String, Long, Float, Double, Boolean, Character, Byte, Short or Integer on Android. Pass Android traits using camel case to conform with Java convention.
+> Intercom supports String, Long, Float, Double, Boolean, Character, Byte, Short or Integer type values on Android. Pass Android traits using camel case to conform with Java convention.
 
 #### Collect Context
 
@@ -107,7 +103,7 @@ The fields collected from the [context object](/docs/connections/spec/common/) a
 
 ## Track
 
-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:
+If you're not familiar with the Segment Spec, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```java
 analytics.track("View Product", buildJsonObject {
@@ -120,8 +116,9 @@ analytics.track("View Product", buildJsonObject {
 > Because Intercom only associates Track events with known users, an Identify call with a `userId` is required before Track events are associated properly.
 
 
-### Revenue and currency
-If you send `properties.revenue` and `properties.currency`, Segment formats that according to [Intercom's Monetary Amount](https://developers.intercom.com/intercom-api-reference/reference/submit-a-data-event#metadata-object){:target="_blank"} and send it as:
+### Revenue and currency properties 
+If you send `properties.revenue` and `properties.currency` to Intercom, Segment formats those properties according to [Intercom's Monetary Amount](https://developers.intercom.com/intercom-api-reference/reference/submit-a-data-event#metadata-object){:target="_blank"} and sends them to Segment as:
+
 
 ```js
 price: {
@@ -130,20 +127,20 @@ price: {
 }
 ```
 
-The bundled mobile integrations also check `properties.total` if `properties.revenue` is not present, and assign the total value as the amount value.
+If `properties.revenue` is not present, the bundled mobile integrations check `properties.total` and assign the total value as the `properties.revenue` or amount value.
 
 ### Limited Properties
-Intercom can only store [five event properties](http://docs.intercom.io/Intercom-for-user-analysis/Tracking-User-Events-in-Intercom#metadata-support){:target="_blank"} per event. That means if you send an event to Segment with more than five properties, Intercom only shows the first five properties.
+Intercom can only store [5 event properties](http://docs.intercom.io/Intercom-for-user-analysis/Tracking-User-Events-in-Intercom#metadata-support){:target="_blank"} per event. If you send an event to Segment with more than 5 properties, Intercom only shows the first 5 properties.
 
 ### Limited Events
 
-Intercom only allows a total of 120 unique _active_ event names. If you're sending Segment more than 120 unique event names, Intercom only accepts the first 120 events that their servers see, and the rest throw an error.
+In Intercom, an "Active" event is an event that hasn't been archived. Intercom only allows a total of 120 unique _active_ event names. If you're sending Segment more than 120 unique event names, Intercom only accepts the first 120 events that their servers encounter. Any additional unique event names will result in an error. 
 
-In Intercom, an "Active" event is an event that hasn't been archived. If you archive an event, it makes it inactive and removes it from your 120 active events. If you need to bring your account back under the 120 event limit, archive some events from in the Intercom UI by navigating to **Settings > (workspace name) data > Events**, then click on the event to archive.
+If you need to bring your account back under the 120 event limit, archive some events from in the Intercom UI by navigating to **Settings > (workspace name) data > Events**, then click on the event to archive. 
 
 ## Group
 
-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:
+If you're not familiar with the Segment Spec, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like:
 
 ```java
 analytics.group("user-123", buildJsonObject {
@@ -158,7 +155,7 @@ Segment supports Intercom companies in all sources. Users can be put into multip
 When you call Group from any of any server-side libraries or mobile sources in cloud-mode (without Segment's mobile Intercom SDK installed), you must include either the `userId` or `email` of an existing user in Intercom.
 
 > info ""
-> In order for the Company Sessions Count to update within Intercom, the company must first be recorded in an `identify` call.
+> In order for the Company Sessions Count to update within Intercom, the company must first be recorded in an Identify call.
 
 
 | Segment Parameter      | Intercom Parameter            | Description                                   |
@@ -173,10 +170,10 @@ When you call Group from any of any server-side libraries or mobile sources in c
 
 
 > info ""
-> Intercom supports values of type `String`, `Long`, `Float`, `Double`, `Boolean`, `Character`, `Byte`, `Short` or `Integer` on Android. Pass Android traits using camel case to conform with Java convention.
+> Intercom supports `String`, `Long`, `Float`, `Double`, `Boolean`, `Character`, `Byte`, `Short` or `Integer` type values on Android. Pass Android traits using camel case to conform with Java convention.
 
 ## Reset
-When `reset` is called The bundled mobile SDK `reset` method un-registers a user in Intercom. When users want to log out of your app and you call Segment's `reset` method, Segment calls:
+The bundled mobile SDK `reset` method un-registers a user in Intercom. When users want to log out of your app and you call Segment's `reset` method, Segment calls:
 
 ```java
   intercom.logout()
@@ -186,6 +183,6 @@ When `reset` is called The bundled mobile SDK `reset` method un-registers a user
 
 ### Arrays and Objects
 
-Intercom doesn't support custom arrays or objects. This means that if you want to send a certain user `trait` or event `property` to Intercom, you must send them at the top level.
+Intercom doesn't support custom arrays or objects. If you want to send a certain user `trait` or event `property` to Intercom, you must send them at the top level instead of in an array or object.
 
-This limitation does not apply, however, for mapping `company` objects on [Identify calls](/docs/connections/spec/identify/). Segment continues to handle that in the same way as before. This is only applicable for any custom traits or properties.
+This limitation does not apply if you are mapping custom traits or properties to `company` objects on [Identify calls](/docs/connections/spec/identify/). 
